Scribd
Upload
418 views2 pages

Junaid Ahmed Document

This document provides requirements and assignment details for implementing a software system called ToolShopSys to manage tool rentals for a business called HarryTools. The system must allow customers to register loyalty cards, rent tools, and return tools. It must also integrate with an external verification system. The assignment requires designing and implementing the system using object-oriented principles in Java or C++. A final report with use cases, class diagrams, and other UML diagrams is also required.

Uploaded by

junaid ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
418 views2 pages

Junaid Ahmed Document

This document provides requirements and assignment details for implementing a software system called ToolShopSys to manage tool rentals for a business called HarryTools. The system must allow customers to register loyalty cards, rent tools, and return tools. It must also integrate with an external verification system. The assignment requires designing and implementing the system using object-oriented principles in Java or C++. A final report with use cases, class diagrams, and other UML diagrams is also required.

Uploaded by

junaid ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Object

Oriented Analysis & Design (SE-321)


Fall 2017
Assignment 2: Implementation of ToolShopSys and its documentation
Due date: Saturday 23-12-207 13:00 hrs Maximum Marks: 25
Assignment will be marked by demonstration of code and report!!!

Requirements:
Harry is the owner of HarryTools, a rental store that rents Home Improvement Tools (Hammers, Drills etc.…)
to people for their DIY (do-it-yourself) projects. HarryTools wants to get a software system made for
managing its rental records. He wants to system to record tool rentals, tools return, customer details and
record payments.

Harry offer a customer loyalty card to the customer. A customer can be registered for issuance of card by
giving his name, mobile number, address and social security number to Harry who enters this record. System
(ToolShopSys) records customer details and accesses the USSEC system for verification of the customer
details. Harry requests the customer to put his thumb on the device attached to the system for biometric
identification, as required by USSEC. Once USSEC matches and confirms the provided data system generates
a unique customer id that is printed on a loyalty card. Harry laminates the card and hands it over to
customer. For every one dollar spent customer get a loyalty point that can be used to get discounts and fine
waiver for late item return.

Usually, a customer selects a tool (or many tools) from display and brings it to Harry to rent out. Harry
would use system (ToolShopSys) to record rentals. Harry asks customer for duration of the rent period (in
days) and enters the days along with tool’s identifier into system for each tool. System displays rental
charges starting from today after calculating it (based on rates, 7 day = 1 Week and 4 Weeks = 1 month),
advance rent payment, and security deposit (Security deposit is based on tool’s price recorded in the
system). Once customer agrees to terms, Harry enters customers’ name, mobile number, address and social
security number in the System (or Customer id if customer has a loyalty card). The system accesses the
USSEC system for verification of the customer details (This is skipped for the loyalty card customer). Harry
requests the customer to put his thumb on device attached to the system for biometric identification, as
required by USSEC. Once USSEC matches and confirms the provided data system approves the rental and
issues a rental receipt with due date to return item(s) and amount to pay. System also prints a rental
agreement with terms & conditions. Harry request’s the customer to make payment and sign rental
agreement. Harry uses the system to record the payment and files the rental agreement. Customer then
leaves the shop with his rented tool(s).

Harry also wants the ToolShopSys to record item returns from customer. Once a customer comes back to
shop to return the rented item Harry uses the system to record this transaction. Customer returns the items
to Harry. Harry accesses the system to process rental item return. He enters item code or customer id in the
menu, and system fetches the rental records. Harry then ask customer to make payment of total rental
amount including the adjustment of the security deposit and any late fees. (The Security deposit is adjusted
towards payment if possible, else he return the security amount). System records the payments and prints a
final receipt for the customer. System updates inventory and all records after returning the items
transaction.

Assignment:

Implement the software based on given requirements. The application should be menu driven where menu should
have options to register a new customer, issue loyalty card, record tool rental and process tool return.

The implementation of the system should be an OO application.
You have an option to either build this system in Java or C++.
For C++, you are required to follow header/code separation and business classes should not have any cin
or cout statements. The same is with java. You do not have to use JFrame but still there should be a clear ui-
business logic separation.
You should use filing to store data and retrieve data.
You have to make a final report of this implementation. Final reports should have following sections and UML
artefacts.
1) Introduction
2) Use-case diagram

Page 1 of 2
3) All high-level use cases
4) All use cases in fully dressed (The use case should be written in essential style and in conversational
format using these headings: Use Case Name, Primary Actor(s), Pre-Conditions, Post-Conditions, Main
Success Scenario, Extensions or Alternative Scenario)
5) All SSD’s
6) Domain Model
7) System Operation Contracts
8) Interaction Diagrams
9) Class Diagram

The code for the assignment should be submitted in zip file with your name and the report should be a
Google Word Document attached with the assignment. All UML Diagrams should be developed using UML
tool and should not be drawn by using Word or by hand.

Page 2 of 2

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy