Collin Car Parking System Validation Phase - ITC508 Object Modelling

ITC508 - OBJECT MODELLING
VALIDATION PHASE
STUDENT NAME: SRIKAR REDDY
STUDENT ID:

Table of Contents
INTRODUCTION................................................................................................................................3
Task 1: Analysis of Subsystem Use Cases........................................................................................4
Task 2: Use Case Diagram of Subsystem.........................................................................................5
Operator Use Case for the Collin Car Parking System.................................................................5
Customer Use Case for the Collin Car Parking System................................................................6
Super Admin Use Case for the Collin Car Parking System...........................................................7
Task 3: Use Case Description...........................................................................................................9
Task 4: Class Diagram....................................................................................................................11
Task 5: Sequence Diagram.............................................................................................................12
Customer Login Sequence Diagram...........................................................................................12
Admin authentication and User Update Sequence Diagram.....................................................13
Car Parking Sequence Diagram..................................................................................................15
References.....................................................................................................................................17
List of Tables
Table 1: All Use Case Description....................................................................................................9
Table 2: Table for Customer Login Sequence Diagram.................................................................12
Table 3: Table for Admin authentication and User Update Sequence Diagram Description........14
List of Figures
Figure 1: Operator Subsystem Use Case.........................................................................................5
Figure 2: Customer Subsystem Use Case.........................................................................................6
Figure 3: Super Admin Subsystem Use Case...................................................................................7
Figure 4: Class Diagram..................................................................................................................11
Figure 5: Customer Login Sequence Diagram................................................................................12
Figure 6: Admin authentication and User Update Sequence Diagram.........................................13
Figure 7: Car Parking Sequence Diagram.......................................................................................15

INTRODUCTION
This report is for Collins Company who need a Car Parking System. The Collin is a Melbourne
Based Company that has over twenty Car Parking outlets across the city. Due to increase in the
cars, the city administration needs a new and significant schema by which the car parking could
be more simplified. In this report, I am going discuss the Validation Phase for the system that
has been previously created. For this a Subsystem is chosen that is going to be analysed over
the use case. Later, those use cases are going to be critically analysed for the functionality and
using that a Class Diagram is developed and at last a Sequence diagram of a subsystem is
developed for finding out the better system analysis (Abidi, Krichen, Alba & Molina, 2015).

Task 1: Analysis of Subsystem Use Cases
The Collin Car Parking System is an integrated system that is the combination of several
different subsystems that are going to help in making an effective planning model that can help
in creating a better system for the analysis purpose for the Parking system. Further, this section
is going to help in creating a better analysis of those subsystems and can help in creating a
sustainable plan for the Collin Car Parking development.
Collins Car Parking system includes various Subsystem out of Which three are chosen for the
Use Case Analysis as it will help in finding out the list of activities that is used as an interaction
between the system and the user. The three Subsystem that is chosen for the Analysis are:
 Operator SubSystem
 Customer Subsystem
 Super Admin Subsystem
The above Subsystems are going to help in validating this system process. Further, for each one
of them a separate Use Case Diagram is made and then a sequence Diagram that is going to
elaborate the overall diagram.

Task 2: Use Case Diagram of Subsystem
Operator Use Case for the Collin Car Parking System
The Operator is one of the main Actors and has a significant impact on this whole parking
system. Operator use case is one of the subsystems in this whole system the operator is going
to manage the Car Parking system. The Operator has the power to Manage all the cars within
the parking system.
Figure 1: Operator Subsystem Use Case
Figure 1 is the Use Case Diagram of the Operator Subsystem. The main Functionality of this
system is that it is able to handle the system efficiently for risk detection in the system. The

operator is also going to collect the parking charges for one time users and collect the payment
from the Fixed Customers. The Update Field is going to make any changes that need to be done
for the Customer regarding payment details or the Passwords.

Customer Use Case for the Collin Car Parking System
Figure 2 represents the Use Case Diagram for the Customer Subsystem. This Use case is going
to show the functionality that could be used by the Customer in the real-time situations or
when the system will be started. Further, by this use case, the final system design could be
easily manageable and is going to help inefficient system designing and maintenance. This Use
Case shows the list of actions that could be performed by the customer by defining the
customer roles and how it is going to interact with the real-time system when implemented. In
this, the Actor that is the Customer is Human and can manage to understand the system easily.
Figure 2: Customer Subsystem Use Case

From figure 2 Primary Use Case is Payment. As without payment, the Collin car parking system
would not be able to maintain the parking space of the overall system.
Super Admin Use Case for the Collin Car Parking System
The Super Admin is the Primary actor of this whole system. The Super Admin manage all the
tasks of the entire system and can update the information of operators and it has to deal with
managing the parking Spaces and the Car owners for the overall system. Further, the Super
Admin can also manage all the parking receipts for all of the cars that are parked at present or
was parked before in the past.
Figure 3: Super Admin Subsystem Use Case

The primary Use Case in this Use Case Diagram is the Managed Parked Cars. By using this Use
Case the Super Admin can manage all the parked cars that are parked in the present or any car
that was parked previously.

Task 3: Use Case Description
Table 1: All Use Case Description
Use Case Description
Login This is the Login Use case that is going to help the Actors of the
System to Login and access the system.
Update This Update Use Case is going to help Super Admin and the System
Admin to update the User Profile as they change
Payment Collection Payment is going to be collected from the Users. This is going to
collect full payment altogether for fixed customers
Parking charges
collection
The charges are collected from the daily basis
Parking Assigning This is going to find out the Parking space and then help in finding out
the Parking space that could be assigned
System Handling The system handling is Use Case that could help Collin Car Parking
System operator to efficiently Manage the data system
Send Notification This use case is going to send the notification whenever any kind of
unauthorised access is done
Send Instructions This will use to turn On or Off that Notification
Payment Details This Use Case is going to show all the details of payment on the
system
Payment method This Use case is going to show the Payment method like Paypal, Card
or Cash
Detect Risk This Use Case will help in detecting all the risks associated with the
System and Payment modules

