2019

SOFTWARE REQUIREMENT
SPECIFICATION (SRS)

MALAIKA MUNAWAR
ROLLNO: F17-0106
SUBMITTED TO:
SIR ABID ALI.
SECTION:
“C”
PROGRAM:
BSSE (4th)
DATE:
13 JUNE, 2019.
SOFTWARE REQUIREMENT SPECIFICATION

TABLE OF CONTENT:
1. INTRODUCTION
1.1 PURPOSE
1.2 DOCUMENT CONVENTION
1.3 PROJECT SCOPE
1.4 REFERENCES
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
2.2 USER CLASSES AND CHARACTERISTICS
2.3 OPERATING ENVIORNMENT
2.4 DESIGN AND IMPLEMENTATION CONSTRAINTS
2.5 ASSUMPTIONS AND DEPENDENCIES
3. SYSTEM FEATURES
3.x SYSTEM FEATURE X
3.x.1 DESCRIPTION
3.x.2 FUNCTIONAL REQUIREMENTS
4. DATA REQUIREMENT
4.1 LOGICAL DATA MODEL
4.2 DATA DICTIONARY
4.3 REPORTS
4.4 DATA ACUSITION, INTEGRITY, RETENSION, AND DISPOSAL
5. EXTERNAL INTERFACE REQUIREMENT
5.1 USER INTERFACES
5.2 SOFTWARE INTERFACES
5.3 HARDWARE INTERFACES
5.4 COMMINICATION INTERFACES
6. QUALITY ATTRIBUTES
6.1 USABILITY
6.2 PERFORMANCE
6.3 SECURITY
6.4 SAFETY
6.5 OTHRES
7. INTERNATIONALIZATION AND LOCALIZATION REQUIREMENT
8. OTHRES
 1.INTRODUCTION:
Our intelligent Traffic Expert Solution for road traffic
Monitoring System offers the ability to acquire real-time traffic
information, .Traffic Expert enables operators to perform real-time
data analysis on the information gathered. Traffic management
measures are aimed at improving the safety and flow of traffic
utilizing traffic capacity more effectively.

1.1.PURPOSE:
Smart Traffic Management is mainly improvised for looking after
the Set off data of a region to manage the Traffic along that area and
implement various useful technologies which are been required by
various persons like vehicle owners, pedestrians, police officers
etc….Mainly the purpose of Smart traffic management system is to
give the details which can be used and they can be implemented in
their daily life. The problems which have been occurred at their
presence can be solved by this Smart Traffic.

1.2 DOCUMENT CONVENTIONS:

The remainder of this document will be used to specify the
requirements of the system. It will also be used to illustrate the
various use-cases and interfaces of the program.

1.3 PROJECT SCOPE:

Smart Traffic is a Video Analytics Module and provides
Traffic Incident Detection, and real time Traffic Flow Metrics &
statistical analysis. Smart Traffic Monitoring can integrate with third
party traffic management and smart roadway systems and hosts a
feature rich product scope itself.

1.4 REFERENCES:
1. Anderson, J. E. 2003. “Control of Personal Rapid Transit Systems.”
Electronic, Vol. 99, No. 1, 108-116
2. Betterton, D., Bowen, G., Wood, K. 2002. ‘Effective urban traffic
management and control – SCOOT VERSION 4.4’. Proceedings of
European Transport Conference Proceedings Cambridge.
3. Christos Xithalis, 2008, PRT Hermes.

2. OVERALL DESCRIPTION:
The Smart Traffic Monitoring System has three active actors
one cooperating system. Mainly pedestrians who uses the dataset
provide by the admin and give the complaints important suggestions
which are under taken by the traffic police and admins whereas the
vehicle owners to generate the same idea of the pedestrians .Traffic
police maintains the information which are provided by the users(
pedestrians, vehicle owners)and make into implementation.

2.1 PRODUCT PERSPECTIVE:

This system is meant to simulate how a four-way
intersection can be managed to reduce the likelihood of
collisions while remaining as efficient as possible. It contains
rules that must be followed for both the traffic controller and
the cars.
2.2 USER CLASSES AND CHARACTERISTICS:
 Every user should be comfortable of working with computer
and net browsing.
 Every user has to register with the STM.
 Every user should have their own login and password.
 Every user can issue the complaints.
 Every user must have basic knowledge of English too.

2.3 OPERATING ENVIORNMENT:

Software Requirement:
 -Operating system: Linux (Ubuntu 13.04 and above)/Windows 7/8/10 -
Technologies: Java, Open CV

Hardware Requirement:
 -RAM, Pentium P3/P4, 20/40 GB Hard disk

2.4 DESIGN AND IMPLEMENTATION

CONSTRAINTS:
 GUI is only in English.
 This system is working for single server.
 Limited to HTTP/HTTPS.
 User should have basic knowledge of computer.

2.5 ASSUMPTIONS AND DEPENDENCIES:

  The administrator is aware of the system workings and different
attributes attached to it.
 The various configurations should be known to him/her.
 Since the results would be in terms of values, to monitor it properly, the
DA should be aware of the significance of each value.
 She/he should also be familiar with Image Processing Domain.
 Once admin fixes the CCTVs, it should automatically start recording real
time traffic and sending output to the signal points.
 The timing of lights would be dependent on the traffics and length of it
on all the four sides.

SYSTEM FEATURES X:
The users of the system should have provided
the surety of the system.
 User authentication and validation with their unique ID.
 Proper monitoring by the administrator which includes traffic
monitoring, assigning fine to the drivers for breaking the traffic
rules.
 No other people or person can see the traffic issues except the
administrator who monitor all the traffic modules.

