TUTORIALSDUNIYA.

COM

Bus Route Enquiry

System
Software Engineering Project

Download FREE Software Engineering Projects for any

university student of BCA, MCA, B.Sc, M.Sc, B.Tech at
https://www.tutorialsduniya.com

If you find any error or mistake in this Software Engineering

project then report at [email protected]

Please Share these SE Projects with your Friends

 BUS ROUTE ENQUIRY SYSTEM

SOFTWARE ENGINEERING PROJECT REPORT

omm
B.Sc. (H) Computer Science

cco
a.
iy
un
slsD
aial
orri

SUBMITTED BY:
Aanandita Arun Jain Cecilia Ruby Dharm Vashisth
utot

16035500000 16035500000 16035500000 16035500000

TTu

Department of Computer Science

Keshav Mahavidyalaya
University of Delhi
 Acknowledgement

Apart from the efforts of team, the success of any project depends largely on the encouragement
and guidelines of many others. We take this opportunity to express our gratitude to the people who
have been instrumental in the successful completion of this project.

omm
The completion of any inter-disciplinary project depends upon cooperation, co-ordination and
combined efforts of several sources of knowledge.

cco
We are eternally grateful to our project supervisor TutorialsDuniya.Com for his even willingness to
give us valuable advice and direction; under whom we executed this project. His constant guidance
and willingness to share his vast knowledge made us understand this project and its manifestations

a.
in great depths and helped us to complete the assigned tasks. We are highly thankful to our project
internal guide TutorialsDuniya.Com, whose invaluable guidance helped us understands the project
better. Although there may be many who remain unacknowledged in this humble.

iy
un
slsD
aial
orri

Aanandita Arun Jain Cecilia Ruby Dharm Vashisth

utot

16035500000 16035500000 16035500000 16035500000

TTu
 Certificate

This is to certify that Software Engineering project report entitled “BUS

ROUTE ENQUIRY SYSTEM” is the work carried out by Aanandita, Arun

omm
Jain, Cecilia ,and Dharm Vashisth, students of B.Sc.(H) Computer Science 4th
Semester, Keshav Mahavidyalaya, University of Delhi under my supervision.

This report has not been submitted to any other organization/institution for the

cco
award of any other degree/diploma.

a.
iy
un
slsD
aial
orri
utot

TutorialsDuniya.Com TutorialsDuniya.Com TutorialsDuniya.Com

TTu

Supervisor Teacher In-charge Principal

 Abstract

In today's tech era, IOT (Internet of things) has become much popular around the world. Almost all
the devices, which are known as smart device, can connect to the internet and access data from any
corner of the world. There was a time when people used to waste their valuable times just to get a
piece of information. Now the technology is more advance then compare to any previous times. One

omm
of the blessings of technology is web application. It allows users to interact with the system from
anywhere as long as they are connected to the internet.

This report presents the work done on the project "DTC Bus System" which is a web application. As

cco
we already discussed above that internet has made the user’s interaction through the system easier,
so this web application can connect to respective servers for accessing data which will surely help
users to get information about bus routes and fare. Moreover, in recent decays peoples are like to

a.
travel to get some relief from their monotonous life. So, they want to travel without any hesitations.
In this modern tech era they want a system that will enhance the portability, accessibility as well as
user friendly. So here, we are going to implement a web system, which we already stated above,

iy
having all the features that will make it more user friendly and accessible.

The aim of this project was to develop a System that would help a public transport company to
un
manage its data.

Creation of Online DTC project is the slice unit which caters to customers who want to avail of quick
food service. This was conceptualized precisely for people on the go.Any one directly they can
slsD

register in this, then the admin will treat them as their customers. So at that time onwards the user
directly can login into this and he can get the food items by his order. Through this project we are
providing more user interaction.

It is having mainly two modules. One is at Administration Level and other one is of user.The
aial

Application maintains authentication in order to access the application. Administrator task includes
managing bus route information.To achieve this aim a database was designed in order to allow the
orri

bus transport company operators to enter, and store all time information about buses like route and
fare.
utot

The complaints which are given by user will be referred by authorities.

The user modules include checking bus route and fare. user can also register complaint againt
TTu

management or ask any query.

With the advent of computer technology and the internet ,users prefer to conduct their business
electronically to their convenience; This paper focuses on the need and construction to provide
same comfort and ease to the user.
 TABLE OF CONTENTS

1. Software Requirement Specification 1

Table of Contents..................................................................................... ii

omm
Revision History............................................................................................. ii

1.1 Introduction........................................................................................ 1

cco
1.1.1 Purpose..............................................................................................1

a.
1.2 Document Conventions.......................................................................... 1

1.3
iy
Intended Audience and Reading Suggestions............................................... 2
un
1.4 Project Scope.......................................................................................2

2 Overall Description............................................................................... 3
slsD

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

Product Features.................................................................................. 5
aial

2.2

2.3 User Classes and Characteristics............................................................... 6

orri

2.4 Operating Environment.......................................................................... 6

utot

2.5 Design and Implementation Constraints..................................................... 7

TTu

2.6 User Documentation............................................................................. 8

2.7 Assumptions and Dependencies............................................................... 8

2.8 Data Flow Diagram................................................................................................................10

2.9 Data Dictionary......................................................................................................................11

 3.1 System Features................................................................................... 12

4. External Interface Requirements.............................................................. 17

1.4.1 User Interfaces.....................................................................................17

1.4.2 Hardware Interfaces.............................................................................. 18

omm
1.4.3 Software Interfaces............................................................................... 19

cco
1.4.4 Communications Interfaces..................................................................... 19

Other Nonfunctional Requirements...........................................................20

a.
1.5.

iy
1.5.1 Performance Requirements.....................................................................20

1.5.2 Safety Requirements............................................................................. 20

un
1.5.3 Security Requirements........................................................................... 21
slsD

1.5.4 Software Quality Attributes..................................................................... 22

Appendix A: Glossary...................................................................................... 23
aial
orri

2.Size Estimation & Scheduling 25

2.1 Cost Estimation 25
utot

2.2Gantt Chart 28

3.Architectural Design 31
TTu

4.Risk Analysis 32
4.1 RMMM plan 32

5.Implementation 33
5.1 XML File 33
 5.2 Strings.xml 39

5.3JavaFile Code 40

6.Testing 44
6.1 Black Box Testing 44

6.2 White Box Testing 46

omm
7.User Manual 51

8.Conclusion 52

cco
9.References 53

a.
iy
un
slsD
aial
orri
utot
TTu
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well

 List of Figures
Figure 1- Data Flow Diagram........................................................................13

Figure 2-Data Dictionary..............................................................................14

Figure 3-Login Page......................................................................................24

omm
Figure 4-Web Portal......................................................................................24

Figure 5:- Screens..........................................................................................39

cco
Figure 6:-Architectural Design .....................................................................41

Figure 7:- RMMM..........................................................................................42

a.
Figure 8:-Code Module.................................................................................62

iy
Figure 9:- Flow Diagram................................................................................63
un
slsD
aial
orri
utot
TTu
 2

Chapter -1
SRS(Software Requirement Specification)

omm
1. 1Introduction
This document lays out a project plan for the development of “DTC Project”

cco
The plan will include, but is not restricted to, a summary of the system functionality,
the scope of the project from the perspective of the “DTC Project” team (me and my

a.
mentors), scheduling and delivery estimates, project risks and how those risks will be
mitigated, the process approach to develop the project, and metrics and

iy
measurements that will be recorded throughout the project.This document will
un
cover each of the system’s intended features, as well as offer a preliminary glimpse
of the software application’s User Interface (UI). The document will also cover
hardware, software, and various other technical dependencies.
slsD

1.1 Purpose
aial

The goal of this project is to provide a mobile application for DTC bus
passengers and a web-portal for DTC personnel and Company’s
orri

administrators , to build an online system to manages buses, fares and there

utot

schedules and passengers to ease the bus service management.

Product to be developed for Delhi Transport Corporation Govt. of
TTu

India, Ministry of Transport .

 3

1.2 Document Conventions

This document features some terminology which readers may be unfamiliar

withSRS: Software Requirement Specification

omm
Front End: This stands for the JSP pages that a user will see when (s) he will
access the application through the web.

cco
Vehicle: Transport entity used for transportation of passengers.

a.
Operator: A user which is hired for data entry of this system.

iy
Entry : A data unit stored to the database.
un
DESC : Description

RAT : Rational
slsD

DEP : Dependency
aial

Sign up: Creating New User

orri

log in : Logging in Existing User

utot
TTu

1.3 Intended Audience and Reading Suggestions

The intended readers of this document are current and future developers
working on “DTC Project” and the sponsors of the project.
 4

1.4 Project Scope

The “DTC Project” is a mobile application, which helps people to find the bus routes
to their desired destination and the fare. The DTC Project system is composed of two
main components: a client-side application which will run on Android handsets, and

omm
a server-side application which will support and interact with client-side queries.

users owners provide their destination information using the web-portal.

cco
the web-portal verifies logins as either passenger or administrator and manages user
information. The data will be held in an Access database on the DTC server.

a.
An administrator of DTC logins in to upload information about the bus routes or

iy
create a new database entry, update an existing database entry, or handle the
complaints and queries put forward by passenger .
un
The application should be free to download from either a mobile phone application
store or similar services.
slsD
aial
orri
utot
TTu
 5

2. Overall Description
2.1 Product Perspective

All system information is maintained in a database, which is located on a web-

omm
server. This includes user and admin information as well as information about
buses i.e their routes and fare.
An Internet connection is necessary to access the system , to fetch and

cco
display results and to sign up and log in .

a.
Since this is a data-centric product it will need somewhere to store the data.

iy
For that, a database will be used. Both the mobile application and web portal
will communicate with the database, however in slightly different ways. The
un
mobile application will only use the database to get data while the web portal
will also add and modify data. All of the database communication will go over
the Internet.
slsD

The mobile application has some restrictions about the resource allocation. To
avoid problems with overloading the operating system the application is only
aial

allowed to use 20 megabytes of memory while running the application. The

maximum amount of hard drive space is also 20 megabytes.
orri

2.2 Product Features

utot

The following list offers a brief outline and description of the main features and
TTu

functionalities of the DTC system. The features are split into two major
categories: core features andadditional features. Core features are essential
to the application’s operation, whereas additional features simply add new
functionalities.
 6

2.2.1 CORE FEATURES

2.2.1.1. USER REGISTRATION & WELCOME

omm
Only appears once (the first time the application is run)

Allows the user to register with the DTC server

