Abstract

The modern world is guided by the change in the technology day by day. Mostly the
relevant changes in technologies are enhancing the modern business techniques.
Different technologies have been developed in the world for making people’s life
easier and better day by day. Android is the latest and a rapid growing technology
available for all the users or users in today’s market. An enormous increase in the end
user acceptance has been experienced in the past few years. The project is based on
the latest GPS technology which enables college management team a better way to
keep eye on the activity of the college buses and manage schedule as well as provide
real time bus location for the students using bus service. This paper proposes an
Android mobile phone application that gives information about buses, bus numbers as
well as bus routes/stops online. The proposed system is completely integrated online
bus tracking systems using database. It provides the facility of tracking the particular
college bus’s location in the google map. They can also view the bus details such as
bus schedule along with the arrival time.

Key Words:
Client-Server Application, GPS, Google Maps API, Database.

i
 List of Figures

1. GPS Technology------------------------------------------------------------------1

2. Use Case Diagram----------------------------------------------------------------5

3. Class Diagram---------------------------------------------------------------------5

4. ER Diagram------------------------------------------------------------------------6

5. App Screenshots------------------------------------------------------------------12

ii
 Table of Contents

TITLE PAGE

Abstract -------------------------------------------------------------------------------i

List of figures-------------------------------------------------------------------------ii

Chapter 1 Project Overview -----------------------------------------------------1

1.1 Introduction ------------------------------------------------------------ 1

1.2 Problem Statement ---------------------------------------------------- 2

1.3 Objectives -------------------------------------------------------------- 3

1.4 Applications ------------------------------------------------------------ 3

1.5 Project Features-------------------------------------------------------- 4

1.6 Feasibility Analysis --------------------------------------------------- 4

1.6.1 Technical Feasibility ------------------------------------------------4

1.6.2 Operational Feasibility ----------------------------------------------4

1.6.3 Economic Feasibility ------------------------------------------------5

1.7 System Requirements --------------------------------------------------5

1.7.1 Hardware Requirements ---------------------------------------------5

1.7.2 Software Requirements ----------------------------------------------5

Chapter 2 Literature Review -----------------------------------------------------6

Chapter 3 Methodology ------------------------------------------------------------7
3.1 Software Development Lifecycle -------------------------------------7
3.2 Use Case Diagram ------------------------------------------------------10
3.3 Class Diagram -----------------------------------------------------------10
3.4 ER Diagram --------------------------------------------------------------11
Chapter 4 Epilogue ---------------------------------------------------------------- 12
4.1 Expected Output ------------------------------------------------------- 12

4.2 Work Completed--------------------------------------------------------13

4.3 Work remaining---------------------------------------------------------13

4.4 Problem Faced ----------------------------------------------------------14

4.5 Work Schedule --------------------------------------------------------- 14

4.6 Result and Discussion --------------------------------------------------15

References -----------------------------------------------------------------------------16
CHAPTER 1: PROJECT OVERVIEW

1.1 INTRODUCTION
College Bus Tracking System is a system developed on Android Platform using java
programming language. It is based on client-server technology along with the use of
database. One Android user (College Bus Driver) sends real time location of the bus
with additional date and time information to the server. The information provided by
that user is stored in the database of the server. And other android users can get the
information through the server. The login page is available on the user app for the
college administrator. The administrator can keep the record of the bus such as bus
no., bus schedule, route info, driver contact, etc. on the database. The administrator
also has the permission to manipulate the bus record as per the needs. Student don’t
need to login. Student can search for the particular bus on the map. Students get
updated on the bus location at certain time interval so that they don’t have to wait for
the bus being unknown whether the bus is coming or has gone. So in summary, our
system handles all the data about current location of bus and by using this data the
real time tracking of bus can be done and this information is then given to remote user
who want to know the real time bus information. For development purpose some
technologies like GPS (Global Positioning System) and Google maps are used. The
system includes server-client based application, which gives real time location of bus
on Google Maps.

1
 Fig 1: GPS Technology

1.2 PROBLEM STATEMENT

Nowadays, many colleges are still using the traditional way of using paper and files to
keep record of the bus route and schedule as well as provides information through
notices which is not effective. So, there is need of a systematic way of keeping
records as well as providing information as per the need. Also Students even don’t
know about the proper timing of the bus. Some students wait for the bus being
unaware of that the bus had already been missed and they are late for the class.
Therefore, the smart system is necessary which provides real time information of bus
to remote user. So we proposed a new system which overcome the drawback of
college transportation system.

2
1.3OBJECTIVES
Following are the objectives of our system: -
1. To make the college transportation system more efficient.
2. To eliminate paper work and increase the level of accuracy.
3. To increase speed of service with the use of technology.

1.4 APPLICATION
Our system can be forwarded in other in order to enhance the business activities of the
public transport. Some other applications are: -
Vehicle tracking systems are commonly used by fleet operators for fleet management
functions such as fleet tracking, routing, dispatch, on-board information and security.
Theft and robbery: - Vehicle tracking systems are also popular in consumer vehicles
as a theft prevention and retrieval device. Police can simply follow the signal emitted
by the tracking system and locate the stolen vehicle.
Asset tracking: Companies needing to track valuable assets for insurance.
Field service management: Companies with a field service workforce for services
such as repair or maintenance, must be able to plan field workers’ time, schedule
subsequent user visits and be able to operate these departments efficiently.

3
1.5 PROJECT FEATURES
Following are the features of our application.

1. Administrator can track the activity of the college bus by sitting at any
location using internet.
2. Administrator can modify the bus schedule that is stored in the database.
3. Students can know the current location of the college bus online.
4. Provides the list of the schedule of the bus stops with its time on the user’s
phone.
5. Keeps the individual record of buses with their history of movement activity.
6. Provides the information of the bus regarding bus no, driver name, driver
contact, etc.

1.6 FEASIBILITY ANALYSIS

A feasibility study is an evaluation and analysis of the potential of the proposed
project which is based on extensive investigation and research to support the process
of decision making. The feasibility study is intended to be a preliminary review of the
facts to see if it is worthy of processing to the analysis phase. From the systems
analyst perspective, the feasibility analysis is the primary tool for recommending
whether the proceed to the next phase or to discontinue the project.

1.6.1 Technical Feasibility

Technical Feasibility is focused on gaining an understanding of the present technical
resources of the organization and their applicability to the expected needs of the
proposed system. It is the evaluation of the hardware and software and how it meets
the needs of the proposed system. The systems project is considered technically
feasible if the internal technical capability is sufficient to support the project
requirements.

1.6.2 Operational feasibility

4
Operational feasibility is the measure of how well the project will support the student
and the college administration during the operational phase. It is dependent on human
resources

available for the project and involves projecting whether the system will be used if it
is developed and implemented.

1.6.3 Economic Feasibility

Economic feasibility aims to determine the positive economic benefits to the
organization that the proposed system will provide. It typically involves a
cost/benefits analysis and it’s the most frequently used method for evaluating the
effectiveness of a new proposed system.

1.7 SYSTEM REQUIREMENTS

It indicates hardware and software requirements of the project at the time of project
development as well as project implementation.

1.7.1 HARDWARE REQUIREMENTS

Minimum hardware requirements for efficient operation of this project are as follows:
-
i. Intel Pentium IV processor or equivalent or higher
ii. 1 GB Ram or Higher
iii. 32 GB HDD or Higher
iv. Network Connectivity
v. Android phone having GPS functionality with Jellybean OS or above.

1.7.2 SOFTWARE REQUIREMENTS

Minimum software requirements for efficient operation of this project are as follows:
i. Android SDK
ii. MySQL
iii. Android Studio

5
6
CHAPTER 2: LITERATURE REVIEW

Nowadays many transportation systems are using the online bus tracking systems to
make their management more systematic and effective. In the context of Nepal, it is seen
that there is not much use this system and many of them uses traditional ways for taking
and giving information of records with pen and paper/notices. Some of the similar apps
that are running nowadays are listed below: -

My Next Bus in London: It is an Android app which displays nearest bus stops or
available busses. I like this app because it is very simple and intuitive. While timetables
are usually boring and complicated to look through, users of this app do not have to
search for anything, but information flows in a natural way. People can get information
about bus routes/stops as well as their surroundings (e.g. events, places and so forth). I
am planning to follow the same idea for our project.
Train Times UK: Another source of inspiration is this project where London underground
trains are shown on a map in quasi real time. That is so awesome! It would be very cool if
our college bus tracking system can have a similar system for college buses as well as
public transport.

7
CHAPTER 3: METHODOLOGY

3.1 Software Development Life Cycle (SDLC)

As the mobile applications have complex functionality the following Mobile Application
Development Lifecycle model is proposed to enable a systematic approach in
development.

1. Implementation Phase

In the first phase, ideas are collected and categorized. The main objective of this phase is
to come out with a new idea or improvements to the existing application. The ideas can
come from the user or from the developers. If the user himself comes out with the idea,
the idea is further detailed and analyzed. Developers can brainstorm to generate ideas for
new applications. The filtered list of ideas is discussed by the mobile application idea
team comprising of the business and IT representatives for the feasibility to launch a
project around the idea. If a similar application exists in the market, the popularity of the
application and the features supported are studied and compared. The differences with the
existing application(s) are documented. If no similar application exists on any mobile
platform, then the idea with its core functionality should be documented. The other
important task in this phase is to define the time required to develop the application. The
initial requirement gathering should also be completed. The work done by the mobile
application idea team should then be documented and forwarded to the design team.

2.Design Phase

In this phase, the idea from the mobile application team is developed into an initial design
of the application. The feasibility of developing the application on all mobile platforms is
determined. Alternatively, the specific target mobile platform is identified. A decision has
to be made on whether the developed application is to be released as a free version or
trial version with limited features or released only as a premium version. The application

8
functionality is broken down into modules and into prototypes i.e., combination of
modules which are to be released in the prototype fashion. The functional requirements
are defined. The software architecture of the application is created. Then the prototypes
and associated modules are defined. A very important part of the design phase is to create
the story board

for the user interface interaction: this storyboard describes the flow of the application.
The

design team’s work is documented and forwarded to the development team for coding.

3. Development Phase

In this phase, the application is coded. Coding for different modules of the same
prototype can proceed in parallel. The development process can be in two stages: Coding
for Functional Requirement and Coding for UI requirements. The code is developed first
for the core functionalities. Parallel development can be done for modules of the same
prototype that are independent of each other. Subsequently, these modules can be
integrated. In the second stage, user interface is designed so that it can be supported on as
many mobile operating system platforms as possible; it is not good practice to have a
different look and feel for the same application on different platforms. The minimum set
of interface components present in all mobile OS platforms should be used in the design.
Finally, the documentation of the development phase is then forwarded to the prototyping
phase.

4. Prototyping Phase

In this phase, the functional requirements of each prototype are analyzed; the prototypes
are tested and sent to the client for feedback. After feedback is received from the client,
the required changes are implemented through the development phase. When the second

9
prototype is ready, it is integrated with the first prototype, tested and then sent to the
client. The development, prototyping and testing phases are repeated until the final
prototype is ready. The final prototype is sent to the client for a final feedback. The work
done in this prototyping phase is documented and then forwarded to the testing phase.

5. Testing Phase

Testing is one of the most important phases of any development lifecycle model. The
testing of the prototype types is performed on an emulator/simulator followed by testing
on the real device. The emulator/simulator is often provided in the SDK. The testing on
the real device, for example in the case of Android operating system development, should
be performed on multiple operating system versions, multiple models of handsets with
variable screen size. The test cases are documented and forwarded to the client for
feedback.

6. Deployment Phase

Deployment is the final phase of the development process. After the testing is completed
and the final feedback is obtained from the client, the application is ready for the
deployment. The application is uploaded to the appropriate application store/market for
user consumption.

Before the application is deployed, the following steps are to be checked.

 Register as a developer on the respective application developer’s website by

