iRoute

Bus Route Management System

Software Requirements Specification
For Android
Version 1.1

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf

Version:
1.1
Date: 27/03/2012

Revision History
Date

Version

Description

Author

04/01/2012

1.0

Software Requirements Specification

Lasindu Charith

27/03/2012

1.1

Software Requirements Specification

Lasindu Charith

Confidential

iRoute, 2012

Page 2

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf

Version:
1.1
Date: 27/03/2012

Table of Contents
1.

2.

3.

Introduction

1.1
1.2
1.3
1.4
1.5

4
4
4
4
4

Purpose
Scope
Definitions, Acronyms, and Abbreviations
References
Overview

Overall Description

2.1
2.2
2.3
2.4
2.5

4
5
5
5
6

Product Perspective
Product functions
User characteristics
Constraints
Assumptions and dependencies

Specific Requirements
3.1

3.2

3.3

3.4

3.5
3.6
3.7
3.8

3.9

Functionality
Accept User Input
Output possible bus routes
Store user favorites
Navigate with Google Maps
Usability
Simple, Graphical User interface
Minimal surprise
Ease of use
User Guidance
Reliability
Availability
Accuracy
Mean time to recover
Performance
Response Time
Transactions per second
Capacity
Resource Utilization
Supportability
Coding standards and naming conventions
Design Constraints
On-line User Documentation and Help System Requirements
Interfaces
3.8.1 User Interfaces
3.8.2 Software Interfaces
3.8.3 Communications Interfaces
Licensing Requirements
3.9.1 Legal, Copyright, and Other Notices

Confidential

iRoute, 2012

6
6
6
Error! Bookmark not defined.
6
7
7
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
8
8
9
9
9

Page 3

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf

Version:
1.1
Date: 27/03/2012

Software Requirements Specification

1. Introduction
1.1 Purpose
Purpose of this document is to describe the detailed requirement specification for the iRoute Bus
Management Application for Android Platform. 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.
The intended audience of this document includes technical assessment personnel and other prospective
developers who would like to develop this system with further modifications.

1.2 Scope
Travelling has become a major requirement of people today. Buses have become one of the prime modes of
transportation. For an ordinary passenger, finding his/her bus route to the destination is a difficult task
specially in Colombo area. If the passenger has less experience in travelling by bus to a particular place it is
difficult to correctly identify the bus route(s) which has the lowest cost in both ticket price and distance.
This project addresses the above problem via an android application which ensures a reliable service to its
users to find the desired bus route(s), given the source and the destination.
1.3 Definitions, Acronyms, and Abbreviations
SRS Software Requirements Specification
RUP Rational Unified Process
BMS Bus Route Management System
API - Application Programming Interface
1.4 References

The Rational Unified Process

http://www.ts.mah.se/RUP/RationalUnifiedProcess/process/artifact/ar_devcs.htm
Android Developers web
http://developer.android.com/index.html

1.5 Overview
The rest of the document contains an overall description of the Bus route Management Application
(section 2) and the specific requirements of the system (section 3)

2. Overall Description
2.1

Product Perspective
This application allows user to input his/her starting place and ending place in the user interface simply by
selecting from the drop down menu, as one would do in Google maps. The output will consist of available
options/routes where user can select from. Interface will be made to have a similar look and feel that is
consistent with android applications. The system is expected to evolve several iterations over several
releases.

Confidential

iRoute, 2012

Page 4

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf

Version:
1.1
Date: 27/03/2012

Open
Application

Enter start & End

locations

User

View Bus Route

View Route in
Google Maps

Android Application

2.2

Product functions

Output a refined list of bus routes, according to the beginning and the destinations which the users
can view the best possible bus route with details.
Bus route is generated according to an optimized path finding algorithm which avoids mismatches
and conflicts in routes as much as possible.
Once the user selects a particular bus route, user is provided with a view of his route and current
position via Google maps.

2.3

User characteristics
User should be familiar with basic functionality of an android phone. The user should be able to
use the touch screen and the other navigation buttons along with the touch screen keyboard to
input data.

2.4

Constraints
Since the amount of memory and space is limited in an android phone, the database will not get installed
locally; instead it will connect to a remote server via internet and fetch required data. The application may
require a bit of processing power and database may need to be updated and expanded further. So there
should be a good internet connection which will also be used when connecting to Google maps.
One of the other constraints is that the application will not work on other platforms and will only work on
android 2.1 and later operating systems.

Confidential

iRoute, 2012

Page 5

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf
2.5

Version:
1.1
Date: 27/03/2012

Assumptions and dependencies

