ITC508 Object Modeling: Elaboration Phase of Collin Car Parking System

This report elaborates on the Collin Car Parking System project, building upon the initial inspection phase. It identifies and analyzes functional and non-functional requirements, including data network capabilities, parking space monitoring, and user interface features. The report also presents UML diagrams, specifically use case and class diagrams, to visualize system processes and real-world objects. The system design section outlines the Waterfall model chosen for development, describing the environment and key design activities. Assumptions regarding customer accounts, parking types, and system updates are also outlined. Desklib provides access to past papers and solved assignments like this to aid students in their studies.

ITC 508 – Object Modelling
Assignment 2
Elaboration Phase
Student Name: Shrikar Reddy Pinninti
Student ID: 11611714

Table of Contents
Introduction.................................................................................................................................................3
Requirement Identification.........................................................................................................................4
Functional Requirements:.......................................................................................................................4
Non-Functional Requirements:................................................................................................................5
UML Diagrams for Collin Car Parking System..............................................................................................6
USE CASE DIAGRAM................................................................................................................................6
CLASS DIAGRAM....................................................................................................................................11
System Design...........................................................................................................................................13
Conclusion.................................................................................................................................................16
LIST OF FIGURES
FIGURE 1: SUBSYSTEM DIAGRAM FOR COLLIN CAR PARKING SYSTEM.........................................................................................6
FIGURE 2: USE CASE DIAGRAM FOR COLLIN CAR PARKING SYSTEM............................................................................................7
FIGURE 3: CLASS DIAGRAM FOR COLLIN CAR PARKING SYSTEM...............................................................................................11
FIGURE 4: BRIEF DESCRIPTION OF THE SYSTEM ENVIRONMENT.................................................................................................14
LIST OF TABLE
TABLE 1: USE CASE DESCRIPTION........................................................................................................................................8
TABLE 2: USE CASE SYSTEM DESCRIPTION...........................................................................................................................10

Introduction
This report is an addendum to the work formerly done as Inspection Phase in Assignment 1. Further, in
Assignment 1 we had chosen a Case Study that was Collins Car Parking System and overall Inspection
was done previously. In this report, we are going to Elaborate the work done in Assignment 1. This
report will further help Collin’s by improving those features that were not properly identified or poorly
identified.
To Elaborate the City Administration about the project this report will work upon finding main
Functional and Non-Functional Requirements for the major areas of the project. All the requirements
will be studied and a list is maintained for each requirement by critical analysis. After that Use Case
Diagram is made for the system for the better implementation and process flow identification. It will be
followed by Class Diagram that will help in identification of the real-life objects that are present in the
system. Both of these UML Diagrams are explained for viable Implementation. These diagrams will be
based on the assumptions that are espoused from the Assignment 1. SDLC for this task is also designed
and listed briefly on various design activities that will explain various task and phases for the Collin Car
Parking System (Faheem, Mahmud, Khan, Rahman & Zafar, 2013).

Requirement Identification
Functional Requirements:
Data Network
 The Collin Car Parking System must transmit data to the UI of the subsystem monitoring system
after every 30 seconds.
 The Collin Car Parking System must receive data at a constant rate from the Subsystem
Monitoring System installed in the parking space.
 The Collin Car Parking System must be able to send a regular update to the customer those who
park car here.
 The Collin Car Parking System must be able to collect Parking information and should be able to
store it efficiently in the system database for every parking space used or unused in the building
at an interval of 30 seconds for at least a year.
 The Collin Car Parking System should be able to transfer data to any external device from the
Data Network.
 The Collin Car Parking System must print and display the record stored on the network.
 The Collin Car Parking System should be able to provide proper security for the Data Network to
maintain the integrity of the overall system.
 The Collin Car Parking System should be able to send notifications to the Parking Authorities
about the collected data consists of loading zones and fire lines.
 The Collin Car Parking System should be able to send a broadcast signal to all nearby devices tell
them space availability.
Monitoring of Parking Space
 The Collin Car Parking System should detect if all of the parking spaces are occupied and send
this report to the external participants.
 The Collin Car Parking System should detect if any parking space within the parking area is
unoccupied and send this report to the external participants.
 The Collin Car Parking System Should detect if parking space loading zones and fire lanes are
occupied and send this report to the external participants.
User Interface
 The Collin Car Parking System should provide all the customers with the best criteria
mechanism for electing out parking space.
 The Collin Car Parking System should display receipts.
 The Collin Car Parking System should display the plan used by the customer.
 The Collin Car Parking System should provide an accessible source by which the customer does
not have to leave the automobile.
 The Collin Car Parking System should provide customer to get the on-demand parking space
information.
 The Collin Car Parking System should provide monitoring abilities to the operator for
determining the overall state of the parking state including at present parking space.

 The Collin Car Parking System should provide flag parking option to the on-duty operator using
which the unavailable spaces that are falsely displayed as available are flag as occupied.
 The Collin Car Parking System should be able to print receipts for the customer including Daily,
Weekly, Monthly, Quarterly and Annual charges with parking space usage.
 The Collin Car Parking System should be able to provide an output that could be customized by
the operator.
 The Collin Car Parking System should be able to provide 24x7 availability to the users.
 The Collin Car Parking System should be internet accessible (Eriksson, 2012).
Non-Functional Requirements:
Performance
 The Collin Car Parking System should be able to update whole parking space in a continuous
