PMAS Arid Agriculture University Rawalpindi

        University Institute of Information Technology

Project Title

Toll Entry System

Submitted by:
Student 1

Rizwan Ali

Student 1 Registration No
19-ARID-1051

Student 2
Adeeba Dastageer

Student 2 Registration No
19-ARID-978

Student 3
Sania Shafi

Student 3 Registration No
19-ARID-1155
Software Requirement Specifications:
Topic:
Toll Management System:

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
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 center.
. The system shall read the credit identity on the toll tag and send that identity and the amount
to be debited to a center. 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.

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
Testers
Motorway Police
1.3 References

 SRE text book

 https://www.scribd.com/document/241377442/SRS-Online-Toll

1.4 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;

2. Overall Description
• Product perspective:
It must require internet connection to display content and allow user to connect with system.

• Product functions:
1. Linked with database
2. Data retrieve
3. Connection with server
4. HTTP protocol used

• 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,

• Constraints
1. Server down.
2. Problem internet availability
3. Complex system isn’t understandable by user.

• Assumptions and dependencies:

1. The requirement shall change according to user needs.
2. The system must follow the standard of the organization
3. If hacker try to attack on system, system should block the specific IP address and report
to concerned Authority
3. Use Case(s)
According to given scenario following are the actors in or use-case:
1. Vehicle Owner
2. Toll Admin
Given below is the use-case diagram for our student management system.

4. Components:
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 routine.
Security:
It is first priority of system as our data is confidential system must
note compensate 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

5. Specific Requirements
Our system involves the following functions

Vehicle Registration
 Our system provides online registration and status information to the toll owner to
view status of vehicle.
 It provides automatic vehicle register number generation based on vehicle model.
 It provides the toll owner to add their vehicle.

Interface Requirements

Hardware Interfaces:
We require LAN connection for interacting with the
database and local computers for any help or any other requirement. We use
TCP/IP protocol for communicating with local hosts. We also need a system with
P4 processor; 1GB RAM and database memory.

Software Interfaces:
We use MS.Net 3.5 and C#.Net 3.5 Programming language for writing the code
for the project. ASP.Net 3.5 for creating the web pages, using GUI for login
screens and interacting with the database. SQL server is used for creating the
local and global database. Visual Studio for writings the programs. Operating
system: Windows XP or higher version.
 Communications Interfaces:
The communications functions required by this
product are LAN connection within the whole system so that the Admin and
vehicle owner can interact with each other. We use TCP/IP protocol.

Reliability
The software will not be able to connect to the centralized database in the
event that the main toll LAN fails or in the event of the server being down due to a
hardware or software failure.

Performance
In performance requirement easy tracking of records and updating can be
done. All the requirements relating to performance characteristics of the system are
specified in the section below. There are two types of requirements.
Static Requirements:
These requirements do not impose any constraints on the execution characteristics of
the system.
 They are number of terminals which a software makes use of an underlying
database that will reside at the server, while the front end will be available online
to the admin and toll computers as well as vehicle owner.

Dynamic Requirements:
These specify constraints on the execution characteristics of
the system. They typically include response time and throughout of the system. Since
these factors are not applicable to the proposed software, it will suffice if the response
tine is high and the transactions are carried out precisely and quickly.

5.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.

5.1.1 <Functional Requirement One>

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 routine
Security:
It is first priority of system as our data is confidential system must note compensate 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.

5.2 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.2.1 <Usability Requirement One>

1. Accessible
2. Availability

Appendix A:
Glossary:
TES: Toll Entry System.
SRS: Software Requirement Specification.
ETS: Electronic Toll System.
LAN: Local Area Network.
IP: Internet Protocol.
TCP: Transmission Control Protocol.
SI: System Interface.

Appendix B:
Analysis Mode:
Dataflow diagram of Toll Entry System.