cco
Enables the user to customize his/her account settings and preferences

2.2.1.2. SEARCH BUS ROUTE

a.
iy
Destination is entered
un
According to the route bus number is fetched from DTC server and displayed.

In addition the fare for the journey is also displayed.

slsD

2.2.2 ADDITIONAL FEATURES

aial

3. COMPLAINTS
orri

4.QUERIES
utot

With the mobile application, the users will be able to search for bus routes.
TTu

The result will be based on the source and destination of location the user
inputs. The result of the search will be viewed in a Tabular view with bus
number and fare as the output .
The web portal will provide functionality to manage the system and the route
information.
 7

2.3 User Classes and Characteristics

There are two types of users that interact with the system: users of the mobile
application, and administrators. Each of these types of users has different use
of the system so each of them has their own requirements.

omm
The mobile application users can only use the application to enter destination

cco
and find bus route. This means that the user is expected to be Internet literate.
The user interface will be as intuitive as possible. Thus, technical expertise

a.
and Android experience should not be an issue.

iy
The administrators only interact with the web portal. They are managing the
overall system so there is no incorrect information within it. The administrator
un
can manage the information for each bus number as well as the options for
the mobile application users by managing queries and complaints. This means
slsD

administrators are expected to be Internet literate and to be able to work with

database management .
aial

It is also important that the application be as user- friendly as possible ,Most

importantly, the application must be reliable.
orri

2.4 Operating Environment

utot
TTu

The main component of the DTC project is the software application, which will
be limited to

the Android operating system (specifically Android 5.0 and above). The
application is not
 8

resource- or graphics-intensive, so there are no practical hardware

constraints.
The app will rely on several functionalities built into Android’s Application
Programming Interface (API), so ensuring appropriate usage of the API will be
a major concern. Beyond that, the application is a self-contained unit and will

omm
not rely on any other Android-related software components.

The application will, however, frequently interact with the DTC server, a virtual

cco
dedicated

server hosted by GoDaddy.com. The server operates on a Linux CentOS

a.
platform with 1GB of

iy
RAM and 15GB of allocated storage space. The DTC database will be stored
on the server
un
using MySQL and will be interfaced with a wrapper written in PHP 5.

2.5 Design and Implementation Constraints

slsD

USER APP
aial

The primary design constraint is the mobile platform. Since the application is
orri

designated for
utot

mobile handsets, limited screen size and resolution will be a major design
consideration.
TTu

Creating a user interface which is both effective and easily navigable will pose
a difficult

challenge.
Other constraints such as limited memory and processing power are also
worth
 9

considering. DTC app is meant to be quick and responsive, so each feature

must be designed and implemented with efficiency in mind.

WEB PORTAL

omm
The system shall be built using a standard web page development tool that
conforms to either IBM’s CUA standards or Microsoft’s GUI standards.

cco
There are no memory requirements

a.
iy
The computers must be equipped with web browsers such as Internet explorer.
un
The product must be stored in such a way that allows the client easy access to it.

Response time for loading the product should take no longer than five minutes.
slsD

A general knowledge of basic computer skills is required to use the product

aial

2.6 User Documentation

orri

On-line User Documentation and Help System

utot

Requirements
TTu

As the product is available in play-store, On-line help system becomes a

critical component of the system which shall provide –

It shall provide specific guidelines to a user for using the E-Store system and
within the system. To implement online user help, link and search fields shall
be provided.
 10

Also a tutorial CD for visual walk through as well as an pdf document

explaining how to use will be provided to user at deployment time.

2.7 Assumptions and Dependencies

omm
The System will run on Web Server with Internet Connectivity

cco
The product shall be based on web and has to be run from a web server.

a.
iy
The product shall take initial load time depending on internet connection strength
un
which also depends on the media from which the product is run.
slsD

The performance shall depend upon hardware components of the

client/customer.
aial
orri
utot
TTu
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well

TTu
utot
orri
aial
2.8 Data flow diagram

slsD
11

un
iy
a.
cco
omm
TTu
utot
orri
aial
slsD
12

un
iy
a.
cco
omm
 13

3. System Features
The System Maintains information about Bus routes and Bus Fare . Of course ,this
Project has a high priority because it is very difficult to travel without prior
information about the Bus routes.

omm
3.1 System Feature 1
3.1.1 Description and Priority

cco
Description: There should be a separate login account for each

a.
user. Divided into admin and passenger.

iy
3.1.2 Stimulus/Response Sequences
un
The web page presented to the user ask for the user name/Id and
slsD

password,

then on clicking Submit button he will be redirected to his account.

Hitting the “enter” key should also login him.
aial

3.2 System Feature 2

orri

Description : Administrator shall be able to Enter/Edit/View Vehicle Details

utot

Response: In the Entering Phase Admin will enter bus route details using web form
and in the edit phase Admin will select bus route no and then edit information using
TTu

web form.

3.3. System Feature 3

Description : There shall be a provision of handling Queries
Response : Time table for vehicle , fare.
 14

3.4. System Feature 4

Description : The web server will crash no more than 2% of the time during
operation.

Response : Users need to be able to use the system as needed, and excessive

omm
crashes are not advisable.

cco
3.2 User Class 1 - The User

a.
3.2.1 Functional requirement 1.1

ID: FR1
iy
un
TITLE: Download mobile Software

DESC: A user should be able to download the mobile Software through either an
slsD