Android 2.1 has several features that are included in the application. For an example, Google Maps
external library, java support, touch screen support is used. The application should work on any
handset as long as it is running Android 2.1 or later.
Since the main dependency is Android SDK, the environment that they have set up is to use Eclipse as
the IDE, with a plug-in for SDK. Any issues with the emulator differing from the way an actual phone
will run the application will have to be considered.
It is also assumed that user input will only come in three forms, the touch screen, keyboard (if only
phone has one) and other buttons on the handset. Since each android phone has its unique buttons, they
will be only used to navigate back and forth and to terminate the application. Application will mostly
rely on touch screen (and keyboard) to perform the rest of the applications navigation.
The application will use an existing bus route database and bus ticket prices as at present. Also it will
depend on the Google maps external library to give the position of the user while travelling in a bus.
List of features will undoubtedly be modified throughout the development process, but any new
features should not have a massive effect on documentation or the overall goal.
In using the onscreen keyboard, it is assumed that the user is literate and can type English in selecting
locations.

3. Specific Requirements
3.1 Functionality
Accept User Input

Users are provided with a simple user interface to input (type) their start and end bus stations. The
drop down lists which will output a alphabetically sorted list of available bus stations in the
database, while typing. Users can use the touch screen keyboard or the physical keyboard of the
handset if available.

Output possible bus routes

Once the inputs are taken they are processed in the remote server and outputs trivial bus routes
according to an optimal path finding algorithm which minimizes the mismatches and conflicts
among routes.

Navigate with Google Maps

Confidential

Once the user selects a particular bus route he/she is provided with an option to navigate with
Google Maps. Users can preview their bus route in the map and can also view the location of their
own. This option is important in seeing the current position of the journey and planning the
transition of busses along the way.

iRoute, 2012

Page 6

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf
3.2

Version:
1.1
Date: 27/03/2012

Usability
Simple, Graphical User interface

The user interface is designed to be simple to use with graphical elements. Texts are simple, clear
and readable. Colors are used according to a theme which makes it more usable.

Minimal surprise

Interface is designed considering the user experience of using android application with providing
minimal surprise.

Ease of use

Full screen is used with right size buttons to suit big fingers. Easy navigation among windows and
menus.

User Guidance

Users are provided with a small help guide and tool tips.

3.3 Reliability
Availability

The server should be available 24/7/365 standby to serve user requests except the time of
maintenance or upgrade.

Accuracy

The output should be accurate to the best possible percentage and should avoid conflicting and
misleading outputs when the inputs are confusing. (Minimum defect rate). i.e critical bugs have to
be eliminated.

Mean time to recover

In a case of failure system should be able to recover within 1 day or so. (depending on the type of
damage)

3.4 Performance
Response Time

The output should be generated within a maximum of 10 seconds depending on the internet
connection speed and handset performance.

Transactions per second

The database can handle 15 transactions per second

Capacity

System can serve 20 users simultaneously.

Resource Utilization

Confidential

The application utilizes minimum amount of CPU and memory of the device.
iRoute, 2012

Page 7

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf

Version:
1.1
Date: 27/03/2012

3.5 Supportability
Coding standards and naming conventions

Proper coding and naming conventions are maintained to support any later changes or
modifications of code.

3.6 Design Constraints

Since this application runs on android platform, the application is bounded under several constraints.
Development is mainly based on Java language and has to rely on Android APIs, SDKs, plugins and tools.
Google maps external library will be used to add navigational functionality to the system. Eclipse IDE will
be mainly used for development word. Major changes to any of above will cause several changes to the
system.
For the first release of the application, only certain number of bus stations can be chosen to travel. Only the
bus stations in Colombo areas will be implemented. Further modification and expansion will be done in
later releases.
Time allocated for the project is about 2 months. All the project and documented within the time
constraint given,.
3.7 On-line User Documentation and Help System Requirements
Users will be provided with both online and offline help in case of need. Online help will be in
android market with necessary documents. Users can always take advantage of the help which
comes with the application itself.

3.8 Interfaces
3.8.1

User Interfaces
View objects are the basic units of user interface expression on the Android platform. The View
class serves as the base for subclasses called "widgets," which offer fully implemented UI objects,
like text fields and buttons.
The user will start the application process by selecting the application icon in the Android
menu. Once the inputs are given, the can be cleared and new inputs can be provided. Additional
options menu is accessible for further tasks.

3.8.2

Software Interfaces

Android API

Google/Google Maps API

Eclipse will be needed for the development portion of the project, and it will be utilizing the
Android software packages.

Confidential

iRoute, 2012

Page 8

iRoute
Software Requirements Specification
Software Requirements Specification_090534V.pdf
3.8.3

Version:
1.1
Date: 27/03/2012

Communications Interfaces
Client needs to communicate with the remote server using HTTP/HTTPS.

3.9 Licensing Requirements

3.9.1 Legal, Copyright, and Other Notices
GPL General public license

Confidential

iRoute, 2012

Page 9