Use Case Model Development And Requirements Gathering For Car Parking Management System

Use Case ID

Primary Actor

Use Cases

UC-1

Sensors

Detect Vehicles

UC-2

Sensors

License plate scan

UC-3

Car

Activate entry sensor

UC-4

Car

Activate exit sensor

Use Case ID:

UC-1

Use Case Name:

Detect Availability of the Parking space

Created By:

Enter your name and student ID

Date Created:

December 30, 2017

Actors:

The actors are divided into Primary and secondary actors.

Primary Actors –

· Sensors

· Camera

Secondary Actors  –

· Car

· Display

Description:

When the car enters the parking lot it activates the entry sensor and the other sensors connected in the network. The license plate is scanned by the micro sensor camera and information regarding the allotted parking space is stored in the database of the information system. Each of the parking space are installed with a micros sensor for sensing the free or occupied space and the information is updated in the database at a regular interval of time. The time of entry should also be recorded for the calculation of the time limit of each of the vehicles. The allocated space is checked and for getting the time limit of the parking space.

Trigger:

The micro camera sensor starts its working when the car enters the car parking system and acts as the main trigger event.

Preconditions:

The list of activities that takes place for starting the use case are as follows:

Step#1: The car approaches the barrier and enters the car parking lot

Step#2: A scanning is made on the available space of the car parking lot

Step#3: The micro sensor camera must be working and connected with the information system

Step#4: Space must be available on the database of the information system for recording the data.

Postconditions:

The micro camera sensor should be connected in the information system and when the car arrives at the parking space the information system should be updated at a real time from vacant to occupy. The car number plate is scanned and the details of the vehicle are added in the database. After valid authorization of the car the car can enter the car parking system. A message is displayed in the display screen with the entry time and the details of the car.

Normal Flow:

When the car approaches the barrier of the car parking system the micro sensor camera scans the number plate and stores it in the database along with the time. A message is displayed with the details of the car and the available parking space to the users. The car enters the parking lot and occupies the space and the database is updated. The sensors installed in the parking space senses the car and on expiry of the session sends message to the information system. At the exit barrier the information of the car is rechecked and matched with the information stored in the database for successful validation and the barrier is raised.

Alternative Flows:

[Alternative Flow 1 – Not in Network]

Closing the barrier if the data is not matched and rechecking the data for validation.

Exceptions:

If the micro sensor camera is defective it cannot detect the vehicle and would cause error such as miscalculation of the parking fees and showing occupied or free space to the new user entering the parking lot.

Error handling should be applied such as time of entry should be calculated again at the exit point and the space allocated should be checked for updating the information system.

Includes:

The use case includes the other use cases like observer abnormality for detection of the time limit of the parking space used by the vehicle and sending mail to the city council after every half an hour.

Frequency of Use:

The use case would be used during the entry of a vehicle into the parking lot for the allocation of the space to the vehicle i.e Once per entry of the vehicle

Special Requirements:

The requirement of the project can be classified into functional and non-functional requirements and given below:

Functional Requirement

Authorization –the lower level employees should not have the access of the information system

Payment – A payment option should be selected by the users for paying the parking fees and the user can exit the car parking system

Database – The database tables should be designed according to the requirement d should be protected from unauthorized access.

Non-Functional requirement

Scalability – The information should be designed to accept the changes in the business policy and control the exit and the entry points efficiently.

Performance – Large number of vehicles should be controlled automatically and the response time of the system should be kept minimum

Reliability – The data should be replicated and act according to the business rules set by the city council

Availability – The data residing in the database should be available all the time and the system should work efficiently during the working hours.

Assumptions:

For the development of the information system the following assumptions are made such as:

· The instruction and the display messages are shown in English and the user understand the language for using the information system

· The owner of the system uses authorization for using the system

· All the information of the vehicles are stored in the information system securely.

Notes and Issues:

If any of the sensors or cameras gets damaged the whole system would malfunction because the data generated from one of the sensors is used as an input for the next operation. For example if the parking space detector gets damaged the database would not get updated and the time limit and the empty space or vacant space of the parking would not be calculated and causes loss for the city council.