application store or similar service on the mobile phone. The application should be
free to download.

RAT: In order for a user to download the mobile application.

aial

DEP: None
orri
utot

3.2.2 Functional requirement 1.3

TTu

ID: FR3

TITLE: User registration - Mobile application

DESC: Given that a user has downloaded the mobile application, then the user should
be able to register through the mobile application. The user must provide user-name,
password and e-mail address. The user can choose to provide a regularly used phone
 15

number.

RAT: In order for a user to register on the mobile application.

DEP: FR1

omm
3.2.3 Functional requirement 1.4

cco
ID: FR4

TITLE: User log-in - Mobile application

a.
DESC: Given that a user has registered, then the user should be able to log in to the

iy
mobile application. The log-in information will be stored on the phone and in the
un
future the user should be logged in automatically.

RAT: In order for a user to register on the mobile application.

slsD

DEP: FR1, FR3

3.2.1.5 Functional requirement 1.5

aial

ID: FR5
orri

TITLE: Retrieve password

utot

DESC: Given that a user has registered, then the user should be able to retrieve
his/her password by e-mail / user id.
TTu

RAT: In order for a user to retrieve his/her password.

DEP: FR1
 16

3.2.1.6 Functional requirement 1.6

ID: FR6

omm
TITLE: Mobile application - Search

DESC: Given that a user is logged in to the mobile application, then the first page that
is shown should be the search page. The user should be able to search for a bus

cco
route to his destination .

a.
RAT: In order for a user to search for a Bus.

DEP: FR4
iy
un
3.2.1.18 Functional requirement 1.18
slsD

ID: FR18

TITLE: Mobile application - No match found

aial

DESC: If no match is found the user should be informed but kept on the search page
orri

in order to get the possibility to conduct a new search right away.

RAT: In order for user to conduct a new search if no match is found.

utot

DEP: FR5
TTu

3.2.3 User Class 3 - Administrator

 17

3.2.3.1 Functional requirement 3.1

ID: FR26

Feature: Administrator log in

In order to administer the system an administrator Should be logged in to the web-

omm
portal

Scenario: Successful log-in

cco
Given the administrator wants to log in

a.
When the administrator logs in with an administrator account

Then the administrator should be logged in as an administrator

iy
3.2.3.5 Functional requirement 3.5
un
ID: FR30

Feature: Manage Bus information

slsD

In order to manage Bus information an administrator Should be logged in to the

web-portal
aial

Scenario: Add bus route information

Given the administrator is logged in
orri

When the administrator adds bus route information Then the information should be
added to the database.
utot

Scenario: Delete Bus information

Given the administrator is logged in And information about a bus route exists
TTu

When the administrator deletes the information Then the information about the Bus
route should be deleted
Scenario: Edit bus information
Given the administrator is logged in And information about a bus route exists

When the administrator edits the information Then the information about the bus
 18

route and should be edited

4. External Interface Requirements

This section provides a detailed description of all inputs into and outputs from the
system. It also gives a description of the hardware, software and communication

omm
interfaces and provides basic prototypes of the user interface.

The protocol used shall be HTTP.

cco
The Port number used will be 80.

There shall be logical address of the system in IPv4 format.

a.
4.1 User Interfaces
iy
un
A first-time
time user of the mobile application should see the log
log-in
in page when
he/she opens the application, see Figure 2. If the user has not registered,
he/she should be able to do that on the log
log-in page
slsD

If the user is not a first-time

time user, he/she should be able to see the search
page directly when the application is opened, see Figure 3. Here the user type
the search he/she wants to conduct.
aial
orri
utot
TTu

Figure 1 -
Login page Figure 2 – Web Portal
 19

The administrators interact with the system through a web-portal, see Figure
2A.

An administrator should be able to log in to the web-portal where he/she can

administer the system by for instance editing route , fare or user information.

omm
4.2 Hardware Interfaces

cco
DTC app is intended as a mobile application for the Android platform and

a.
hence is solely

iy
supported on Android-powered devices.
The Android platform supports push messages that will be used to
un
synchronize data between

the local application and the main application server. Information will be sent
using TCP/IP and
slsD

the HTTP protocol.

The Android platform provides abstractions for all network communication

aial

interfaces and thus

orri

the hardware as well.

Since the application must run over the internet, all the hardware shall require
utot

to connect internet will be hardware interface for the system. As for e.g.
Modem, WAN – LAN, Ethernet Cross-Cable, mobile data.
TTu

The hardware connection to the database server is managed by the

underlying operating system on the mobile phone and the web server.
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well

 20

4.3 Software Interfaces

The communication between the database and the web portal consists of
operation concerning both reading and modifying the data, while the
communication between the database and the mobile application consists of

omm
only reading operations.
The DTC app is to be developed under the Android operating systems using

cco
the Java JDK

(Java Development Kit) and the Android SDK (software development kit)

a.
tools.

iy
4.4 Communications Interfaces
un
The DTC app shall use the HTTP protocol for communication over the internet
slsD

and for the intranet communication will be through TCP/IP protocol suite.
The communication between the different parts of the system is important
since they depend on each other. However, in what way the communication is
aial

achieved is not important for the system and is therefore handled by the
underlying operating systems for both the mobile application and the web
orri

portal.
utot

The DTC application will have a network server that is web-based and created
using the PHP (Hypertext Processing) language. The server exists to retrieve
TTu

