Object Modelling: Collin’s Parking Car Park System

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