Object Modelling Assignment

Running head: OBJECT MODELLING
OBJECT MODELLING
Name of student
Name of university
Author’s note:

1
OBJECT MODELLING
Table of Contents
Introduction....................................................................................................................2
Requirements..............................................................................................................2
Non-functional requirements.....................................................................................2
Functional requirements.............................................................................................3
Use case diagram........................................................................................................4
Use case description...................................................................................................8
Domain model class diagram...................................................................................11
Conclusion....................................................................................................................15
References....................................................................................................................16

2
OBJECT MODELLING
Introduction
This report intends to provide the requirements analysis and the illustration of the new
system using the proper UML diagrams. Because of the extensive development of the
business environment, management of the company of Swifty has made the decision of
investing in the unified system that would be denoted as the Swifty Unified Management
System. This system that is being implemented in the organisation would be properly used by
the various actors of the system and then all the actors would gain the respective benefits
from the system. The manager level staff of the company would be provided with the
complete access to the system for making the required changes or even executing any
business process.
Requirements
Non-functional requirements
Reliability: The measure of how much the proposed system is reliable for using by the
users (Dennis, Wixom & Roth, 2018). The system is required to provide the accurate data for
the queries presented by the users (Bullo & Lewis, 2019). It should provide the accurate help
for any issues that the users faces during using the SUFS system.
Performance: The SUFS should act according to the input of the users. It should
present the data of the queries of the users in the appropriate sections with ensuring that the
data has been provided clearly. (Balanis, 2016). The system should take 2 to 3 seconds for
returning any major queries of the users (Rajaraman, 2018). The system that is being
developed in the system should take the reboot time of 1 minute and not more than 2 minutes
so that the performance of the business is not hampered extensively.
Security: The passwords for the accessing the system data might only be changed by
the data administrator of the system and no other individual. The passwords should never be

3
OBJECT MODELLING
viewable at any point of entry or any other instant for ensuring that the passwords are not
viewed by any unauthorised individual. The users should receive the notification of any
profile changed through the preferred communication method of the record when the profile
information has been modified.
Usability: The bookings that are made by the customers should be easily available on
the homepage of the customer portal and the notification of the booking would be provided to
the users before they are supposed to board the booked cars. The data of the vehicle should be
entered in the proper columns in the database by the system administrator. It should not allow
the entry of any kind of the duplicate data in the system.
Functional requirements
 The system is required to provide the functionality of easy removal of particular
vehicle to the system admin from the database that has been transferred for repair
of any service (Alvarez et al., 2016)
 The tracking of the live location of any particular vehicle of the company should
be allowed by the system to the manager as well as the system admin (Kan et al.,
2016).
 The proposed system is required to allow the customers to make their booking of
any specified car easily with the successfully execution of the payment for the
particular vehicle (Lessard, Recht & Packard, 2016).
 The service provider should be allowed access in the system for viewing the
pickup order for repair and then send the invoice in the system for the payment
(Valacich, George & Valacich, 2017).
 The system should provide the reminder of any upcoming booking of the
customers to help them remember their booking.