information from the database and fare payments. The product also calls for a
database system that stores user information . The HTTP server will use a
push protocol to push notifications of updates onto the Android phones.
Furthermore, whenever a user opens the DTC app from their phone, a pull
protocol will be used to retrieve and sync the latest transaction updates from
the server.
 21

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Performance should not be an issue because all of our server queries involve

omm
small pieces of

data. Changing screens will require very little computation and thus will occur

cco
very quickly.

Server updates should only take a few seconds as long as the phone can

a.
maintain a steady signal. The fare calculation algorithms used by in

iy
application will be highly efficient, taking only a fraction of a second to
compute.
un
5.2 Safety Requirements
DTC app will not affect data stored outside of its servers nor will it affect any
slsD

other applications installed on the user’s phone. It cannot cause any damage
to the phone or its internal components. The only potential safety concern
associated with this application applies to virtually all handset apps: DTC app
aial

should not be used while operating a vehicle or in any other situation where
the user’s attention must be focused elsewhere.
orri

The customer’s web browser shall never display a customer’s password. It

utot

shall always be echoed with special characters representing typed characters.

The system’s back-end servers shall never display a customer’s password.
TTu

The customer’s password may be reset but never shown.

The system’s back-end servers shall only be accessible to authenticated

administrators.

The system’s back-end databases shall be encrypted.

 22

5.3 Security Requirements

This application assumes that only the user or whoever he/she allows will
have access to his/her Android handset. With that being said, only a Google
email or user id address is required to verify the identity of the user upon

omm
opening the app. Since it is not connected to any payment transaction
methods it and only used for look up this does not pose a threat to privacy
violation.

cco
The system shall use secure sockets in all transactions that include any

a.
confidential customer information.

iy
The system shall automatically log out all customers after a period of inactivity.

The system shall not leave any cookies on the customer’s computer containing the
un
user’s password.

The system shall not leave any cookies on the customer’s computer containing any of
slsD

the user’s confidential information.

5.4 Software Quality Attributes

aial

The graphical user interface of DTC app is to be designed with usability as the first
orri

priority. The app will be presented and organized in a manner that is both visually
appealing and easy for the user to navigate. There will be feedbacks and visual cues
utot

such as notifications to inform users of updates

TTu

To ensure reliability and correctness, there will be zero tolerance for errors in the
algorithm that computes fare To maintain flexibility and adaptability, the app will
take into account situations in which a user loses internet connection or for whatever
reason cannot establish a connection with the server. These users will still be able to
use the application.
 23

With DTC app being ported solely for the Android platform, this software application
has the advantage of being portable and convenient to use whenever and wherever.
Overall, the app balances both the ease of use and the ease of learning. The layout
and UI of the app will be simple enough that users will take no time to learn its
features and navigate through it with little difficulty.

omm
Appendix A: Glossary

cco
OFFLINE USER

An offline user may become a DTC BUS APP user by downloading the

a.
application and claiming their account.

User /Client: iy
un
This stands for the user accessing the application through the web browser or
slsD

Someone who interacts with the mobile phone application

Admin/Administrator
aial
orri

System administrator who is given specific permission for managing and

controlling the system
utot

Web-Portal
TTu

A web application which present special facilities for admin.

Application Store
 24

An installed application on mobile phone which helps user to find new

compatible applications with mobile phone platform and download themfrom

Internet

omm
cco
a.
iy
un
slsD
aial
orri
utot
TTu
 25

Chapter – 2
Estimation And Scheduling

Size Estimation

omm
 We have categorised external inputs on sub fields

If < 3 - Simple

cco
< 4 - Medium

>= 4 - Complex

a.
 For external output

iy
If 1 detail - Simple

2 detail - Medium
un
>2 detail - Complex

 We take all logical fields as well as external enquiry as simple

slsD

 External Input
aial

1. Login credential => Name, Password (medium)

2. Signup credential => I’d, Name, Phone number, (complex)
orri

3. Admin login => Name, Password, Key (medium)

4. Bus details add => (medium)
utot

5. Bus delete details => (medium)

6. Input querry => Source, Destination (simple)
TTu

7. Request => Details (simple)

8. Complaint => Details (simple)
 26

 External Output
1. Result => Bus details + Fare
(medium)
2. Request Ad. => Request at admin
(simple)

omm
3. Complain Ad. => Complain at admin
(simple)

cco
 Logical internal files (simple)
1. User login

a.
2. User signup
3. Bus info
4.
5.
iy
Reg. new service
Reg. complains
un
6. Fare calculated
7. Admin login
8. Bus route delete
slsD

9. Bus route add

10. Reg. handling
11.Complaint handling
aial

12.Assign key
orri
utot

 External interface files

TTu

 External enquiries
1. Bus details (result)
2. Complain (user can write)
3. Request (user can write)
4. Complain (admin can read)
 27

5. Request (admin can read)

Simple Medium Complex

External I/P 3 4 1
External O/P 2 1 0

omm
Logical Interface 2 0 0
External Interface 0 0 0
External Enquiry 5 0 0

cco
a.
iy
UFP = 3X3 + 4X4 + 1X6 + 2X4 + 1X5 + 12X7 + 5X3
un
= 9 + 16 + 6 + 8 + 5 + 84 + 15

= 143
slsD

CAF = 0.65 + 0.01 X 14 X 3

aial

