Online Parking Management System

Design Document

Version 1.0

Group Id: S160209DAE

Supervisor Name: Noor Rahman

 Revision History
Date Version Description Author
(dd/mm/yyyy)
Design Document MC 120402082
21-09-2016 1.0
Introduction to Design Phase, Muhammad Imran
Entity relationship Diagram(ERD),
Sequence Diagrams, Architecture
Design Diagram, Class Diagram,
Database Design, Interface Design,
Test Cases
 Table of Contents

1. Introduction of Design Document

2. Entity Relationship Diagram (ERD)

3. Sequence Diagrams

4. Architecture Design Diagram

5. Class Diagram

6. Database Design

7. Interface Design

8. Test Cases
 1. Introduction of Design Document

Analysis and design phase are extracted from Software Development Life Cycle (SDLC). The
analysis phase involves gathers requirements and resources of system according to users and makes
relevant system. In analysis section, it addresses security consideration. Key activities for this phase
include:
Conduct the risk assessment;
Analyze security requirements;
Perform functional and security test;

Design phase must be user friendly. Design phase refers to the correctness of your system. Analysis
are mold into design phase later. Design of the system must be detailed. Physical design and its
correlation to graphical user interface must be good. Design of the system must be detailed.

This document describes the process followed for Detailed Analysis and Design Phase of the Project
Online Parking Management System (OPMS). It provides the programmer with enough information
to successfully code all the modules and functions necessary in delivering the Online Parking
Management System (OPMS) application.

This document provides a comprehensive architectural overview of Online Parking Management

System (OPMS), using a number of different architectural views to depict different aspects of the
system. It is intended to capture and convey the significant architectural decisions which have been
made on the system.
Using this document, during Detailed Analysis and Design Phase it becomes easy to understand and
work on the project by getting following views and aspects of project:

Entity Relationship Diagram.

Sequence diagrams.
Architectural Diagram of the system.
Class Diagram.
Database Design.
Interface Design.
Test Cases.

2. Entity Relationship Diagram (ERD)

Following is the ERD of the Proposed System

3. Sequence Diagrams

User Tasks:

User Login:
Add user Info.
Add Vehicle Info

View Parking

Space:
Check Availability:

Booked Parking:
Send SMS/E-mail:
Payment:
Generate Bill:

Admin Tasks:
Admin Login:

Add user:
Edit User:

Delete

User:
4. Architecture Design Diagram
5. Class Diagram
6. Database Design
 7. Interface Design

Log in for Admin:

Log in for User:
Add Parking Detail:
Search Vehicle:
 8. Test Cases

Test Case # 1 Testing for log in for Administrator.

Preconditions The Application is run on system successfully.
Actions 1. The Admin enters the user name.
2. The Admin enters the password.
3. The user hits the log in button.
 4. The user is logged in and the welcome statement and the main menu
appear. (in case of entering incorrect user name or password the system
displays the message Invalid username or password)
5. Use case ends.
Expected The Admin is logged in.
Results
Tested By Muhammad Imran
Results Pass.

Test Case # 2 Testing for log in for User.

Preconditions The Application is run on system successfully.
Actions 1. The User enters the user name.
2. The User enters the password.
3. The user hits the log in button.
4. The user is logged in and the welcome statement and the main
menu appear. (in case of entering incorrect user name or
password the system displays the message Invalid username or
password)
5. Use case ends.
Expected Results The User is logged in.
Tested By Muhammad Imran
Results Pass.

Test Case # 3 Testing for add parking area.

Preconditions The User login to system successfully.
Actions 1. The User enters the name of the location.
2. The User enters the location of the parking.
3. The user hits the Add Parking button.
4. The Parking added successfully. (if there is no location of
parking defines the system shows a warning message)
5. Use case ends.
Expected Results The location of Parking area added successfully.
Tested By Muhammad Imran
Results Pass.
Test Case # 4 Testing for add Parking Space.
Preconditions The parking area added successfully.
Actions 1. The User enters the parking space.
2. The User enters date of the parking.
3. The User enters date of leave parking.
4. The user hits the Add button.
5. The parking space added successfully. (If there is no parking
space defines then the system shows a warning message).
6. Use case ends.
Expected Results The route added successfully.
Tested By Muhammad Imran
Results Pass.

Test Case # 5 Testing for manage parking space.

Preconditions The parking space defines successfully.
Actions 1. To Edit parking space and enters parking space information
again user hits Edit button.
2. To delete the parking space the user hits the Delete button.
3. The parking space added/manage successfully. (If there is no
parking space defines then the system shows a warning
message).
4. Use case ends.
Expected Results The route added/manage successfully.
Tested By Muhammad Imran
Results Pass.

Test Case # 6 Testing for manage parking space.

Preconditions The parking space defines successfully.
Actions 1. To Edit parking space and enters parking space information
again user hits Edit button.
2. To delete the parking space the user hits the Delete button.
3. The parking space added/manage successfully. (If there is no
parking space defines then the system shows a warning
message).
4. Use case ends.
Expected Results The route added/manage successfully.
Tested By Muhammad Imran
Results Pass.
Test Case # 7 Testing for add users personal information.
Preconditions The user login to the system successfully.
Actions 1. The User enters his/her name.
2. The User enters his/her cnic no.
3. The User enters his/her address.
4. The User enters his/her license no.
5. The User enters his/her contact no. or E-mail.
6. The User adds his/her vehicle information if he/she has personal
vehicle.
7. The Users personal information added successfully. (This users
information is necessary. If there is no information then system
shows an error message).
8. Use case ends.
Expected Results The Users personal information added successfully.
Tested By Muhammad Imran
Results Pass.

Test Case # 8 Testing for add Vehicle Info.

Preconditions The User login to system successfully.
Actions 1. The User enters the Vehicle No.
2. The User enters the Vehicle Model.
3. The User enters Vehicle Made.
4. The User enters Vehicle Company.
5. The user hits the Add Vehicle button.
6. The Vehicle Info added successfully. (if there is no vehicle info
defines the system shows a warning message)
7. Use case ends.
Expected Results The Vehicle Information added successfully.
Tested By Muhammad Imran
Results Pass.

Test Case # 8 Testing for Payment.

Preconditions The User login to system successfully.
The Parking Space and Parking is defined successfully.
Actions 1. The User Choose the payment method.
2. The User Choose between credit card and online payment.
3. The user hits the Add payment button.
4. The payment is done successfully. (if there is no payment the
system shows a warning message)
5. Use case ends.
Expected Results The Vehicle Information added successfully.
Tested By Muhammad Imran
Results Pass.

Test Case # 10 Testing for add/manage users.

Preconditions The Admin login to the system successfully.
Actions 1. The Admin adds a new user by hitting Add new user button.
2. The Admin Update a user by hitting Edit User button.
3. The Admin delete a user by hitting Delete user button.
4. To information provided to the user is in encoded form. The
Admin does not view the users personal information.
5. The Admin manages the application. (If the Admin add, update
or delete the defined user then the system shows a corresponding
message).
6. Use case ends.
Expected Results Admin manages the users successfully.
Tested By Muhammad Imran
Results Pass.

The End