Software Requirements Specification for <Project>

Page 1
Pir Mehr Ali Shah
Arid Agriculture University, Rawalpindi

Project Title
Toll Plaza System

Submitted by:

Student 1
M. Shoaib 19-ARID-1135

Student 2
Rana Awais 19-ARID-1147

Student 3
Salih Umar 19-ARID-1153
Software Requirements Specification for <Project>
Page 2

Table of Contents
1 INTRODUCTION................................................................................................................ III
1.1 PURPOSE III
1.2 SCOPE III
1.3 OVERVIEW III

2 OVERALL DESCRIPTION.................................................................................................IV
2.1 • PRODUCT PERSPECTIVE IV
2.2 • PRODUCT FUNCTIONS IV
2.3 • USER CHARACTERISTICS IV
2.4 • CONSTRAINTS IV
2.5 • ASSUMPTIONS AND DEPENDENCIES IV

3 USE CASE(S).................................................................................................................... IV
4 SPECIFIC REQUIREMENTS.............................................................................................IV
4.1 FUNCTIONALITY IV
4.2 <FUNCTIONAL REQUIREMENT ONE> IV
4.2.1 Login logout interface :.........................................................................................................................iv
4.2.2 System interface.....................................................................................................................................iv
4.2.3 Security :................................................................................................................................................iv
4.2.4 Administrator login................................................................................................................................iv
5 NON FUNCTIONAL REQUIREMENT.................................................................................V
5.1 USABILITY V
5.1.1 <Usability Requirement One>...............................................................................................................v
5.2 RELIABILITY V
5.2.1 <Reliability Requirement One>.............................................................................................................v
5.3 SUPPORTABILITY V
5.3.1 <Supportability Requirement One>.......................................................................................................v
5.4 DESIGN CONSTRAINTS V
5.4.1 <Design Constraint One>......................................................................................................................v
5.5 PURCHASED COMPONENTS V

6 INTERFACES...................................................................................................................... V
6.1 USER INTERFACES V
6.2 HARDWARE INTERFACES V
6.3 SOFTWARE INTERFACES V
6.4 COMMUNICATIONS INTERFACES VI
6.5 LICENSING REQUIREMENTS VI
6.6 LEGAL, COPYRIGHT, AND OTHER NOTICES VI
6.7 APPLICABLE STANDARDS VI

7 SUPPORTING INFORMATION..........................................................................................VI
Software Requirements Specification for <Project>
Page 3
Use case Diagram for Toll Plaza System

System

Toll Collection
System
Applies for
RFID Card

Submits
Detail

Checks into Toll Authority

toll

Valid Entry

User Check out

Actor
(Vehicle) Of toll

Forward
Request

Deduct
Ammount
System
Admin
.........................VI
Software Requirements Specification for <Project>
Page 4

Scope Statement Template

Table of Contents
1 INTRODUCTION....................................................................................................... III
1.1 PURPOSE III
1.2 SCOPE III
1.3 OVERVIEW III

2 OVERALL DESCRIPTION.......................................................................................... IV
2.1 • PRODUCT PERSPECTIVE IV
2.2 • PRODUCT FUNCTIONS IV
2.3 • USER CHARACTERISTICS IV
2.4 • CONSTRAINTS IV
2.5 • ASSUMPTIONS AND DEPENDENCIES IV

3 USE CASE(S)............................................................................................................. IV
4 SPECIFIC REQUIREMENTS.......................................................................................IV
4.1 FUNCTIONALITY IV
4.2 <FUNCTIONAL REQUIREMENT ONE> IV
4.2.1 Login logout interface :....................................................................................................................... iv
4.2.2 System interface..................................................................................................................................... iv
4.2.3 Security :.................................................................................................................................................... iv
4.2.4 Administrator login............................................................................................................................... iv
5 NON FUNCTIONAL REQUIREMENT........................................................................V
5.1 USABILITY V
5.1.1 <Usability Requirement One>........................................................................................................... v
5.2 RELIABILITY V
5.2.1 <Reliability Requirement One>........................................................................................................ v
5.3 SUPPORTABILITY V
5.3.1 <Supportability Requirement One>............................................................................................... v
5.4 DESIGN CONSTRAINTS V
5.4.1 <Design Constraint One>................................................................................................................... v
Software Requirements Specification for <Project>
Page 5
5.5 PURCHASED COMPONENTS V

6 INTERFACES.............................................................................................................. V
6.1 USER INTERFACES V
6.2 HARDWARE INTERFACES V
6.3 SOFTWARE INTERFACES V
6.4 COMMUNICATIONS INTERFACES VI
6.5 LICENSING REQUIREMENTS VI
6.6 LEGAL, COPYRIGHT, AND OTHER NOTICES VI
6.7 APPLICABLE STANDARDS VI