= 1.07
orri

FP = UFP X CAF
utot

= 143 X 1.07
= 153.01
TTu

= 153 (approx)
 28

Cost Estimation
Screens - 7

Reports - 7

omm
3 GL - 1

Object Paint = 7X2 + 7X5 + 1X10

cco
= 14 + 35 + 10

= 59

a.
NOP = Object Point X ( 1- reuse)

= 59 X (1-0) iy
un
= 59

Efforts = NOP/ PROD

slsD

= 59/13 = 4.53

NOP = New Object Point

aial

PROD = Productivity
We assume nominal developer experience
orri
utot
TTu
 29

7 Screens Signup,Login,Admin,Complain(Admin),Request
Signup,Login,Admin,Complain(Admin),Request(Admin),Query(Admin),Query(User)
(Admin),Query(Admin),Query(User)

omm
cco
a.
iy
un
slsD
aial
orri
utot
TTu
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well

 30

Gantt Chart

SRS Cost & Size Design Implementation Testing User Mannual &
Estimation source code

omm
Deployment

Group Topic : DTC Bus Management

cco
Steps End Date

a.
SRS - 20 February

iy
Cost & Size Estimation - 27 February
un
Design - 13 March

Implementation - 27 March

Testing - 3 April
slsD

User manual & source code Deploy - 10 April

aial
orri
utot
TTu
 31

Chapter – 3
Architectural Design

omm
cco
a.
iy
un
slsD
aial
orri
utot
TTu
 32

Chapter – 4
Risk Management

Sno. RISK CATEGORY PROBABILITY IMPACT RMMM PLAN

omm
1 Some team Technical 30% 2 Use backup staffs
members leave risk which knows what
the project was going on in the
development project.

cco
in between.

2 Delivery Project risk 30% 1 Team may use extra

a.
deadline members to complete
tightened. the task on schedule

3 iy
Losing of all Project risk 20% 2
time.

Carry out necessary

un
the project backup of database
data. This may data, source code and
be caused by a documentation.
hard disk being
wiped out by a
slsD

virus, hard disk

failure etc.

4 Team Project risk 10% 3 We could set some

aial

dissension/lack guide lines and rules

of cohesion. how we deal with
each other.
orri
utot
TTu
 33

Chapter - 5
Implementation

omm
 Implementing Module for User Enquiries

XML FILE

cco
<?xml version="1.0" encoding="utf-8"?>

a.
<ScrollView
xmlns:android="http://schemas.android.com/apk/res/and
roid"
iy
xmlns:app="http://schemas.android.com/apk/res-auto"
un
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:background="#aaf"
android:layout_height="match_parent"
slsD

tools:context="com.example.dharmvashisth.bus_manageme
nt.MainActivity">
<LinearLayout
aial

android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_margin="8dp"
orri

android:orientation="vertical">
utot

<LinearLayout
android:layout_width="match_parent"
TTu

android:layout_height="wrap_content"
android:orientation="horizontal"
android:layout_margin="6dp"
>
<TextView
android:layout_width="65dp"
android:layout_height="wrap_content"
 34

android:id="@+id/from"
android:text="From"
android:textSize="20sp"
/>
<Spinner
android:layout_width="wrap_content"

omm
android:layout_height="wrap_content"
android:id="@+id/source"
android:layout_marginLeft="5dp"

cco
android:entries="@array/stands"

>

a.
</Spinner>

</LinearLayout> iy
un
<LinearLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:layout_margin="6dp"
slsD

android:orientation="horizontal"
>
<TextView
aial

android:layout_width="65dp"
android:layout_height="wrap_content"
android:id="@+id/to"
orri

android:text="To"
android:textSize="20sp"
utot

/>
<Spinner
TTu

android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/destination"
android:entries="@array/stands"
android:layout_marginLeft="5dp"

>
 35

</Spinner>

</LinearLayout>
<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"

omm
android:layout_gravity="right"
android:text="Find"
android:id="@+id/findr"

cco
android:textSize="16sp"
android:background="#43a"
android:textColor="#eef"

a.
/>
<TextView

iy
android:layout_width="match_parent"
android:layout_height="155dp"
un
android:id="@+id/result"
android:textSize="24dp"

android:shadowColor="#f00"
slsD

android:hint="Bus Details and fare "

/>
<LinearLayout
aial

android:layout_width="match_parent"
android:layout_height="wrap_content">
<EditText
orri

android:layout_width="234dp"
android:layout_height="wrap_content"
utot

android:id="@+id/request"
android:hint="Request"
TTu

android:background="#fff"
android:inputType="textMultiLine"
/>
<Button
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="18dp"
 36

android:id="@+id/btnRequest"
android:text="Submit Request"
android:background="#43a"
android:textColor="#eee"

/>

omm
</LinearLayout>

cco
<LinearLayout
android:layout_width="match_parent"
android:layout_height="wrap_content"

a.
android:layout_marginTop="16dp"
>
<EditText
iy
android:layout_width="234dp"
un
android:layout_height="wrap_content"
android:id="@+id/complain"
android:hint="Complain"
android:background="#fff"
slsD

android:inputType="textMultiLine"
/>
<Button
aial

android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginLeft="18dp"
orri

android:id="@+id/btnComplian"
android:text="Register Complain"
utot

android:background="#43a"
android:textColor="#eee"
TTu

/>

</LinearLayout>

