Collin’s Parking Car Park System: UML Design and Object Modelling

This report provides a detailed architecture and design for the Collin’s Parking Car Park System, covering functional and non-functional requirements, UML use case diagrams, a domain model class diagram, and specific design activities. It identifies key functional requirements such as parking guidance, entry/exit management, payment processing, security features, and mobile app booking, along with non-functional requirements like fault tolerance, usability, reliability, performance, and security. The UML use case model includes scenarios for ordinary and fixed customers, detailing processes like reservation, parking, account management, and billing. The domain model class diagram illustrates the relationships between various system components. The design activities cover environment setup, application components, user interfaces, database design, and software classes methods, ensuring a comprehensive approach to system development following the SDLC methodology.

Running head: OBJECT MODELLING
Object Modelling: Collin’s Parking Car Park System
Name of the Student
Name of the University
Author’s Note

1
OBJECT MODELLING
Table of Contents
1. Functional and Non Functional Requirements............................................................................2
1.1. Functional Requirement........................................................................................................2
1.2. Non Functional Requirement................................................................................................3
2. UML use case..............................................................................................................................5
2.1. Brief use case description.....................................................................................................6
2.2. Fully Developed use case description...................................................................................9
3. UML Domain Model Class Diagram.......................................................................................11
4. Specific task required for the design activity............................................................................11
4.1. Environment.......................................................................................................................11
4.2. Application Component......................................................................................................12
4.3. User Interfaces....................................................................................................................12
4.4. Database..............................................................................................................................13
4.5. Software Classes Methods..................................................................................................13
Bibliography..................................................................................................................................16

2
OBJECT MODELLING
1. Functional and Non Functional Requirements
1.1. Functional Requirement
1. Main Control -
1.1. Parking guidance
1.2. Parking counter system
1.3. Parking space protector system
1.4. Software management system
2. Entry and Exit Management –
2.1. Automated card reader
2.2. Automatic ticket generator
2.3. Monthly card reader
2.4. Automatic number plate recognition
2.5. Talk back functionality
2.6. Barrier opening software
3. Payment –
3.1. Postpaid parking
3.2. Prepaid parking
3.3. Temporary Parking

3
OBJECT MODELLING
3.4. Cash and Billing management
3.5. Customer account management
4. Security
4.1. Parking space detection
4.2. Embedded system and sensor network
4.3. Image processing and intelligent space detection
5. Mobile App Booking –
5.1. Creation of simple user interface
5.2. Securing the database of the application
5.3. Management of the User account
5.4. Enabling cross platform support
1.2. Non Functional Requirement
Fault tolerance – The inputs of the users and the user interaction should be remembered
if there is an interruption between the user and the system. The information system should also
be able to recover from its malfunction quickly and respond to the users.
Usability – All the relevant use cases should be accessed by the customer with less
navigation and the user must not feel redirected.
Reliability – The information should return the accurate values based on the query of the
customer and error message should be displayed on wrong inputs. The data in the database

4
OBJECT MODELLING
should not be loosed during backup and migration for keeping all the details of the entries and
details of the users.
Performance – the output displayed to the customer should be accurate and the time
required for connecting with the database should be kept minimum such that the waiting time to
get the message is minimum. The support for the customer should increase with the increase in
the demand with the application of virtualization and cloud storage options that can be integrated
for increasing the scalability of the current information system.
Security – An authorization should be used for accessing the information system and the
details of the customer and the reservation details should not be accessed by the unauthorized
users for increasing the security the car parking information system. The footage generated from
the CCTV should be stored in local storage for monitoring the activity of the users of the car
parking system and use as an evidence for handling the emergency conditions.

5
OBJECT MODELLING
2. UML use case
Figure 1: use case for ordinary Customers

6
OBJECT MODELLING
Figure 2: use case for Fixed Customers
2.1. Brief use case description
Use case 1- reserve
The fixed customer can reserve their parking space and they needs to authenticate and
input their details such ad date and time, registration number of the vehicle, length of stay and
submit the details. The validation of the information would be done on the system end for
creating reservation, data storage in the information system.

7
OBJECT MODELLING
Use case 2 – Parking
When the user approaches to the entry barrier the camera reads the license plate and the
database is searched to find if the customer is a fixed customer. The fixed spot details are
displayed to the fixed customer and if the customer is not registered the empty spot details are
displayed and a spot is allocated to the user. If the license plate is not recognized the user is
provided the option to manually input their registration number and use the information system.
Use case 2 – manage Account
The details of the accounts can be updated by the user and for that the user need to
connect with the information by authentication with their old details.
Use Case 3 – View Reservation
The existing spots allocated to the fixed users can be changed by authenticating into the
user account and finding the free spots available in the system. The edit option is used as a sub
case.
Use Case 4 – Register
It is used by the unregistered users for registering with the current parking system. The
user needs to fill a registration form for registering with the information system
Use case 5 – manage parking
The current usage history, available wallet balance, parking prices can be viewed by the
user by connecting with the application and logging into the account.
Use case 6 – Edit reservation