span of 30 seconds (it will use an optimized Scheduling Algorithm).
 The Collin Car Parking System should provide customers with the most updated parking space
information.
 The Collin Car Parking System should send response message to their registered devices within a
fixed time limit (It does not control Network delays or Internet or Mobile Devices).
Reliability:
 The Collin Car Parking System must be reliable. Reliability of Collin Car Parking System can be
defined as the “whenever a user request for any kind of information the like Parking Space they
should get the correct information that should be up to date”. For Collin Car Parking System, the
information needed by the user is accurate and reliable when the Information is processed
under 30 Seconds. If the information gets old, it is discarded.
Maintainability:
 The Collin Car Parking System should not need to require higher maintenance time per se.
 The Annual maintenance should not be more than 7-10 days for the Collin Car Parking System
Environmental:
 The Collin Car Parking System should not be harmful to the users or the operators
 The Collin Car Parking System should not cause any kind of jitter in the external networks
(Eriksson, 2012).

UML Diagrams for Collin Car Parking System
USE CASE DIAGRAM
Figure 1: Subsystem Diagram for Collin Car Parking System

Figure 2: Use Case Diagram for Collin Car Parking System

Table 1: Use Case Description
Use Case Description
Manage User This is a Super Admin Use Case for Managing all of the User within the
Parking System
Manage
Application
This is a Super Admin Use Case that enables Super Admin to Manage the
overall application of the Parking System
Manage
Parking Space
This Use Case Feature enables the Super Admin to Manage Parking
Space
Manage
Parked Cars
This Use Case will give the Super Admin a feature to Manage all those
cars that are parked within
Manage Car
Owner
This Use Case is mainly for System Admin but it can also be used by the
Super Admin for managing all Car Owner that are in the System
Database
Manage
Parking
Receipts
This Use Case is used by System Admin and the Super Admin in order to
manage all the Parking Receipts of the car parked by the customer
Search
Parking Space
This Use Case is used by the Customer for the Searching the Parking
Space available to Park Cars
Parking Space
Allocation
This Use Case will be used by the Customer when they got the Parking
Space Allocated to them
Check receipts This Use Case will print out the receipts for the duration for which the
cars were parked
Payment
Collection
It is a Use Case used by the Operator for Payment collection. It could be
either Card or Cash
Parking
Charges
Calculation
This Use Case will be used by the Operator for calculating the parking
fare for every car parked
Parking
Assigning
This Use Case is used by the Operator for Assigning the Parking for every
incoming Car

System
Handling
Regular Check-up by the Operator to ensure that system is up and
running
Login Logout It will provide all Actors within the system to Login into the system for
working and after that Logout, once their job is finished
Update Profile This Use Case will enable all of the Actors within the system to make
changes to their profile
Password
Change
All the Actors except customer have to change their password every 30
days

Table 2: Use Case System Description
Use case name Collin Car Parking System
Scenario A car enters the parking system looking for the parking space and then a parking
space will be found out by the operator for the Car
Triggering
Event
Car Enters the Parking System for Parking
Stakeholders Company Staff, System Administrator, Dedicated Engineers, Security Consultant,
Customer Type
Brief
Description
Parking will be searched for the available Parking Space
Precondition Car Owner Drives the Car to the parking system
Postcondition Car Owner will get the Receipt and that record will be maintained by the Operator
within the system
Flow of activity ACTION SYSTEM
1. User Drives into the Car
Parking
1. Recognize the customer
2. User Login 2. System will Validate the
Customer account associated
with that Account and
authenticate
3. Customer will wait for
parking allocation
3. System will measure the
Dimensions of the car
4. Reorganization of the
Number Plate
4. System will identify the
Vehicle for that Parking Space
5. Entrance into the Parking
System
5. Passengers leave their
respective car
6. Car Parking Procedure 6. System will start the Car
Parking Procedure
7. Parking the Car 7. System stores car in the
respective Parking Space
Exception
condition
 Account not validated
 Session Expired

 No Parking Space
 No Shaded Parking Space
 Communication Failure due to Bandwidth
 Parking System not available due to Maintenance
CLASS DIAGRAM
Figure 3: Class Diagram for Collin Car Parking System

Description
 The Parked cars will be secured because all of them are parked away from public access
 Parking Damage like Scratch and Dent could be avoided
 The Collin Car Parking System will be highly useful for the Handicap people
 One or More operator will always be there for the System monitoring
 Security of Parking System is designed in such a way that there might not be any kind of damage
to the car parked within the system
 Customer can reserve a Parking spot
 Customer will get an allocated time after that the charges can vary from the expected charges
 No Need to provide a Top notch ventilation System
 It could be constructed very fast
 Drivers and the passengers have to worry about walking in and then parking
 No need to search for Parking Space
 Minimal time needed for the Maintenance
 Various types of account can be created by the Customer according to their Feasibility
 Each Parking slot consists of Several different types of sensor
Assumptions Taken
 Customer has an account in the Collin Car Parking System Database
 Customer Could be any type. Example a Private Parking Spot owner, when one-time Parking
Space needed, Periodical Customer, New Customer
 No limit of time for Private Parking Spot Owner
 User need the space for a specific amount of time
 Every Customer will pay the receipts for the parking
 System will be updated every week for security and reliability
 Car would be of Standard type