</LinearLayout>

</ScrollView>
 37

Strings.xml

<resources>
<string name="app_name">Bus Management</string>

omm
<string-arrayname="stands">
<item>Budh Vihar</item>
<item>Mangolpuri Y block</item>
<item>Mangolpri khurd</item>

cco
<item>Avantika</item>
<item>West Enclave</item>

a.
<item>Keshav Mahavidyalaya</item>
<item>Rani Bagh</item>

iy
<item>Shakurpur</item>
<item>Britania Chowk</item>
<item>NSP</item>
un
<item>Delhi Hatt</item>
<item>Madhuban Chowk</item>
<item>Rohini East</item>
slsD

<item>Rohini West</item>
<item>Rithala</item>
</string-array>
</resources>
aial
orri
utot
TTu
 38

JavaFile Code
Package com.example.dharmvashisth.bus_management;

omm
import android.content.Intent;
import android.graphics.Typeface;
import android.support.v7.app.AppCompatActivity;

cco
import android.os.Bundle;
import android.view.MenuItem;
import android.view.View;

a.
import android.webkit.URLUtil;

iy
import android.widget.Button;
import android.widget.EditText;
un
import android.widget.Spinner;
import android.widget.TextView;
import android.widget.Toast;
slsD

public class MainActivity extends AppCompatActivity implements

View.OnClickListener{
aial

EditText complain,request;
Spinner src,des;
orri

Button find,req,comp;
TextView result;
utot

StringBuilder res,bno;
@Override
TTu

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

getSupportActionBar().setDisplayShowHomeEnabled(true);
getSupportActionBar().setDisplayHomeAsUpEnabled(true);
 39

complain=(EditText)findViewById(R.id.complain);
request=(EditText)findViewById(R.id.request);
src=(Spinner)findViewById(R.id.source);
des=(Spinner)findViewById(R.id.destination);

omm
result=(TextView)findViewById(R.id.result);

cco
Typeface
typeface=Typeface.createFromAsset(getAssets(),"xoxoxa.ttf");
result.setTypeface(typeface);

a.
find=(Button)findViewById(R.id.findr);

iy
req=(Button)findViewById(R.id.btnRequest);
comp=(Button)findViewById(R.id.btnComplian);
un
request.setVisibility(View.INVISIBLE);
complain.setVisibility(View.INVISIBLE);
slsD

find.setOnClickListener(this);
req.setOnClickListener(this);
aial

comp.setOnClickListener(this);
orri

}
utot

@Override
public boolean onOptionsItemSelected(MenuItem item) {
TTu

if(item.getItemId()==android.R.id.home)
{
Toast.makeText(getApplicationContext(),"Sign
Out",Toast.LENGTH_SHORT).show();
Intent back=new
Intent(this.getApplication(),login.class);
 40

this.finish();
startActivity(back);
}
return super.onOptionsItemSelected(item);
}

omm
public void fareCalculated(int stand)
{
int f;

cco
if(stand<6)
{
f=5;

a.
}
else if (stand<11)
{
iy
f=10;
un
}
else
{
slsD

f=15;
}
bno.append("\nFare : ");
aial

bno.append(f);
orri

result.setText(bno.toString());
}
utot

public void busInfo()

{
TTu

int flg=1;
bno=new StringBuilder();
int stand=0;
bno.append("Bus No. : ");
stand=des.getSelectedItemPosition()-
src.getSelectedItemPosition();
 41

//starts from 3rd stand

if(src.getSelectedItemPosition()>1&&des.getSelectedItemPositio
n()>1)
bno.append(" 948 ");
// starts from 2nd stand

omm
if(src.getSelectedItemPosition()>0
&&des.getSelectedItemPosition()>0)
bno.append(" 983 ");

cco
if(src.getSelectedItemPosition()==des.getSelectedItemPosition(
))
{

a.
flg=0;
}
else
iy
bno.append(" 743 ");
un
if(flg==1)
slsD

fareCalculated(stand);
else
result.setText("Ïnvalid Input");
aial

}
orri

@Override
public void onClick(View view) {
utot

switch(view.getId())
TTu

{
case R.id.findr:
Toast.makeText(this, "Result Computing...",
Toast.LENGTH_SHORT).show();
result.setText("");
busInfo();
 42

break;
case R.id.btnComplian:
complain.setVisibility(View.VISIBLE);

Toast.makeText(this, "Complaint Clicked",

omm
Toast.LENGTH_SHORT).show();
break;
case R.id.btnRequest:

cco
request.setVisibility(View.VISIBLE);
Toast.makeText(this, "Request Clicked",
Toast.LENGTH_SHORT).show();

a.
break;
}
}}
iy
un
slsD
aial
orri
utot
TTu
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well

 43

Chapter – 6

Testing
Black Box Testing

omm
 Equivalence Class Testing

cco
*SNO = No. Of stands covered
*src=Selected source stand index

a.
*des=Selected Destination stand index
*sc=Stands Covered
iy
un
Input Equivalence Class
slsD

 Valid Input Classes

I1={ 0<= src <15 }
aial

I2={ 0<= des <15 }

orri

 No Invalid Inputs in Query to input Source and Destination

utot
TTu

Output Equivalence Testing

 Output Classes
O1={ src==des , Invalid Input}
 44

O2={ src=0 && sc<=5 ,Bus No : 743 Fare : 5 }

