Table of Contents

1. Introduction…………………………………………………………………………..1

1.1 Purpose……………………………………………………………………….1

1.2 Document Conventions………………………………………………………1

1.3 Intended Audience and Reading Suggestions………………………………..1

1.4 Project Scope…………………………………………………………………2

1.5 References……………………………………………………………………2

2. Overall Description…………………………………………………………………..3

2.1 Product Perspective…………………………………………………………..3

2.2 Product Functions…………………………………………………………….3

2.3 User Classes and Characteristics……………………………………………..3

2.4 Operating Environment………………………………………………………3

3. External Interface Requirements…………………………………………………...5

3.1 User Interfaces……………………………………………………………….5

3.2 Hardware Interfaces………………………………………………………….5

3.3 Software Interfaces…………………………………………………………..5

3.4 Communications Interfaces………………………………………………….5

4 Other Non-Functional Requirements………………………………………………7

4.1 Performance Requirements………………………………………………….7

4.2 Safety Requirements…………………………………………………………7

1
4.3 System Quality Attributes……………………………………………………7

2
1. Introduction

1.1 Purpose

On-time arrivals, departures, and maintaining an accurate timetable of the public

This project includes a Vehicle tracking unit to collect the vehicle information, a Website
for registering the passengers and an Application that provides this information to the
passengers through Short Message Service (SMS).

1.2 Document Conventions

In this SRS, we have used Times New Roman font. The font size for main headings is 16
with bold font style. The size of subheadings is 14 with bold font style and the text is
written in font size 12.

1.3 Intended Audience and Reading Suggestions

Audiences benefited by our project work are basically common people who suffer
regularly due to delay in bus facility(as City Bus in our case).Administrator is the
supreme authority governing and managing the whole Transport Alert System. The rest
of the SRS contains Project Scope, Overall Description, External User Interfaces, System
Features and Other Nonfunctional Requirements.

3
Reading Sequence for the Document:

• Purpose

• Intended Audience and Reading Suggestions

• Project Scope

• Product Perspective

• Product Functions

• User Classes and Characteristics

• Other Nonfunctional Requirements

1.4 Project Scope

On-time arrivals and departures of a public transport is a major problem in the present
scenario due to increasing traffic and poor management of traffic system in India. It leads
to dissatisfaction and inconvenience among the common people.

To overcome the problem in the existing system, GPS enabled devices are installed in the
vehicles. The entire vehicle under the observation can be mapped with current location
and delay of a vehicle can be determined on the enquiry basis.

1.5 Reference

• http://www.google.com

• http://www.wikipedia.com

• http://www.mapmyindia.com

• The Complete Reference -Herbert Schlitz.

• Software Engineering –Somerville.

4
2 Overall Description

2.1 Product Perspective

Public Transport is the most common mode of travel across the globe. Cost effective,
ease of availability and comfort are driving more and more people to use public transport.
However delays and cancellation of services in existing public transport systems are
resulting in major dissatisfaction to passengers.

Our project is a very interactive application which deals with the common people
problem who wants the information regarding correct bus timing. It basically provides
the inquiring facility to the user by SMS.

2.2 Product Functions

• Transport Alert System (TAS) is a key solution to determine the location of the
vehicle. The solution includes vehicle tracking unit which is installed in vehicles to
collect its information and software that provides this information to the passengers
through Short Message Service (SMS).

• User friendly.

• Real time vehicle information.

• Get instant SMS alerts.

• User creation and password management through Website.

5
2.3 User Classes and Character

The various user classes that you anticipate will use this product are

• Admin

• Passenger

• Route

• Bus

• Location

• GPS data retrieval

2.4 Operating Environment

The application will work properly with following configuration:

• Pentium 4 and above

• Windows 98 or above

• RAM 512 MB and more

• JDK 1.5 and above

• Apache Tomcat Server 5.5 or above

• MySQL 5.1 or above

6
3. External Interface Requirements

3.1 User Interfaces

This application will use JSP, Servlets, CSS, JavaScript and AJAX for the development
of the web pages which will run on server.

3.2 Hardware Interfaces

This application requires the basic hardware i.e. Keyboard, Mouse, Monitor, etc. The
GPS device is also required.

3.3 Software Interfaces

The software required to develop the application are as follows:

• NetBeans IDE 6.8

• MySQL 5.1

• Apache Tomcat

3.4 Communications Interfaces

The application is developed on Server Side Programming and Apache Tomcat will be
acting as a Server. Communication among the modules will be done with the help of
HTTP protocol.

7
 4. Other Nonfunctional Requirements

4.1 Performance Requirements

• All error will be effectively handle, and prompt the user if required.

• All network issue will be effectively managed.

4.2 Safety Requirements

There is not any such loss, damage or harm that could result from the use of the product.
But there is one security concern regarding with the authentication of passenger (if the
login id, password is lost than they must complain to administration otherwise any other
person can access that account in behalf of that passenger & send wrong notification.

4.3 Software Quality Attributes

This product has some quality characteristics which include availability, correctness,
flexibility, maintainability, portability, reliability, reusability, testability and usability.
These are some of the quality attributes which will be beneficial to both customer and
developer in some ways. For example, this product will have the attribute of reusability,
so that the developer will be able to further extend the functionality of this product or
make a new product by reusing the same product instead of starting right from the
scratch. In the same way other attributes are also useful to both the customer and the
developer.