Object and Data Modelling: Functional and Non-Functional Requirements, Use Case Modeling, UML Domain Model Class Diagram, Activities of SDLC

Running head: OBJECT AND DATA MODELLING
Object and Data Modelling
Name of the Student
Name of the University

1OBJECT AND DATA MODELLING
Table of Contents
1. Functional and Non-Functional Requirements: 2
1.1 Functional Requirements: 2
1.2 Non-Functional Requirements: 3
2. Use Case Modeling: 4
3. UML Domain Model Class Diagram: 8
Activities of SDLC: 9
Bibliography: 11

2OBJECT AND DATA MODELLING
1. Functional and Non-Functional Requirements:
1.1 Functional Requirements:
i. Message Showing: The system will need to show various messages and responses
to the customer request through the display, installed in the pillars. When the user
will appear at the pillar, the system will sense the presence of the car and show
relevant messages and options.
ii. Authentication: The authentication is process of verifying a user. The system will
read the ticket and retrieve the details from the database. If the ticket is valid then
only the customer will be authenticated to enter the parking area.
iii. Authorization: The authorization is the process of validating the user request. The
system will have various authorization levels which will separate the fixed
customer requests from the ordinary customer requests. All these authorizations
will be done within the core of the system. The customer identification will be
done using the ticket.
iv. Payment handle: The system will handle the payment process. In case of fixed
customers, the system will be taking all the charges for the ticket at the time of
generating. The card is provided to the ticket reader device and the payment will
be deducted. In case of ordinary customers, the system will calculate the charge
and the payment needs to be done through card or cash.
v. Report Generating: The system will be generating reports based on the stored
data and information. These reports can be accessed by the organization’s
executive management only. The system will create report weekly, monthly and

3OBJECT AND DATA MODELLING
yearly basis. This reports will be stored in the system for a long time so that it can
be available to the management for a long period.
vi. Data Storing: The system will collect input from the customer and various
hardware devices and store those input data into the system database. The data
storing will be done through various checks and validation processes.
1.2 Non-Functional Requirements:
i. Availability: The system will be available for providing service 24*7. The
customers can come to park their cars at any hour of the day. In order to maintain
the system availability, the organization will be appointing an expert to maintain
the system functionality.
ii. Recoverability: The system will be equipped with a disaster recovery technique.
In case all the data and the magnetic tapes are destroyed, the organization will be
able to collect all the data from the disaster recovery approach.
iii. Scalability: Scalability refers to the capability of the system coping with the
business requirements. The system will be using resources based on the frequency
of the car appearing. In order to boost the profit, the system will be generating
forecasting reports that will allow the management to identify when more
resources are required. Through proper scalability, the system will be ready for
providing services to the customer.
iv. Security: In modern world, securing an ICT system is a major factor. The system
will not be accepting any peripheral devices. This will any type direct injection of
viruses or Trojans. The system will be secured using three layered approach so
that no one can access the database unauthorized way.