O3={ src=0 && sc<=10 ,Bus No :743 Fare : 10 }
O4={ src=0 && sc<=15 ,Bus No : 743 Fare : 15}

omm
O5={ src=1 && sc<=5 ,Bus No : 983 743 Fare : 5}
O6={ src=1 && sc<=10 ,Bus No : 983 743 Fare : 10}

cco
O7={ src=1 && sc<=15 ,Bus No : 983 743 Fare : 15}

a.
O8={ src=2 && sc<=5 ,Bus No : 948 983 743 Fare : 5}

iy
O9={ src=2 && sc<=10 ,Bus No : 948 983 743
un
Fare : 10}
O10={ src=2 && sc<=15 ,Bus No : 948 983 743
slsD

Fare : 15}
aial

White Box Testing

orri

 Basic Path Testing

utot
TTu

Module Code for Testing

*Entry Point is busInfo()
 45

omm
cco
a.
iy
Flow Diagram For fareCalculated()
un
slsD
aial
orri
utot
TTu
 46

Flow Diagram

omm
 P denotes data flow diagram for fareCalculated()

cco
a.
iy
un
slsD
aial
orri
utot
TTu
 47

omm
cco
a.
iy
un
Cyclomatic Complexity Calculations
slsD

Edges(e)=47
Vertices(v)=41
aial

Cyclomatic complexity( cc)= e – v + 2

orri

= 47 – 41 + 2
utot

=6+2
TTu

=8
Hence , there will be 8 independent paths.
 48

Independent Paths

1.

omm
2.

cco
3.

a.
4.
iy
un
5.

6.
slsD

7.
aial

8.
orri
utot
TTu
 49

Chapter – 7
User Manual
1.0 Introduction

omm
The “DTC Project” application allows users a simple interface to access their account from a
mobile device to view bus route and fare information. This document will provide
instructions for using the application .

cco
2.0 Getting Started
Download and install the “DTC Project” application availavle on play store or istore . The

a.
application is compatable with Android versions 5.0(Lollipop) and above.

2.x Quick Start : USER

iy
STEP 1 : Tap the “DTC Bus” icon in your device menu. The Sign up screen will be brought up.
un
STEP 2 : First time users need to sign up by providing their information ( name , contact
number and password) . “SAVE ACCOUNT” will create their unique account .

STEP 3 : Recurring user already having account need to log in to use the application by
slsD

providing their user name and password.

STEP 4 : Once you are loged in , Enter your Source and Destination stops from the drop
down menu available according to bus routes available and the corresponding route
aial

number and fare will be displayed

STEP 5 : In case of query or complaint use “SUBMIT REQUEST” and “REGISTER COMPLAINT”
orri

options provided on the same page.

utot

2.x System Requirements

Smartphone with Android versions 5.0(Lollipop) and above.
TTu

Internet connection for first time login.

3Troubleshooting

Missing or Incorrect Password or E-Mail

A message will be displayed in the event incorrect login information is entered. Try again
with proper credentials to access
 50

Chapter -8
Conclusion
The entire project has been designed and developed as per the requirements of

omm
the user. It is found to be bug free as per the testing standards that are
implemented.

cco
The whole system’s activities are divided into two major parts likeUser and
admin. For implementing the system Android studio is used.
The system comprise of following features:

a.
Display bus number
Calculation of fare

iy
Record requests from the user
Record Complaints of the user
un
The estimated cost of the project is (efforts) 4.53 PM and the estimated size of
the project is 153FP.
slsD

t
There are also few features which can be integrated with this systemto make it
more flexible. Below list shows the future points to be
consider :
aial

 Getting the current location of the bus.

Generating bus passes.
orri

Finally, we like to conclude that we put all our efforts throughout the
utot

development of our project and tried to fulfill most of the requirements of the
user.
TTu
 51

Refrences

1. https://www.tutorialsduniya.com

2. IEEE Software Engineering Standards Committee, “IEEE Std 830-1998,

omm
IEEE Recommended Practice for Software Requirements
Specifications”, October 20, 1998.[IEEE] The applicable IEEE
standards are published in “IEEE Standards Collection,” 2001

cco
edition.

a.
3. The principle source of text book material is “Software

iy
Engineering A PRACTITIONER ’ SAPPROACH” by Roger S.
Pressman.
un
4. The principle source of text book material is “A Concise
slsD

Introduction to Software Engineering” by Pankaj Jalote.

5. https://www.tutorialsduniya.com
aial
orri
utot
TTu
 TutorialsDuniya.com

Download FREE Software Engineering Projects PDF for any

university student of BCA, MCA, B.Sc, B.Tech, M.Sc at
https://www.tutorialsduniya.com

 3 Level Authentication  Airline Reservation System

 Banking Management System  Bus Route Enquiry System
 Car Showroom Dealership  Cricket Management System
 Criminal Record Management  E-Boutique
 Exam & Result Management  Health Care
 Hospital Management System  Online Bookstore
 Online Complaint Portal  Online Event Booking
 Online MetroCard Recharge  Online Missing Person Info
 Online Shopping  Online Shopping System
 Our First Home  Railway Reservation System
 Reality Show Management  Tour & Travel Management
 Smart City Traveller  Weather ForeCasting

Many more FREE Software Engineering Projects are available at

https://www.tutorialsduniya.com

Please Share these SE projects with your Friends as well