7 SUPPORTING INFORMATION................................................................................VI

1 Introduction
Toll management systems play an important role in the growth of infrastructure all over the world
. It is a kind of the money that a commuter has to pay to the road authorities while passing from one city
to another.
This in turn is a tax that is used in the construction of roads, flyovers, and expressways.
This Application can provide all the information related to Toll booth and the passenger checks
in online and pays the amount, then he/she will be provided by a receipt. With this receipt he/she
can leave the toll booth without waiting for any verification call.
Automatic Vehicle Identification: Automatic Vehicle Identification (AVI) is the process of
determining the identity of a vehicle subject to tolls. This identification is usually done through
barcodes affixed to each vehicle; to be read optically at the toll booth.
Automatic Vehicle Classification: This is a low-cost method of storing the records of vehicle
classes of all customers. The class of the vehicle is determined through AVI data.

Transaction Processing: Transaction processing deals with maintaining customer accounts,

posting toll transactions and customer payments to the accounts.

Violation Enforcement System: Violation Enforcement System (VES) is useful in reducing

unpaid tolls, as an unmanned toll gate otherwise represents a tempting target for toll evasion
Software Requirements Specification for <Project>
Page 6

1.1 Purpose
The purpose of this document is to describe the functional electronic toll system (ETS)
requirements any future changes and/or additions made to these requirements must also be possible
Toll plaza electronic system shall read data from vehicle toll tags to support toll payment transactions
,the system shall calculate the toll due based on the vehicle characteristics (vehicle size, weight, axle
count, etc.), tag data, and stored toll prices.the system shall update the toll tag value after debiting the toll
amount and send a record of the transaction to a centre.
. The system shall read the credit identity on the toll tag and send that identity and the amount to
be debited to a centre.The system shall control roadside displays indicating success or failure of
the toll transaction to the driver .The system shall respond to changes in tolls from the Toll
Operator.The system shall forward wide-area alert information to the Toll Operator.

In existing system, current times of increasing traffic on the road, it is important to collect
the toll tax in a managed and controlled process so that it doesn't result in a total unorganized
jungle of traffic. It is very challenging to handle a vehicular flow by a manual system of revenue
collection. Poor management at toll plaza may result into great chaos and revenue loss. This
would not be desired any one.

The existing system had following Drawbacks:

 It was very time consuming
 Reports were generated manually.
 The Activities are often prone to errors.
 The speed of processing of data is very slow.
 The information required was not readily available.
 Lots of paper work was there.

1.2 Scope

Toll management system is the most important part of a Highway Project. The system is
designed with various built-in security features, with a focus on ease of toll collection in the lane
and avoiding, detecting, and stopping any revenue leaks.

Stakeholders.
Automobile owner
Programmers
Software Requirements Specification for <Project>
Page 7
Testers
Motorway Police

1.3 Overview
In order to provide better traffic flow high occupancy vehicle (HOV) lane will
be converted to a High Occupancy Toll (HOT) lane.  Federal Highway Administration
(FHWA) authorized this conversion as a pilot project to improve travel efficiency in
the corridor and provide more options to individual travelers.  

1.      Better utilize the HOV lane to improve traffic throughput in the corridor;
and
2.      Optimize this new revenue stream to help pay for transportation
improvements and transit operations in the corridor.

2 Overall Description
2.1 • product perspective
It must required internet connection to display content and allow user to connect eith sysyten.

2.2 • product functions

Linked with database
Data retrieve
Connection with server
HTTP protocol used

2.3 • user characteristics

Motor way police should be able to use the system they must know how to connect system
online .they must be able to use computer and must know way of its operating computer typing
text on it,

2.4 • constraints
Server down ,
Problem internet availability
Complex system isn’t understand by user.

2.5 • assumptions and dependencies

The requirement shall change according to user needs .
The system must follows the standard of the organization
If hacker try to attack on system, system should block the specific ip address and report to
concerned Authority
Software Requirements Specification for <Project>
Page 8

3 Use Case(s)

Identifier TPMS_ID
Title Toll management system
Requirement Login logout interface :
System must have login logout interface for users to track their transactions
and other queries

System interface
System must have a user friendly interface through which user interact and
track their task and daily routien
Security :
It is first priority of system as our data is confidential system must note
compensiate any mistake of security purpose
Administrator login
It is master login Interface containing and managing all data of other
users it can also track works of other user

Source Stakeholders ,programmers and motorway police

