Object and Data Modeling: Collin’s Car Parking System

Running Head: OBJECT AND DATA MODELLING
Object and Data Modeling: Collin’s Car Parking System
Name of Student
Author’s Note

2
OBJECT AND DATA MODELLING
Table of Contents
1. Functional and Non-Functional Requirements:...........................................................................3
1.1. Functional Requirements:.....................................................................................................3
1.2 Non-functional Requirements:...............................................................................................4
2. Use Case Modeling:...................................................................................................................5
2.1. Brief use case description.........................................................................................................6
2.2. Fully Developed use case description...................................................................................8
Bibliography..................................................................................................................................13

3
OBJECT AND DATA MODELLING
1. Functional and Non-Functional Requirements:
1.1. Functional Requirements:
a. Message Displaying: This particular system will display different messages as well as
responses to customers throughout the display that is installed in pillars. Once user appears at
pillar, the sensor installed in particular system senses the presence of vehicles and display the
required messages as well as options.
b. Authentication: This is the process to verify a user by doing real time checking of ticket and
retrieving all types of details from their saved databases. Once the ticket validation is done,
customer will get authenticated to enter the parking lot.
c. Authorization: This the process to authorize the validation of the user request for the parking
area. The whole process is consists of different levels that also different for both fixed customers
and normal customers. The whole authorization process gets done from the core of any system.
The identification of customers will be done by doing the proper uses of issues ticket.
d. Handing of Payment: This particular system will also check the payment done. For some fixed
customers, the system takes all charges for ticket at a time of generation. The card will be
entered to ticket reader device and the exact payment gets deducted by calculating the parked
time. The payment of parking card can also be done by using debit/credit card or cash.
e. Report Generation: The system will generate reports retrieving their stored data and
information. This report can only be accessed by the management supervisors only. It also
generates report in all weekly basis, monthly as well as on yearly basis also. The report get
stored in the system for life time so that it can be checked any time.

4
OBJECT AND DATA MODELLING
f. Storage of Data: This particular system gets inputs from all customers and stored their inputted
data on the system database. The storage of data will be done after doing different levels of
authentication as well as validations.
1.2 Non-functional Requirements:
a. Availability: This automated system is available for 24*7 to provide services. The customer
can park their vehicles at any time of the day. To maintain the space availability, there will be an
appointed person who will look after any space related issues and functioning of system.
b. Recoverability: The system will also be outfitted with an effective disaster recovery technique.
In case of any data theft and data loss, the organization has the back-up plan to collect data with
the help of implemented data recovery technique.
c. Security: In today’s modernized world, securing the ICT system is one of the major concerns.
The system will not get accessed on any peripheral devices, because it can be any other types of
direct injection of any infected viruses. The system gets secured with three layers of approaches
which do not allows any un-authorized users to access the database system.
d. Scalability: With the scalability process, it mainly discusses about the capabilities of system to
get accompanied with the business requirements. It also discussed about the system which will
use the resource based on the speed of car appearing. In terms of gaining the profit, the system
also generates different forecasting reports that allow management to do identification of
resource required. With the help of appropriate scalability, the system gets ready to provide
better services to the customers.
e. Usability: The use of the installed system will be on its high quality. The customer will
perform all pre-determined tasks based on the instructions that appear of the display.