Tailoring Rental System

Table of contents

Contents
Project Description (Tailoring Rental System).......................................................................................3
Translate the events into use cases.......................................................................................................3
Generate the initial use case diagram...................................................................................................4
Find initial Problem domain classes.......................................................................................................5
Document first cut scenarios for the RENT use case with their corresponding sequence diagrams.....5
Refine the classes into generalization/specialization hierarchies..........................................................6
Identify any special classes....................................................................................................................6
Identify multiple inheritances and create a solution for it.....................................................................7
Identify whole–part hierarchies............................................................................................................7
Identify attributes and custom methods...............................................................................................7
Identify additional relationships............................................................................................................8
Update class diagram to include initial attributes, custom methods and association relationship.......8
Document second cut scenarios for the RENT use case with their corresponding sequence diagrams.
...............................................................................................................................................................9
Identify time-dependent behaviours. Represent these behaviours on a state chart diagram..............9
Project Description (Tailoring Rental System)
In this project, we have discussed the different rental situations for user and admin. By considering
all the situations we create use case diagram, use case description, hierarchy diagram, sequence
diagram, state chart diagram and identify all the entities and attributes. We have used the Creately
Visiual workspace for the diagrams.

Translate the events into use cases.

 In this event we have to identify all the users, primary Actor, Secondary Actor,
Condition, Scenario, Trigger, Extensions.

Use Case Name Rental Information

Primary Actor Mr. Joseph Acme (Admin)
Secondary Actor 1. Mr. Jacobson( Rental Desk Manager)
2. Mr. MacArthur(Service Manager In
charge)
User: Customer
Pre Condition: 1. Customer must register into the system.
2. They must specify the days for rental
item.

Post Condition 1. The Customer make a decision about

whether to rent items or
Not.
2. Future References

Main Success Scenario 1. Customer should fill all the fields of the
form.
2. Late fine will be charged to the
customer.
3. Customer would get all the items.

Trigger The Customer should login the website of

Tailoring Rental System.
Extensions 1. The Customer does not satisfy with the
item. Process end.
2. If the return time will be not perfect
then it will go for replace.
Generate the initial use case diagram.
 Figure 1 Use Case Diagram of Admin

Figure 2 Use Case Diagram of Customer

Find initial Problem domain classes.

In our Project we have find the domain classes. These are:-

 Enquiry
 Payment
 Admin
 User Master
 Booking Items
 Feedback

Document first cut scenarios for the RENT use case with their
corresponding sequence diagrams
This sequence diagram shows the customer scenario for booking the item. Firstly
admin will login the page and then manage and view the booking for the item. After
that they will check the feedbacks of the item. If there is a need of add item then it
will update and logout the page.

Figure 3: Sequence Diagram for admin

Refine the classes into generalization/specialization hierarchies.

Figure 4: Generalization

Identify any special classes.

The Special Class in the diagram is Feedback Class. This is used in order to improve
the customer experience. Whatever shortcoming suggested by the customer are
likely to be improved by the customer.
The feedback Class has the following attributes:-
 F_id (PK), F_Name, Email, Address, Postal_Code, Phone_No, Service, Opinion

Identify multiple inheritances and create a solution for it.

In A UML Class Diagram implementing Multiple inheritance. In the above diagram.

An abstract representation of multiple inheritance. Instances of Class Feedback and
Item each contain instance of Class User master. An instance of Class Admin contains
instances of class Feedback and Item each of which has an instance of class user
maker. So this way we can solve the problem we will make the Feedback and Item as
a Virtual Class then the same instance copy will send to Admin as a single one.

Identify whole–part hierarchies

In this Diagram we are showing the whole part hierarchies with all the class and their
structure.

User Master

Booking Feedback Item Payment Enquiry

Admin

Figure 5: Whole part hierarchies

Identify attributes and custom methods.

In our UML Class Diagram, there are 6 Classes.

Class Attributes Custom

methods
Enquiry E_Id,Username,Email_Id,Contact_no,Query,Data_form,To_date add()
update()
delete()
User U-Id,Full_name,Password,Address,City,Mobile,Email Add()
Master Update()
Delete()
Admin A_Id,Username,Password Add()
Update()
Delete()
 Payment P_id,Item_Name,Email,Amount Add()
Item I_Id,Color,Price,I_Name,No_of_pas Add()
Update()
Delete()
Feedbac F_Id,F_Name,Email,Address,Postal_Code,Phone_No,Service,Opinion Add()
k Update()
Delete()
Booking ItemIde,Name,Date,Address,Email,No_pieces View()

Identify additional relationships.

Relationship is the association, dependency and aggregation. In our project we
have used the various additional relationship that is one to one (1:1), one to
many (1: M) and many to many(1:1). We can show the dependency also in the
class like User master is dependent on the admin and booking on the car. The
relationship, can be shown as:-

User Master Admin

Figure 6: additional relationalship

Update class diagram to include initial attributes, custom methods

and association relationship.

In this Diagram we have updated the Feedback and item class as a Virtual so that the
only one copy of data and functions will be copied.
 Figure 7: Update class diagram

Document second cut scenarios for the RENT use case with their
corresponding sequence diagrams.
This Diagram shows the Sequence Diagram for users .

Figure 8: sequence diagram for customer

Identify time-dependent behaviours. Represent these behaviours on

a state chart diagram.

In our project the admin have decided to give the rent items for a specific time.
Some for 2 week maximum and other for 3 to 6 months. If the customer will not
return the item within the time period then the customer would pay $20.00 a day.
So customer must return items within the time period. The state chart diagram for
this is
State 1
Customer
Register

Booked Time/Granted
State 2
Taken Item

Check Date/Time/Expire Check Date/Time

State 5
State 3
On time
Impose time

Return/Remove Regist. Return/Remove Regist.

State 4
Finalised

Figure 9: State Chart Diagram