8
OBJECT MODELLING
For canceling the registration or editing the data and time of reservation the user needs to
edit the details 30 minutes before the actual time starts
Use case 7 – register vehicle
This is used for registering another vehicle with the account of the customer and the user
needs to fill a form and submit is for recording the details of the vehicle in the information
system.
Use case 8 – Edit vehicle details
The registered user can edit the details of their vehicle after authenticating into the
information system.
Use case 9 – Authenticate user
The accounts for the fixed customer are created and they needs to use their registered
email ID and password for logging into the system. The details are fetched from the database and
a new session is created for the user to maintaining the access to the information system.
Use case 10 – Set price
A tariff plan is followed and is displayed to the customer for choosing the best plan
according to the needs of the customer.
Use case 11 – inspect usage history
The system administrator is able to view the history of the usage and needs to
authenticate with the system for gathering the data and create a statistics of the usage.
Use case 12 – Monthly billing

9
OBJECT MODELLING
The details of the fixed customer are analyzed and all the reservations that are not
cancelled are identified and a bill is generated for the customer and sent via emails.
2.2. Fully Developed use case description
Use case 2 Parking
Actor Fixed users, normal users
Goals of the actor To park the vehicle
Participating actor Display, Entry Camera, keypad, spot sensor,
exit camera and database.
Precondition The entry point is empty
Post Condition A parking space is allocated and the database
is updated.
Flow of Events for the main successor
1. User approaches the barrier installed at the entry point
2. The camera installed in the barrier detects the license plate of the vehicle
3. The display at the entry point displays the details of the reservation by fetching details
from the database
4. The reservation is selected by the user
5. A parking spot is assigned and the route is displayed on the display.
6. User exits the parking system
7. The spot sensors sends message to the information system that the space is occupied
8. The database is updated and the space is no longer used for allocation to other user
Flow of event for extension

10
OBJECT MODELLING
1. The camera at the entry point fails to scan the vehicle number plate
1.1. The display prompts the user to enter their type such as fixed or normal user
1.1.1. The fixed user enters ID, password and the registration number for
authorizing into the information system.
Entry barrier keypad
1.1.2. Authentication of the user
1.1.3. The credit card of the customer is shared for payment.
1.1.4. A proper message is displayed to the customer.
1.2. The fixed customer arrives at the entry barrier prior to the timing
1.2.1. The customer is treated as a normal customer
1.2.2. The parking space is checked for availability and if it is available then
allocated to the user and if not available then the customer needs to change
their parking space.
1.3. The user does not having fixed reservation
1.3.1. A prompt message is displayed to get the length of reservation form the
user.
1.3.2. The user interface and the keyboard is used for inputting the values in the
information system.

11
OBJECT MODELLING
3. UML Domain Model Class Diagram
4. Specific task required for the design activity
4.1. Environment
For the development of the Collins car parking system and software development
environment should be created following the software development methodology such as Agile
or waterfall models. The main elements required for the creation of the environment is the
development of a communication plan for maintaining communication with the external systems.
A message format should be used and a set of communication protocol should be used for
communicating with the stakeholders associated with the development of the car parking system.

12
OBJECT MODELLING
Some security methodology should be applied for detection of the errors and maintain a recovery
mechanism for confirming the application of the new technology for the development of the
Collins parking car parking system.
4.2. Application Component
This are the elements that are used for defining a software program for performing some
specific function. The components consists of the scope and size of the functions, interfaces and
the boundaries of the system. The accepted programming language that can be used for the
configuration of the information system should also be analyzed for starting the development
process. The components and the additional that are required to be purchased in order to develop
the car parking system should be listed and integrated with each other during the development
process for reducing the errors in the final build information system.
4.3. User Interfaces
An user interface should be designed with the company’s logo and the it should be kept
same for the entry barrier and the mobile application designed for the Collins car parking system.
The user interface plays an important role for the productivity and the success of the network and
it is required to analyze the user requirement for designing the user interface for the system. All
the functionalities and options should be available to the user and the involvement of the user in
the development process can reduce the errors in the project. According to the current needs of
the system multiple user interface should be developed for different devices such that it can
fulfill the different needs of the customers using the car parking system.

13
OBJECT MODELLING
4.4. Database
The database of the information system designed for collin’s car parking system should
be developed for storing the data generated from the activity of the users and provide the users
the result of their query. The use of relational database management system can be an ideal
choice for the organization and for this there is a requirement to convert the data model of the car
parking system into the relational database. The different issues generated during the
development of the data model should be addressed for reducing the errors in the database and
management of the throughput and the response time of the database. The security of the
database should be at the high level such that the data cannot be retrieved by any unauthorized
users and the information’s are kept secured.
4.5. Software Classes Methods
The software methodology for the development of the car parking system includes the
creation of design class diagrams, state machine diagrams and sequence diagrams. The Collins
car parking system is developed following the software development lifecycle methodology. The
different phases of the SDLC model should be followed for the development of an error free car
parking system. The five phases of the SDLC model are the planning, analysis, design,
implementation and maintenance.
The planning phase is used for the requirement analysis and different procedure such as
brainstorming with the development team and the using a set of questionnaires for interviewing
the stakeholders can be used. It is important to create an initial project plan and analyze the
resource required for the development of the project.