Rationale Improve taxation system of motorway
Business Rule (if Any restriction, policy, rule that the requirement must be fulfilled
required) through its functional behavior
Dependencies Security is first priority

4 Specific Requirements
Toll plaza requirement
General requirement
Automobile tax record.
Person useable

4.1 Functionality

Toll management systems play an important role in the growth of infrastructure all over the world. It is a
kind of the money that a commuter has to pay to the road authorities while passing from one city to
another. This in turn is a tax that is used in the construction of roads, flyovers, and expressways.

4.2 <Functional Requirement One>

4.2.1 Login logout interface :

System must have login logout interface for users to track their transactions and other queries
Software Requirements Specification for <Project>
Page 9

4.2.2 System interface

System must have a user friendly interface through which user interact and track their task and daily
routine

4.2.3 Security :
It is first priority of system as our data is confidential system must note compensiate any mistake of
security purpose

4.2.4 Administrator login

It is master login Interface containing and managing all data of other users it can also track
works of other user

5 Non Functional Requirement

5.1 Usability

Usability refers to the quality of a user's experience when interacting with products

or systems, including websites, software, devices, or applications.
 Usability is about effectiveness, efficiency and the overall satisfaction of the user.
5.1.1 <Usability Requirement One>
Accessible
Availability

5.2 Reliability

Reliability refers to the consistency of a measure. Psychologists consider three types of consistency: over
time (test-retest reliability across items (internal consistency), and across different  researchers (inter-rater
reliability).

5.2.1 <Reliability Requirement One>

Security

5.3 Supportability

Supportability is the degree to which system design characteristics and planned logistics resources meet
system requirements.
 Supportability is the capability of a total system design to support operations and readiness needs
throughout the life-cycle of a system at an affordable cost

5.3.1 <Supportability Requirement One>

System must be sport able by internet browsers and can be used in a operating system
Software Requirements Specification for <Project>
Page 10
5.4 Design Constraints

There are two aspects in the design of toll plaza. One is based on network topology index calculation
and uses information technology to design toll station management system, including Internet of things 

5.4.1 <Design Constraint One>

Throughput
Throughput is defined as the amount of information or material passed put through or delivered in a
specific period of time
Response time
Response time is the total amount of time  it takes to respond to a request for service. ... Ignoring
transmission time for a moment, the response time is the sum of the service time and wait time.
User feedback

5.5 Purchased Components

Investment
Cost on program development
Hardware cost
Web Hosting cost

6 Interfaces

6.1 User Interfaces

User friendly :
A user-friendly interface is not overly complex, but instead is straightforward, providing quick
access to common features or commands. Clean. A good user interface is well-organized, making it easy
to locate different tools and options
Easily operate able by user :
A good interface makes it easy for users to tell the computer what they want to do, for the
computer to request information from the users, and for the computer to present understandable
information. Clear communication between the user and the computer is the working premise of
good UI design

6.2 Hardware Interfaces

The hardware system consists of microcontroller, LCD , RFID, motor driver, and GSM
Hardware Requirements:-
 Keyboard
 Monitor
 Mouse
 Pentium processor-lll
Software Requirements Specification for <Project>
Page 11
 Modem
 Internet connection

6.3 Software Interfaces

S/W Requirements:-
The software system consists of a Assembly based language is used . This system consists of a
microcontroller interfaced with RFID, Motor driver, Max 232 and LCD 16x2 display, forming
the hardware unit and interfaced to the server making up the software unit.

Operating System : Windows95/98/2000/XP

Application Server : Tomcat5.0/6.X
Front End : HTML, JAVA,PhP
Scripts : JavaScript
Server side script : Java server pages
Database : Mysql
Database connectivity : JDBC

6.4 Communications Interfaces

http protocol
https protocol

6.5 Licensing Requirements

System must be according to international standards

6.6 Legal, Copyright, and Other Notices

All data is confidential safe and secure if someone shares or leak our system data then
copyright is cased on them and legal action will took against on him.

6.7 Applicable Standards

Application standers;
Useable;
Easily accessible
Software Requirements Specification for <Project>
Page 12

7 Supporting Information
[The supporting information makes the SRS easier to use. It includes:

• Table of contents

• Index

• Appendices

These may include use-case storyboards or user-interface prototypes. When appendices

are included, the SRS should explicitly state whether or not the appendices are to be
considered part of the requirements.
Web hosting
Web application
Can be open on any Browser
User Feed back
Use case

Use case Diagram for Toll Plaza System

System

Toll Collection
System
Applies for
RFID Card

Submits
Detail

Checks into Toll Authority

toll

Valid Entry

User Check out

Actor
(Vehicle) Of toll

Forward
Request

Deduct
Ammount
System
Admin