Register This Use Case is going to help in registering the customers on the
system using several security questions
Check Available
Space
This Use Case is going to help in checking the Available Space for the
Parking the cars
Verify Receipt This will help in verifying the receipts of that are generated for the
Payment
Profile Update The Profile Update use Case is going to help in updating any minute
detail of the Customer
Manage Users The Users are Going to be Managed by the System Admin via this Use
Case
Manage
Applications
The Applications within the parking System is going to be Managed by
the help of this Use Case
Manage Parking
Spaces
By this Use Case, all the Parking System spaces are going to be
managed
Manage Parked
Cars
Using this the parked Cars within the parking area can be managed
Manage Parking
Receipts
This Use Case is going to help in managing the Parking Receipts all the
Cars that are parked
Manage Car
Owners
The respective Car Owners are going to be managed by this Use Case
Diagram

Task 4: Class Diagram
Figure 4 represents the Class Diagram of the Collin Car Parking system. The Class Diagram is
going to help in finding out the static structure of the Collin Car Parking System. It shows the
system classes with the attributes and that further includes the methods and also the
relationship between all the objects. The Class Diagram is going to help in finding a sustainable
Structure by which the system design could be implemented. Also, the class diagram is going to
help in finding all the relevant data that is present in the system (Chen, 2013).
Figure 4: Class Diagram
Class Diagram is the Diagram that could be used to being the making of the system, by using the
class diagram the real-time entity of the system could be depicted further, the class diagram is
going to be helpful in creating a full system description by which could be implemented in a
logical manner (Zhdanov, Klimov, Korolev & Utemov, 2008).
In Figure 4, the superclass is the Permission Class. That Class is going to be used for setting all
the permissions. The Class Diagram that was made in the previous task was an elaborated
version of this class diagram. Also, this Class Diagram is the First Cut diagram meaning that this
diagram does not provide any kind of relationship between the Classes. Further, this class
diagram will help in deciding the function call and also helps in creating a datatype that could
be used as a part by which the system model could be briefly defined.

Task 5: Sequence Diagram
Customer Login Sequence Diagram
Figure 5: Customer Login Sequence Diagram
Table 2: Table for Customer Login Sequence Diagram
Message Description
Login to Page The Customer request to login to the Page or
the system
Forget Password I customer does not know the password this
process is called
Run into Administrator Password is run into the system as an
administrator
Security Question Security Questions are asked to verify user
Verify details Details are verified by the from the database
Validation of Details Verification process for the database
Store Values in Database Values are stored into the database
Allow user to Access, using the token and
session
User can access the data using the token for
a specific session

Send email for password reset An email is sent for resetting the password
Invalid login details If the login details are invalid then it is
popped up
Authenticate the users to access page After verification, the person is authenticated
Destroy session details Login details are destroyed for the particular
session
Login Successful The user is logged out from the system
Admin authentication and User Update Sequence Diagram
Figure 6: Admin authentication and User Update Sequence Diagram

Table 3: Table for Admin authentication and User Update Sequence Diagram Description
Message Description
Enter ID and Password The Admin enters ID and Password
Verify ID and Password The ID and Password is verified by the system
Ack An Acknowledgement is sent to the System
by the Database
Display Admin Page Admin Page is Displayed
Check Users Admin Check the user on the detail page
Get User Details system get the user details from the
Database
Send Reply The acknowledgement is sent to the System
by the database
Display Details The System display details to the admin
Update User The user request is sent to the system by
admin
Update User The update request is sent by the system to
the database
Update User The database is updated for the user
Success or Fail The update result is sent as Fail or Success
Display Result The System Display the result to the Admin

Car Parking Sequence Diagram
Figure 7: Car Parking Sequence Diagram

Table 4: Sequence Diagram Description
Message Description
Request for parking Car requests for parking for opening gates
Vehicle Verification Operator verifies the vehicle
Car Inspection Operator inspects the car
Access for details Operator access the database
Details send Database send the details to operator
Verify Details Operator verify the details of the car
Ack The acknowledgement is sent
Create Log entry Operator creates the log entry in the
database
Create Session The database creates a session for a car
Instruction The instruction is sent to the System
regarding the car
Check User Type The System checks the user type
Space Details The system checks the space details
Save Details The details are saved within the database
Send Instruction Database sent an instruction to the Operator
regarding the cars
Open Gates Operator opens the gate
Park Car The car is parked

References
Abidi, S., Krichen, S., Alba, E., & Molina, J. (2015). A New Heuristic for Solving the Parking
Assignment Problem. Procedia Computer Science, 60, 312-321.
http://dx.doi.org/10.1016/j.procs.2015.08.132
Wang, W., Song, Y., Zhang, J., & Deng, H. (2014). Automatic parking of vehicles: A review of
literatures. International Journal Of Automotive Technology, 15(6), 967-978.
http://dx.doi.org/10.1007/s12239-014-0102-y
Zhdanov, A., Klimov, D., Korolev, V., & Utemov, A. (2008). Modeling parallel parking a
car. Journal Of Computer And Systems Sciences International, 47(6), 907-917. doi:
10.1134/s1064230708060063
Chen, J. (2013). First-Cut DCD ( Class Diagram (UML)) | Creately. Retrieved from
https://creately.com/diagram/example/ha0fpedh1/first-cut%20dcd