Software Requirement

Specification
For
Automated Parking garage
system,
Vehicle Parking Management
System

1
CONTENTS

1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Overview 3
1.4 Definitions 4
2. General Description 5
2.1 Overview 5
2.2 Product perspective 6
2.3 Product Functions 6
2.4 User Characteristics 7
2.5 Assumptions and Dependencies 7
3. Requirements 7
3.1 Functional Requirements 7
3.1.1 General Requirements 8
3.1.2 Update Requirements 9
3.2 External Interface Requirements 10
3.2.1 User Interfaces 10
3.2.2 Hardware Interfaces 10
3.3 Performance Requirements 10
3.4 Attributes 11
3.4.1 Availability 11
3.4.2 Security 11

2
Introduction

1.1 Purpose
This document gives the description of the software requirements for
an automated parking garage management web portal (called the
Vehicle parking management system, VPMS). This
specification is intended for the designer, developer and maintainer of
the VPMS

1.2 Scope
The function of the VPMS is to control and supervise the entries and
exits into and out of a parking garage. The system allows or rejects
entries into the parking garage depending on the number of available
parking spaces. It also provides the facility to search vehicle parked in
the garage using a unique parking number assigned to each parked
vehicle. Moreover, a particular user can login and use his/her account
to keep track of all the vehicles belonging to him/her which are parked
in the garage.

1.3 Overview
The remainder of this document is structured as follows: There will be
some definitions of important terms in the next subsection. General-
Description part contains an overall description of the VPMS. The
Requirements part identifies the specific functional requirements, the
external interfaces and the performance requirements of the VPMS.

3
1.4 Definitions
Parking garage 
: Consists of 10 entry gates and 12 exit gates.
There are 10,000 parking spaces and 100 reserved ones.

Dashboard:
 This is the overall view of the type, ID number and

other related specifications of the vehicles parked in the garage.

Vehicle Category: It differentiates the vehicles according to their

wheel number.


Parking Number: It is the unique abstract identifier attached to

each parked vehicle to locate it in the garage.

Report: It is the tabular representation of each specification of the

vehicles parked in the garage.

Actions: It provides the feature to remove, add or view more related

details of the vehicle.

4
General Description
2.1 Overview

To give a short overview of the functionality of the VPMS the
following user scenarios are provided:

Entry

 Driver with an account: 

1. A driver enters the details of the vehicle. If, the parking garage
is full, nothing happens

2. Otherwise the report w.r.t to the current entry is updated.


3. The driver enters the parking garage. 
 


4. The driver parks the car the parking number assigned to the car
and leaves the parking garage. 


 Driver without an account: 

1. The driver enters his/her details and first creates a user

account. 


2. After logging in the car driver then enters the car details after
selecting the ADD VEHICLE option. 


3. All the processes are then same as above scenario.

      Exit 

1. The driver returns to his car and drives to an exit station.

2. The driver opens his/her report and using the ACTION option
removes the vehicle from the report releasing the parking
number for further entry in the future. 
 


5
2.2 Product Perspective
The software system is an embedded system. The software system
should control for

 each entrance: 

- A Parking number 

- A Gate 

- The Vehicle Category 

- The User account 

 each exit:

- An Action
- he report
- A Gate

2.3 Product Functions


The software system should control the report display, gates, parking
number, user account and reporting of the booking status to the user.

 If a valid car registration number is entered then a parking number

and active booked status should be send to the user.

 Choosing removal of vehicle among the actions should release the

parking number and the cancelled booking status must be send to
the user. 

 The gates should be closed after the car has passed the induction
loop. 

 The system should enable the user to select various payment options
and send the bill to the specified address in the user account.

6
2.4 User Characteristics

The system users (drivers) should not require special training. They
should be familiar with web systems and should have some experience
of user account creation and usage.

2.5 Assumptions and Dependencies 

Assumptions about the parking garage:
1. Every parking space can be reached from any entrance. 

2. Every exit can be reached from each parking space. 

3. No entrances are convertible to exits and vice versa. 
 

4.Emergency situations (e.g. fire) will not be considered here. 


Requirements
3.1 Functional Requirements
This is a list of functional requirements the system should satisfy. The
functional requirements are presented in the following way:

 Description: 
A description of the specific requirement 

 Input:
 A description of the inputs that the software system gets 

 Processing: 
A description of what the software system does

with the input. 

 Output:
 A description of the response /new state of the software

system. 

The input, processing and output sections are only specified when
needed. 

7
Functional Requirement 1: Data Objects 

In the software the following data objects exist:

K: Maximum number of parking spaces in the parking garage.
O: Number of occupied parking spaces in the parking garage.
A: (K-O), number of parking spaces available.

3.1.1 General Requirements 

Functional Requirement 2 

Description

The VPMS should control the entries and exits of a parking garage.

Functional Requirement 3 

Description

The VPMS has to guarantee that no more than K cars are in the
parking garage.

Functional Requirement 4
 
Description

‘K’ is divided into ‘O’ reserved parking spaces and ‘A’ non-occupied
parking spaces.

Functional Requirement 6
Description

The VPMS should support ‘N’ entries and ‘M’ exits. The VPMS has to
handle simultaneous entries and exits.

Functional Requirement 7

Description
 
Each registration number within a user account should receive unique
parking number.

8

Input
 
User account details, car registration number.


Output
 
Output unique parking number.

3.1.2 Update Requirements

Functional Requirement 9 

Description
 
The duration of parking should be mentioned before the allotment of
parking number.

Functional Requirement 10

Description
The previously entered duration can be changed and should
accordingly update the report.

Functional Requirement 11 

Description

The system should internally manage the calculations of ‘K’, ’O’ and
A=(K-O).

Processing

Check to make sure that ‘K’ is greater than ‘O’. Set new value of ‘K’.

Functional Requirement 12

Description

If more than one car wants to register in the parking garage through
different user accounts, the VPMS has to handle all events in the order
they occur.

Processing

Events should be handled in order in which they occur, and only
permit drivers in if there are open spaces.

9

Output

Enable registration to the various users (drivers) 

Functional Requirement 13 

Description

If several car’s parking number leave the parking garage at the same
time the VPMS has to handle the events in order.

3.2 External Interface Requirements

The VPMS exploits the web access because of its ease of use and
familiarity nowdays. 

3.2.1 User Interfaces 

Apart from the web interface there is no need for another user
interface. 

3.2.2 Hardware Interfaces 

Hardware interface is required only for entry and exit at the parking
gates. Entry uses parking number to allot place within the garage while
exit releases it.

3.3 Performance Requirements

Performance Requirement 1
Description

All changes to report at the backend during entry or exit station should
happen within 5 sec.

Performance Requirement 2
Description

 For each car that enters the parking garage there is a parking space
available.

10
3.4 Attributes
3.4.1 Availability

The system has to be available 24 h/day. The parking garage won’t be

closed at any time.
3.4.2 Security

No tickets other than the tickets of this parking garage should be

accepted by the ticket reader.

11