PANIMALAR ENGINEERING COLLEGE DEPARTEMENT OF COMPUTER SCIENCE & ENGINEERING SOFTWARE ENGINEERING UNIT 2 SRS ( SOFTWARE REQUIREMENT SPECIFICATION)

) PROBLEM

QUESTION: An independent truck company wants to track & record its drivers driving habits. For this purpose the company has rented 800 phones numbers & has printed the number on the front, back & sides of 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 waits for you to develop a system that: (i) (ii) (iii) Collects information from caller about the driver performance & behavior as well as truck condition. Generates daily & monthly report for the driver & truck management. 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 Specification Truck Driver Monitoring System Table of Contents 1. 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. 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.

1.0. Introduction
1.1. Purpose The purpose of this document is to present a detailed description of the Truck Hacking System. It will 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 driving behavior. This system will be designed to minimize the rash driving & regulate the traffic. By minimizing the rash driving avoid accidents. More specifically, this system is designed to allow the caller to communicate with aon-duty manager to inform about the driver performance & behavior as well as the truck conditions .The software will facilitate communication between caller & on-duty manager via phone& generates the report for each driver & truck management. 1.3. Definitions, acronyms &abbreviations Term Caller Database Callee On-duty manager Software Requirements Specification

Definition

Person informing about the driver performance &behavior. Collection of all the information monitored by this system. Person who receives & updates information Person who receives information generates reports and takes corrective action. A document that completely describes all of the functions of a proposed system and 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 the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next chapter. The third chapter, Requirements Specification section, of this document is written primarily for the 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 intended for different audiences and thus use different language.

2.0.
2.1

General Description
Product perspective Caller Phone On-duty manager Caller Phone

The Truck Hacking System has callers , cal lee and on-duty manager. Any caller can communicate with the 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. 2.3 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.

User Characteristics The Caller is expected to make a call. The On-duty manager is expected to analyze the complaints 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 trucks in their database. Adding new truck information, modify , delete truck details are supported in this task. Maintain Driver Details : The truck company maintains information about their drivers in their database. It includes adding new driver details, modify, delete driver details are supported in this task. Schedule List : It tells which driver is driving the truck with destination place, date. 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 the complaint register. Generate Daily Report : prepare daily report about all received complaints . Generate Monthly Report : prepare Monthly report about all received complaints .

ii)

iii) iv)

v) vi) 3.1.1

Caller Use Case

Make a call

Caller

3.1.2

On-duty manager Use Case

Collect Info Generate report

Report problem On-duty manager

3.2

Non-Functional Requirements Functionality : The end-user collect all the information and record it in the system . Two level of 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 the complaints, to generate the reports Reliability : Since MS- Access is used to store the information, report generation and action taken 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 the information maintained in this system. 3.3 Interface Requirements There is no special hardware interface connected to this system. Since MS Access7.0 with Visual Basic 6.0 is used to store the database , no ODBC interface is required for connectivity.

4.

Appendices
Hardware Specification :

Processor : i3 RAM : Software Specification : Front End : Visual Basic 6.0 Back End : MS. Access 10.0 Database Schema : Truck Table TruckNo Number

DOP( Date of Purchase) Model

Date String 4

Permit Limit Present Condition

String String

Truck Id Driver Id Destination Date& Time

String String Date String

Driver Table Driver Id Name DOB Address DOJ

String String Date String Date Complaint Register Table Truck Id Place Current Status Complaint Action String String String String String

Schedule Table Trip Id

Number

5.

Index Truck 2,3,4 Complaint Phone No On Duty Manager Caller 2,3,4

ASSIGNMENT QUESTION: An automated ticket issuing system sells rail tickets. Users select their destination & input a credit card & a personal identification number. The rail ticket is issued & their credit card account charged with its cost. When the user presses the start button, a menu display of potential destination is activated along with the message to the user to select the destination. Once a destination has been selected, user is requested to input a personal identifier. When the credit transaction has been validated, the ticket is issued. (i) Write a set of non-functional requirements setting out its expected reliability & its response time. (ii) Identify the ambiguities or omissions in the statement & write the system requirements using java based notation. Any reasonable assumptions could be made.