paying the annual fee, if necessary, for respective OS.
 Check the rules and regulations of the application store for the deployment of an
application.
 Refine the application, for example, by removing all the log files and comments.
 Design the icon and wallpaper to be used on the application store.

 Create the file format required on operating system platform.

10
7. Maintenance Phase

The maintenance is the final phase of this model and this maintenance is a continuous
process. Feedback is collected from users and required changes are made in the form of
bug fixes or improvements. Appropriate security patches, performances improvements,
additional functionality, new user interfaces should be provided at regular intervals in the
form of updates to the application. The maintenance phase also includes the marketing of
the application: advertising and highlighting its unique features. If any application
requires a backend server: this server and related operating system must be maintained as
well.

3.2 Use Case Diagram

Fig 2: - Use Case Diagram for Bus Tracking System

11
3.2 Class Diagram

Fig 3: Class Diagram for Bus Tracking System

12
3.3 ER Diagram

Fig 4: ER Diagram

13
CHAPTER 4: EPILOGUE
4.1 Expected Output

Our project College Bus Tracking System is expected to be error free and user-friendly.
This also tends student to get access to a particular bus to get the information about the
bus location with time. This mobile application hopes to fulfil the needs of the students as
well as the college administrators. We hope the user will find the application useful and
helpful in action.

The main screen on the Bus Application side which is Driver app will have following
layout:

It will prompt user to enable the GPS and internet connection if not enabled.

14
Fig: Prompt for setting

After the connection is successful, it shows the latitude and longitude coordinates of
the device position and updates on the movement.

15
Fig: Show current location with updates

4.2 Work Completed

As our research work is still going on and we are not much familiarized with the
development tools, we only got success in completing about 45% of our work. Up to now
we have completed the work on the client or driver side application with positive result.
Our research work is still going on along with the code and testing.

4.3 Work Remaining

We have approximately 55% work remaining till now. We are giving our best attempt to
make the application useful, interactive and error free. Currently, we are working on that
55% work on the client and database part of our project.

16
4.4 Problem Faced
During our research session we got some problem in getting related projects. It was not
so easy to study on the relevant project and acquire knowledge about the working
mechanisms. We got some error while testing our app in Android Studio so we used an
android phone for the testing and debugging purpose. We got stuck in Google API for
some period but later on, continuing our research we also solved that issue.

4.5 Work Schedule

Our work schedule has been scheduled as below. Our total time of the project is
estimated to be 55 days in which the time schedule for different task is as follow in the
Gantt chart.

Documentation and Report

Testing and Debugging

Coding

Designing

Familiarization of Tools

Research Days

0 50 100 150 200 250 300 350

Figure 1: Gantt chart

17
4.6 Result and Discussion
While doing research on the project we divided our project work into modules and
assigned each module to each team member. We performed our task with a good team
coordination and support. We acquired more knowledge about the java programming
language. We also got some more useful ideas on this project. We learnt to use different
developer tools, software and also got the idea to debug the error along with error
handling. We also learnt some more about android application development while doing
our study and research work. In some difficult case we consulted with our teacher for
their guidance.

Despite of the problems we encountered while doing our project, we became success on
solving them and completing our project up to this level. So in overall, with our hard
team work and collaboration we have come this far and hope for the successful
completion of our project.

18
REFERENCES

[1] T.P. Liang, et al.,” Adoption of mobile technology in business-a fit viability model”,
Industrial Management & data systems, vol. 107, pp. 1154-1169, 2007.

[2] Daniel Mavcock, Slalom Consulting, “Enterprise Mobile Application Lifecycle.”

[3] http://javapapers.com/android/android-location-tracker-with-google-maps/

Accessed on-15th June

[4]http://www.codeproject.com/Articles/665527/A-GPS-Location-Plotting-Android-
Application Accessed on-15th June

[5] https://developer.android.com/guide/topics/location/strategies.html

Accessed on-16th June

[6]http://www.todroid.com/how-to-create-a-google-map-application-using-androidstudio/

Accessed on-17th June

19