14
OBJECT MODELLING
The analysis phase is used for the identification of the cost and the hardware required for
the development of the information system. The errors generated in the system should be
identified and it should be removed for the development of the project. The codes and programs
used for the configuration of the devices installed in the network of the car parking system
should be checked before deployment and the errors in the codes should be identified such that
the car parking system is fully functional and no errors should be generated during the day to day
activity.
A preliminary design of the car parking system should be developed for the installation of
the sensors, entry and exit barrier and the servers for connecting with each other. The creation of
a dmz zone helps in securing the servers from physical access and secure the information
residing in the servers. The hardware and software required for the development of the
information system should be identified for the creation of the design of the car parking system.
The design plan should be followed in the implementation phase and servers and the
elements should be recorded for the integration with the module and maintain a continuous
operation for serving the users. The integration of the modules helps in identification of the
errors at the early stage of the development and helps thee development team to deliver a quality
software product by reducing the errors in the system. The implementation phase takes longer
time than the development phase because different modules are required to be integrated with
each other for interoperability and eliminating the risk associated with the development of the
project.
The maintenance phase consists of the different types of services such as database
maintenance, updating the operating system and application of patches for removing the flaws in

15
OBJECT MODELLING
the current system. The permission for accessing the resources are also managed in this phase
according to the changes in the needs of the car parking system.

16
OBJECT MODELLING
Bibliography
Akkaya, I., Derler, P., Emoto, S., & Lee, E. A. (2016). Systems engineering for industrial cyber–
physical systems using aspects. Proceedings of the IEEE, 104(5), 997-1012.
Buede, D. M., & Miller, W. D. (2016). The engineering design of systems: models and methods.
John Wiley & Sons.
Coruhlu, Y. E., & Yildiz, O. (2017). Geographical database for object-oriented land division
modelling in Turkey. Land use policy, 68, 212-221.
De Giacomo, G., Oriol, X., Estanol, M., & Teniente, E. (2017, June). Linking data and BPMN
processes to achieve executable models. In International Conference on Advanced
Information Systems Engineering (pp. 612-628). Springer, Cham.
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Dick, J., Hull, E., & Jackson, K. (2017). Requirements engineering. Springer.
Grönninger, H., Krahn, H., Rumpe, B., Schindler, M., & Völkel, S. (2014). Textbased
modeling. arXiv preprint arXiv:1409.6623.
Hanandeh, F. A., Alsmadi, I., Al-Shannag, M. Y., & Al-Daoud, E. (2015). Mobile agents
modelling using UML. International Journal of Business Information Systems, 19(4),
419-432.
Hilken, F., Niemann, P., Gogolla, M., & Wille, R. (2015, July). From UML/OCL to Base
Models: Transformation Concepts for Generic Validation and Verification.

17
OBJECT MODELLING
In International Conference on Theory and Practice of Model Transformations(pp. 149-
165). Springer, Cham.
Knapp, A., Mossakowski, T., & Roggenbach, M. (2015). Towards an Institutional Framework
for Heterogeneous Formal Development in UML. In Software, Services, and Systems (pp.
215-230). Springer, Cham.
Przigoda, N., Soeken, M., Wille, R., & Drechsler, R. (2016). Verifying the structure and
behavior in UML/OCL models using satisfiability solvers. IET Cyber-Physical Systems:
Theory & Applications, 1(1), 49-59.
Razik, L., Mirz, M., Knibbe, D., Lankes, S., & Monti, A. (2018). Automated deserializer
generation from CIM ontologies: CIM $ ${+}{+} $ $—an easy-to-use and automated
adaptable open-source library for object deserialization in C $ ${+}{+} $ $ from
documents based on user-specified UML models following the Common Information
Model (CIM) standards for the energy sector. Computer Science-Research and
Development, 33(1-2), 93-103.
Rumpe, B. (2014). Executable Modeling with UML. A Vision or a Nightmare?. arXiv preprint
arXiv:1409.6597.
Seidl, M., Scholz, M., Huemer, C., & Kappel, G. (2015). UML@ classroom: An introduction to
object-oriented modeling. Springer.
Thramboulidis, K., & Christoulakis, F. (2016). UML4IoT—A UML-based approach to exploit
IoT in cyber-physical manufacturing systems. Computers in Industry, 82, 259-272.

18
OBJECT MODELLING
Tolvanen, J. P., & Kelly, S. (2016, February). Model-Driven Development challenges and
solutions: Experiences with domain-specific modelling in industry. In Model-Driven
Engineering and Software Development (MODELSWARD), 2016 4th International
Conference on (pp. 711-719). IEEE.