1

PANIMALAR ENGINEERING COLLEGEDEPARTEMENT OF COMPUTER

SCIENCE & ENGINEERINGSOFTWARE ENGINEERING

UNIT 2SRS ( SOFTWARE REQUIREMENT SPECIFICATION)

PROBLEMQUESTION:
An independent truck company wants to track & record its drivers driving habits.
For thispurpose the company has rented 800 phones numbers & has printed
the number on the front, back & sidesof all trucks owned by the company. Next
to the 800 numbers a message is written PLEASE REPORT
ANY DRIVER OR TRUCK PROBLEM BY CALLING THIS
NUMBER.
The hacking company waitsfor you to develop a system that:(i)
Collects information from caller about the driver performance & behavior as well
as truck condition.(ii)
Generates daily & monthly report for the driver & truck management.(iii)
Reports problems that require immediate action to an on-duty manager.Analyze the
problem statement & list major functions to be incorporated with the
SRS document.
ANSWER:Software Requirement SpecificationTruck Driver
Monitoring SystemTable of
Contents1. Introduction .............................................................................................
Error! Bookmark not defined.
1.1 Purpose ............................................................................................
Error! Bookmark not defined.
1.2 Scope of the product .......................................................................
Error! Bookmark not defined.
1.3 Definitions,acronyms & abbreviations ...........................................
Error! Bookmark not defined.

2
1.0. Introduction
1.1. Purpose
The purpose of this document is to present a detailed description of the Truck
Hacking System. Itwill explain the purpose and features of the system, the
interfaces of the system, what the system will do,the constraints under which it
must operate and how the system will react to external stimuli.
1.2. Scope of Project
This software system will be a Truck Hacking System for tracking the trucks &
drivers drivingbehavior. This system will be designed to minimize the rash driving
& regulate the traffic. By minimizingthe rash driving avoid accidents.More
specifically, this system is designed to allow the caller to communicate with aondutymanager to inform about the driver performance & behavior as well as the
truck conditions .The softwarewill facilitate communication between caller & onduty manager via phone& generates the report foreach driver & truck management.
1.3. Definitions, acronyms &abbreviations
Term Definition
Caller Person informing about the driver performance &behavior.Database Collecti
on of all the information monitored by this system.Callee Person who receives & u
pdates informationOn-duty manager Person who receives information generates re
ports and takes corrective action.Software RequirementsSpecificationA document
that completely describes all of the functions of a proposed systemand the
constraints under which it must operate.
1.4. References
IEEE.
IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications.
IEEE Computer Society, 1998.
1.5. Overview of Document
The next chapter, the Overall Description section, of this document gives an
overview of thefunctionality of the product. It describes the informal requirements
and is used to establish a context forthe technical requirements specification in the
next chapter.The third chapter, Requirements Specification section, of this
document is written primarily forthe developers and describes in technical terms
the details of the functionality of the product.Both sections of the document
describe the same software product in its entirety, but are intendedfor different
audiences and thus use different language.
2.0. General Description
2.1 Product perspective

CallerCallerPhonePhoneOn-dutymanager

3
The Truck Hacking System has callers , cal lee and on-duty manager. Any caller
can communicate withthe system is through phone. The on-duty manager will
take action accordingly.
2.2 Product functions
A Truck Hacking System does the following things as shown below.

Collect information from caller about the driver performance & behavior as well as
truck condition

Generate daily & monthly reports for each driver & truck management.

Reports problems that require immediate action to an on-duty manager.

2.3 User Characteristics
The Caller is expected to make a call. The On-duty manager is expected to
analyze thecomplaints and take the necessary actions. Internet literate and to be
able to use system.
3.0 Specific Requirements
3.1 Functional Requirements
This system has the following tasks.i)
Maintain Truck Details :
The truck company maintains information about their trucksin their database.
Adding new truck information, modify , delete truck details aresupported in this
task.ii)
Maintain Driver Details :
The truck company maintains information about their driversin their database. It
includes adding new driver details, modify, delete driver details aresupported in
this task.
iii)
Schedule List :
It tells which driver is driving the truck with destination place, date.
iv)

Receive Complaint :
When a Caller gives the complaint about the truck over the phone,informations like
truck no , date, time , place, current problem are recorded in thecomplaint register.
v)
Generate Daily Report :
prepare daily report about all received complaints .
vi)
Generate Monthly Report :
prepare Monthly report about all received complaints .
3.1.1 Caller Use Case
CallerMake a call

4
3.1.2 On-duty manager Use Case 3.2 Non-Functional Requirements
Functionality :
The end-user collect all the information and record it in the system . Two levelof
logins are available . 1. Callee Login 2. On Duty Manager Login to update and
view the complaints.On Duty Manager login has more rights than Callee Login.
Usability :
This system is provided with user friendly menu driven options to update
thecomplaints, to generate the reports
Reliability :
Since MS- Access is used to store the information, report generation and
actiontaken against driver for their rude driving or any other activity is very
confidential.
Performance :
Information are quickly updated and reports are generated with in fraction
of seconds
Security :

Since two logins are provided with passwords, third person cannot access
theinformation maintained in this system.
3.3 Interface Requirements
There is no special hardware interface connected to this system. Since MS
Access7.0 with VisualBasic 6.0 is used to store the database , no ODBC interface
is required for connectivity.
4. Appendices
Hardware Specification :
Processor : i3RAM :
Software Specification :
Front End : Visual Basic 6.0Back End : MS. Access 10.0
Database Schema :Truck Table
TruckNo NumberDOP( Date of Purchase) DateModel StringCollect
InfoOn-dutymanagerGeneratereportReportproblem

1.4 References .......................................................................................

Error! Bookmark not defined.
1.5 Overview of the document ..............................................................
Error! Bookmark not defined.
2. General Description ................................................................................
Error! Bookmark not defined.
2.1 Product Perspective .........................................................................
Error! Bookmark not defined.
2.2 Product Functions ...........................................................................
Error! Bookmark not defined.
2.3 User Characteristics ........................................................................
Error! Bookmark not defined.
2.4 General Constraints .........................................................................
Error! Bookmark not defined.
2.6 Assumptions and Dependencies .....................................................
Error! Bookmark not defined.
3. Specific Requirements .............................................................................
Error! Bookmark not defined.
3.1 Functional Requirements ................................................................
Error! Bookmark not defined.
3.2 Non-Functional Requirements ........................................................
Error! Bookmark not defined.
3.3 Interfaces Requirements ..................................................................
Error! Bookmark not defined.
4. Appendices ...............................................................................................
Error! Bookmark not defined.
5. Index .........................................................................................................
Error! Bookmark not defined.