3. X.1 DESCRIPTION:
The Traffic Monitoring System (TMS) is a proactive monitoring
system that helps to control traffic infractions, avoid traffic accidents,
proactively detect potentially dangerous drivers, and recreate traffic-
accident scenarios offline (such as for insurance companies or legal process
investigations. Once installed in a car (similar to the black box in an aero
 plane), TMS can collect GPS and record information. Every time the car stops
at an intersection or refuels, the device uploads the information to a
database or main network. Once this process is concluded, the internal
memory can be deleted. The data is then analyzed and scanned for
predefined patterns of driving behavior, or proximity in time and position to
known traffic accidents and other irregular events. Applied nationwide, TMS
could potentially encourage drivers to avoid speed infractions: It
automatically detects traffic infractions and collects data on abnormal
vehicle behavior that can be statistically related to alcohol, drugs, dangerous
driving, etc.

3. X.2 FUNCTIONAL REQUIREMENT:

Functional requirements capture the intended behavior of the
system. This behavior may be expressed as services, tasks or functions the
system is required to perform.
Following are the required features of this project:

 The system will show the traffic on a road graphically.

 System will allow the vehicle owner and pedestrian to view road model
graphically and view traffic situation.
 System will allow admin of the system to rewrite traffic data.
 System will provide interface to admin to control the flow of traffic i.e.
manage emergency situation and reconfigure device.
 System will allow admin to adjust signal timing.
 According to the adjusted timing of signal the system should clear out the
particular way and then the next route accordingly.
 By measuring the traffic lined up on road signal timings should be
adjusted.
 According to the adjusted timing of signal the system should clear out the
particular way and then the next route accordingly.
  There should be an emergency override that allows traffic authorities to
remotely let go a particular signal in case an ambulance or important
vehicle arrives on that way
4. DATA REQUIREMENT:
The input consists of the query to the database and outputs consists
of the solutions of that query.

4.1 LOGICAL DATA MODEL:

4.2 DATA DICTIONARY:

 Length of the Traffic on the route, i.e. number of vehicles on the
road,
 Distance between the Consecutive Signals,
  Synchronization among Consecutive Signals,
 Time-of-the-day,
 Dedicated Lanes, if available (for left turns).

5.EXTERNAL INTERFACE REQUIREMENT:

5.1USER INTERFACE:
 The design and layout of every form will be very clear and very
interactive to the administrator.
 When the administrator open the software, the welcome window will
appear.
 From each and every window the user can easily go to any desired
window so that there will be an absolute and relative linking and admin can
monitor and track the process easily.
 There should be proper coordination between the different modules
and that should also be maintained at the front end in terms of look and feel to
the DA.
 In the screen layout, the background color is very light and the graphics
and font style will be in proper manner and well organized.
 The admin will be able to check out the logs anytime for identification
of errors or lags in the system.

5.2 SOFTWARE INTERFACE:

 Client : Web Browser, Windows series

 Web Server : WASCE, Windows series

 Data Base Server : DB2,Windows series

 Development End : J2EE, Java, Oracle, XML, DB2, OS

 (WINDOWS XP), Web Server.

5.3 HARDWARE INTERFACE:

The hardware requirements for Traffic Monitoring
System are as listed below:

For Server:
a. Intel Pentium 4
b. 2GB RAM
c. 80 GB hard disk
d. Network Interface card.

For client:
a. Intel Pentium III or above.
b. 512 MB RAM
c. 40 GB hard disk
d. Network Interface card

5.4 COMMUNICATION INTERFACE:

 Client on Internet will be using HTTP/HTTPS protocol.
 Firewall security is required for securing the server.
 TCP/IP protocol is basic need for client side.
 Add the chosen traffic CCTVs whose recording is to be done. Analyze
those videos and the format configuration for recording should be AVI
format.
 Calculate timing information and give it to the signal systems.
6 QUALITY ATTRIBUTES:
Non-functional requirement play a significant role in the development of
the system. If not captured properly, the system may not fulfill some of the
basic business needs.

6.1 Availability
System should be available every time and on every window it
should support.

6.2 Reliability
System should be reliable enough to satisfactorily the performance.
6.3 Supportability
It should provide support to user to easily access all the pages
without much effort and it should be capable to update and maintain in future.

6.4 Maintainability
System should be easily maintainable. It should be flexible
enough to stand with change and exceptions. The system should also handle
new requirements. It should have capability to maintain in new environment

6.5 Usability
System should be user friendly and should provide informative
error message to inform user when something goes wrong

6.6 Security
Security is the main issue. System should be safe and ensure the
security. It will ensure secure transfer of data.
6.7 Performance

 The performance of the functions and every module must be well.

 The overall performance of the software will enable the users to work
efficiently.

 System should give better resource sharing results.

 Performance of the results and data application should be efficient and

fast enough.

APPENDIX A GLOSSORY:

Term Definition
Traffic police His co-insides with the remaining users to
upgrade the complaints and implement it.
Vehicle owners They use the traffic data and implement when
they require. If they have any compliant they can
provide.
A Person who is designated the whole dataset
which are require by the remaining users and
Admin
maintain the whole project in a reasonable
manner.
Pedestrians A Person(s) who uses the datasets provide by the
admin and implement the ideas which he had.
7. OTHER REQUIREMENTS:

 Use case diagram

 Usage scenarios.

sUSE CASE DIAGRAM:

UASGE SCENARIOS:

Use Case Title

View Traffics
Actor Vehicle Owner/Pedestrian
Use Case ID 01
Description In this use case system will allow the user to view the road graph
to view situation of traffic flow.

Task 1. This use case starts when user wants to view the traffic
Sequence
situation.
2. User option to road graph.
3. System open road graph.
4. This use case end.
Extend/include : None

Exceptions None

Pre-Conditions User must open the application.

Post Operation done successfully.
Conditions

Modification 1.0
History
8. APPENDIX B ANALYSIS MODEL: