This document appears to be the table of contents and introduction section of a student project proposal on developing a mobile application for bus ticket booking. It outlines the current problems with manual and separate ticketing systems used by different bus companies, including long queues and lack of information sharing. The objectives are to create a centralized system allowing online booking and validation of tickets via mobile phones for improved convenience and coordination across companies. The significance and scope are also briefly discussed to introduce the purpose and goals of the proposed system.

1. i
DECLARATION
I MICHAEL Aminiel with registration number NIT/BIT/2016/402 declare to the best of my
knowledge that the project presented here, as a partial fulfillment of Bachelor Degree in
Information Technology, is my own work and has not been copied anywhere or presented
elsewhere.
CANDIDATE NAME SIGNATURE DATE
MICHAEL AMINIEL . .
SUPERVISOR NAME SIGNATURE DATE
MR. PETER MWAKALINGA . .

2. ii
ABSTRACT
The chapter one introduces what this proposal is for, it explain the problem, and explain about
background section. Also in the problem statement section it explain in detail about the problems
which arises in the current system, then it introduces the main objective of this project and its
specific objectives which will be used to build up the proposed system, lastly it explain the
significance of the project.
Chapter two describes the existing system how it works and its weakness and also explains the
related works that has been done in other place around the world and lastly introduces the
proposed system, how it will work and its strength.
The chapter three explains about methodology that will be used form beginning up to
accomplishment of this project. Chapter three explain about data collection how the data were
collected by using questionnaire and observation methods and what kind of the questions asked
in Questionnaire section and the data presentation based on the comments from the users answers
to the question asked. Chapter four explain about system requirements and specification i.e.
functional and non-functional requirements. Chapter five explain about budget and timeframe for
the whole project to complete and the cost estimated for the project cost.

3. iii
ACKNOWLEDGEMENT
First, I would like to thanks the almighty GOD for keeping me alive until this moment.
Thanks to the government of Tanzania and to my Institute, Thanks to the department academic
staffs and department assessors for their challenges and contributions that made me strong
In addition, I would like to thanks my supervisor Mr. Mwakalinga for his exceptional guidance
throughout the project period.
Thanks to my family for their support in prayers and my daily needs.
Lastly, without forgetting many thanks to my classmates for their exceptional cooperation and
daily challenges that they give me.

4. iv
TABLE OF CONTENTS
Contents
DECLARATION ..........................................................................................................................i
ABSTRACT.................................................................................................................................ii
ACKNOWLEDGEMENT ..........................................................................................................iii
TABLE OF CONTENTS ............................................................................................................iv
LIST OF FIGURES.....................................................................................................................vi
LIST OF TABLES .....................................................................................................................vii
CHAPTER 1: INTRODUCTION ............................................................................................... 1
1:1 Backgrounds.......................................................................................................................... 1
1.2 Problem statement................................................................................................................. 1
1.3 Project objectives .................................................................................................................. 2
1.3.1 General objectives.............................................................................................................. 2
1.3.2 Specific objectives.............................................................................................................. 2
1.4 Significance of the project..................................................................................................... 2
1.5 Project scope ......................................................................................................................... 3
CHAPTER 2: LITERATURE REVIEW .................................................................................... 4
2.1 Study of the existing system.................................................................................................. 4
2.2 weakness of the existing system............................................................................................ 4
2.3 Review of the proposed system............................................................................................. 4
2.4 Strengths of the proposed system.......................................................................................... 5
CHAPTER 3: METHODOLOGY .............................................................................................. 5
3.0 METHODOLOGY AND DATA COLLECTION.................................................................... 5
3.1System development method ..................................................................................................... 5
3.1.1Description of system development life cycle .................................................................... 6

5. v
Requirement analysis............................................................................................................... 6
3.2Data collection.................................................................................................................... 7
3.3 DATA ANALYSIS ............................................................................................................... 8
3.4 Cost estimation...................................................................................................................... 8
3.5 Project schedule..................................................................................................................... 9
CHAPTER 4: REQUIREMENTS AND SPECIFICATIONS .................................................. 10
4.1 SYSTEM REQUIREMENTS ............................................................................................. 10
4.1.1 Functional requirements................................................................................................... 10
4.1.2 Non-Functional Requirement........................................................................................... 10
4.2 Use case diagram................................................................................................................. 12
4.3 System Requirements.............................................................................................................. 13
CHAPTER 5: DESIGN............................................................................................................. 14
5.1 Logical design (basic/General Design) ............................................................................... 14
5.2 Conceptual design (Detailed Design).................................................................................. 16
5.3 Interface Design ...................................................................Error! Bookmark not defined.

6. vi
LIST OF FIGURES
Figure 3.1 Diagram of agile methodology ................................................................................... 6
Figure 4.1 use case diagram........................................................................................................ 12

7. vii
LIST OF TABLES

8. 1
CHAPTER 1: INTRODUCTION
Public transportation has been classified as an essential mode of travelling. Public in many
countries, especially in the third world, prefer to use buses and train services to travel from one
location to another. Bus pass and ticketing system is the ticketing system which uses self-service
technology as a base of mobile application helping the user to book a ticket by them.
Recently, with the introduction and evolution of smartphones applications, the consumers’
behavioral habits have changed in the goods and services purchasing power. Consumers’ on-line
purchases using mobile application had increasing globally, without boundaries. Consumers’ or
the public population, in current age, can purchase their transport ticket through mobile phone
and pay on-line to book, validate and retrieve tickets using simple mobile applications.
1:1 Backgrounds
Mobile devices have larger impact in our daily life. The proposed project is concerned with
ticketing and identification of the passenger in the public transport service. Currently, the sold of
bus ticket is still done manually which is customers who want to buy the bus ticket need to go to
the counter and buy the bus ticket manually. In addition, users also cannot buy the bus tickets
over the phone and the phone line is always busy. It brings a lot of inconvenience to the user.
Users also need to go to the bus port to get tickets and ask for about the bus schedule. This
causes them to arrive early to the bus station so that the bus ticket is not sold out. The other
problem is the possibility to miss the bus tickets, bus tickets is stolen or left behind. This causes
the user to go back to the bus station to buy a ticket
1.2 Problem statement
Most public transportation modes in Tanzania, except air transportation still use the traditional
ticket system, which use a paper based ticket. But some of bus companies they have their own
ticketing system but the problem is poor management of the system and how the passengers will
access the system. The problem with the traditional ticket bus system (manual ticket) is when
users have to stand up in a long queue to buy a bus ticket or asking information for buses
schedule. The main issue with manual system is each bus company work separately some with
their own system while others they still using manual system; communication must be made by
each branch’s front-officer to the head office for each customer’s enquiry in order to get the

9. 2
latest update on schedule, seat availability and other reservation-related information; as well as to
avoid duplicate bookings or over-capacity). Moreover, there is also a physical limit to the
reservation availability as each branch only operates during certain hours and reservations can
only be made on-the-spot. These limitations are not the only issues the company is currently
facing. In addition, that create problems include human errors (e.g. miscalculations in ticket
price, mistakes in noting passenger data, etc.). Furthermore, manual booking system the paper
works can be easily lost the storage space and costs.
1.3 Project objectives
The project objectives have divided into two categories as follows.
1.3.1 General objectives
The main object is to develop a mobile application which will help the passengers to buy the bus
ticket over the Internet, 24 hours a day throughout the week, and do all bus pay through their
credit card or using mobile money transfer like m-pesa, airtel money or tigo pesa. This solves
the issue of bus ticket being misplaced or stolen It helps passengers get tickets with ease and buy.
1.3.2 Specific objectives
 Manage reservations and seating effectively
 Safe and secure payment gateway module
 Detail reports for managing trips - Save time spent by standing in queue for purchase of
your Pay online using online payment facility
 Take a ticket printout - Counter booking using online application
 Generate detailed report of sales details
 Manage various trips, rates and types
 Allow users to reserve seats online
1.4 Significance of the project
 Helps passengers get tickets with ease.
 Passengers need not stand in queues for getting the ticket.
 No need to print tickets.
 You can find all the bus pass related information online without going to the bus station.

10. 3
 This online bus pass software system will help passengers get bus passes online and
eliminate the need of standing in queues for passes or collecting a ticket for journey.
 The payment can be done online via credit or master card or mobile money transfer like
M-pesa or tiGo pesa.
 Passengers first need to verify themselves the system using various address and photo
proofs. Once verified the system allows them to book passes for any route online.
 The app is also used to collect information about the travel of the passenger and helps
government in bringing new plans helping the passenger.
1.5 Project scope
Bus pass and ticketing mobile application will base on all android devices and will be access by
downloading it from android play store. After the user downloads the app he/she required to
register to the system for authentication purpose to know the users who is accessing the system
in order to get access and ready for use. This application will allow user to select for the route
he/she want to travel then app will give him/her the action to select bus company registered
under the given route which he/she select. The user can also select the specification of bus i.e.
upper class or luxury bus for such company. The user can recharge his account through net
banking, pay pal, or from his mobile account through mobile money transfers m–pesa, tigo pes
or airtel money without visiting any bus depot. An interface can also be added in android app
that user can see the bus route and cost for a journey from source to destination. After the user
paid for seat needed to upload authorization photo to verify his/he payment. After filling the
required details, the user receives a unique id. The user just needs to show this id to the ticket
checker. The Ticket Checker enters this ID in his android application and thus can retrieve the
user details like the photo of the person, source and destination of the pass, validity of the pass

11. 4
CHAPTER 2: LITERATURE REVIEW
2.1 Study of the existing system
In existing system there was a pass type electronic ticketing which was fixed for same source and
destination and It was of two type monthly card payment and passengers can visit the bus port
and stand in the queue waiting for ticket and pass. The passenger has to visit the bus depot to
renew his/her account and NFC tag was used and data was entered to that card and it was
scanned in each travel from source to destination and it expires at the end of month or quarter as
per account type, but proposed mobile application system is quite flexible that is it has to renew
as per user’s need and source and destination is also flexible, as per the journey cost the amount
is deducted from passengers account so it is easy , fast and less cash handling process. So the
existing system is not user friendly. In that either customer can board the bus and then take the
ticket or he can use pass for monthly and quarterly for fixed source and destination. Sometime
change issue also gets create. Passenger and conductor both don’t have change for ticket amount
which creates issue. This is standard method works in the public transport.
2.2 weakness of the existing system
i. Every bus company working separately with theirs own system which give difficulties to
select the bus of his/her choice in term of quality and affordable prices
ii. Poor management of government tax due to every bus company operate in their own
system which is difficult for tax regulatory to determine the exactly tax required to paid
by the bus company per trip.
iii. The problem of some bus companies with the traditional ticket bus system (manual
ticket) is when users have to stand up in a long queue to buy a bus ticket or asking
information for buses schedule.
2.3 Review of the proposed system
The proposed mobile application system is quite flexible that is it has to renew as per user’s
need and source and destination is also flexible, as per the journey cost the amount is deducted
from passengers account so it is easy , fast and less cash handling process. The payment can be
done online via credit or master card or mobile money transfer like M-pesa or tiGo pesa.
Passenger’s first need to verify themselves to the system using various address and photo proofs.
Once verified the system allows them to book passes for any route online. will help passengers

12. 5
get bus passes online and eliminate the need of standing in queues for passes or collecting a
ticket for journey.
2.4 Strengths of the proposed system
The proposed system will have many advantages and the following are its strength
 Helps passengers get tickets with ease because they can just download the application
through their android smartphones to access the bus route information and book for
tickets.
 Passengers need not stand in queues for getting the ticket.
 No need to print tickets.
 Help the passengers to find all the bus pass related information online without going to
the bus station.
 Enable the organization responsible for transport regulatory authority (SUMATRA) to
regulate the transport fare for every specific route registered to the system.
CHAPTER 3: METHODOLOGY
3.0 METHODOLOGY AND DATA COLLECTION
3.1System development method
This agile process is an iterative approach in which customer satisfaction is at highest priority as
the customer has direct involvement in evaluating the software. An Agile approach focuses on
adaptability and response time to changing requirements. The studies of the hardware, software

13. 6
and technology that can be used are also being conducted. The design phase where the process of
designing the proposed system will be initiated in this phase where the solutions have been
proposed in the model based on the information that has been obtained.
3.1.1Description of system development life cycle
Figure 0.1 Diagram of agile methodology
Requirement analysis
This is the phase in which we going to collect the information from them by using Questionnaire
and Observation methods of data collection. The Questionnaire method is the best since the
targeted users/client can fill the questionnaire at his free time and later you can collect it rather
than using the interview methods, which is costly, and time consuming. Moreover, the
Observation method is the best since it will be observed how the current system works and how
the proposed system will work and in which environment

14. 7
Analysis
After collecting data we will sit down and analyze the information, we gathered from the site to
see what the user wants and how will deliver it to them so they can satisfy and solve their facing
challenges
Design
After it is finished the analyzing and determining what the user wants, in this phase we start the
designing of the system based on what we got from the analysis phase. The tools that have been
used in the designing conception and basic design of the system is Microsoft Visio 2016 since it
has many functionalities and it is wide used, and UML which is the Visual languages for
representing how the system will react to internal and external environment.
Coding
After finishing the design here is where we implemented the code and the language to write the
code will be java using android studio IDE to develop an application for bus registration, route
and ticketing system.
Testing
Before the system implementation the system will deliver partially to the customer to know if the
system meets their requirements. If the system does not the requirements we will start to
analyze the requirements need by the customer and start from the first phase.
3.2Data collection
As explained in the phase of requirement gathering in the methodology part, the methods which
chosen in order to collect data are questionnaire and observation method
Questionnaire
In the questionnaire method, the list of the open-ended questionnaire was prepared for collecting
information on how the proposed system will work and what will be the input to the proposed
system.

15. 8
Observation
In the observation method, the case study was visited to see how the current system works and
what will be expected from the proposed system and in what environment the proposed system
will work in order to deliver maximum efficiency.
3.3 DATA ANALYSIS
Percentage of smartphone users in Tanzania Currently it’s 52%
Population of retailer Approximately every street has one
Population of wholesales (middle man) Approximately every district has one
Percentage of mobile app users worldwide Approximately 86%
3.4 Cost estimation
S/N. Component Activity Cost
1 Stationary Cost Printing, Photocopy, Binding 70,000/=
2 Communication Cost Internet services and Telephone
communication
50,000/=
3 Flash disk For storage and backup 20,000/=
5 Miscellaneous Emergency and Transportation 50,000/=
Total 190,000/=

16. 9
Table 3.1 Cost estimation
3.5 Project schedule
WEEKS 1 2 3 4 4 6 7 8 9 10 11 12 13 14 15 16
TASKS
PLANNING
DESIGN
CODING
TESTING
DELIVERY
Table 3.2 project schedule

17. 10
CHAPTER 4: REQUIREMENTS AND SPECIFICATIONS
4.1 SYSTEM REQUIREMENTS
4.1.1 Functional requirements
Functional requirements define the specific functions that the system performs, along with the
data operated on by the functions. The functional requirements are presented in scenarios that
depict an operational system from the perspective of its end users.
 The system shall incorporate mechanism to authenticate its users.
 The system shall verify and validate all user input and should notify in case of error
detection and should help the user in error correction.
 The system shall allow sharing of files in the system.
 The system shall allow quick messages to be exchanged without face to face interaction.
4.1.2 Non-Functional Requirement
Non-functional requirements address aspects of the system other than the specific functions it
performs. These aspects include system performance, costs, and such general system
characteristics as reliability, security, and portability. The non-functional requirements also
address aspects of the system development process and operational personnel. It includes the
following:
i. Performance
The system must be interactive and the delays involved must be less .So in every action-
response of the system, there are no immediate delays.
ii. Security: all passwords that are generated or accepted must be stored in database in an
encrypted form
iii. Usability: the system will have the good user interface be user friendly and consistent
and shall provide attractive graphical interface for the user which more interactive forms
and menus that make the system usable to system users.
iv. Reliability: The system will operate 24 hours a day, 7days a week, while ensuring that
information is delivered on time as required.
v. Accessibility: Users can access their results from any location(as long as they are within
a network service reception area)

18. 11
vi. Availability
If the internet service is not available other preferable ways can be used to accomplish the
task. Example an inventory system does not require internet.

19. 12
4.2 Use case diagram
Figure 4.1 use case diagram

20. 13
4.3 System Requirements
4.3.1 Software requirements
 Operating System (windows or mac OS)
 Android SDK
 Integrated Development Environment(IDE)-Android Studio or Eclipse
4.3.2 Hardware requirements
 Processor – i5 or i7
 Hard Disk – 500 GB
 Memory – 4GB RAM

21. 14
CHAPTER 5: DESIGN
5.1 Logical design (basic/General Design)

22. 15

23. 16
5.2 Conceptual design (Detailed Design)
Entity Relationship diagram for android bus pass and ticketing system
Passenger/
user
Select
Bus
Travel throughBuys
M 1
name phone
password email
address
Seat_available
bus_name departure
location
departure
time
departure
date
departure
location
Arrival time
seat_No
route_Idticket_type
M
1
M
1
seat_No
id_No

24. 17
5.3 Interface (I/F) Design