BUS TICKET BOOKING AND MANAGEMENT SYSTEM

PROPOSAL

THESIS SUBMITTED IN PARTIAL FULFILMENT OF THE

REQUIREMENT FOR DIPLOMA IN IT

BY

DBIT-01-8448/2020

IAN KIVUVA MUMO

TO

THE DEPARTMENT OF INFORMATION TECHNOLOGY

FACULTY OF SCIENCE AND ENGINEERING

ZETECH UNIVERSITY

JANUARY 2022

1
 DECLARATION

This proposal is my original work and has not been presented for a diploma in any other university.

Ian Kivuva Mumo

………………………………… ……………………………..

Signature Date

This proposal has been submitted for examination with my approval as the unit lecturer.

Francis Mutuku

…………………………………. ………………………………

Signature Date

Zetech University, Nairobi, Kenya

2
 DEDICATION

I hereby dedicate this research project to my esteemed lecturers, university staff and my beloved mum and all
my friends for their highly appreciated contribution in achievement of my Diploma.

3
 ACKNOWLEDGEMENT

Firstly, I would like to thank the almighty God for His protection during the entire work. I also acknowledge the
entire school and my supervisor for his guide during the project.

I express my sincere gratitude to the university HOD MR Daniael Njeru for providing an opportunity to work on
a real time project.

I would also thank my parents for their continous support that plays an important role in the completion of this
project.

Appreciation is extended to those individuals who contributed their time and talent to the

development of Basics of BUS TICKET BOOKING AND MANAGEMENT SYSTEM.

4
TABLE OF CONTENTS

DECLARATION--------------------------------------------------------------------------------------------------------------- i

ACKNOWLEDGEMENT--------------------------------------------------------------------------------------------------- ii

DEFINITION OF KEY TERMS------------------------------------------------------------------------------------------ iii

ABBREVIATIONS AND ACRONYMS--------------------------------------------------------------------------------- iv

ABSTRACT-------------------------------------------------------------------------------------------------------------------- v

LIST OF FIGURES---------------------------------------------------------------------------------------------------------- vi

LIST OF TABLES---------------------------------------------------------------------------------------------------------- vii

CHAPTER ONE: RESEARCH INTRODUCTION--------------------------------------------------------------------1

1.1 Executive Summary----------------------------------------------------------------------------------------------- 1

1.2 Research Objectives---------------------------------------------------------------------------------------------- 1

1.2.1 General Objective------------------------------------------------------------------------------------------- 1

1.2.2 Specific Objectives------------------------------------------------------------------------------------------ 1

1.3 Background Information---------------------------------------------------------------------------------------- 1

1.4 Study Justification------------------------------------------------------------------------------------------------ 1

1.5 Study Limitation--------------------------------------------------------------------------------------------------- 1

1.6 Problem Scope----------------------------------------------------------------------------------------------------- 1

CHAPTER TWO: LITERATURE REVIEW--------------------------------------------------------------------------- 2

2.1 Introduction------------------------------------------------------------------------------------------------------------- 2

2.2 Global Review---------------------------------------------------------------------------------------------------------- 2

2.3 Regional Review-------------------------------------------------------------------------------------------------------- 2

2.4 Local Review------------------------------------------------------------------------------------------------------------ 2

5
CHAPTER THREE: SYSTEM METHODOLOGY AND DATA COLLECTION------------------------------3

3.1 Introduction------------------------------------------------------------------------------------------------------------- 3

3.2 System Requirements Specification-------------------------------------------------------------------------------- 3

3.2.1 Functional Requirements--------------------------------------------------------------------------------------- 3

3.2.2 Non Functional Requirements--------------------------------------------------------------------------------- 3

3.3. Design------------------------------------------------------------------------------------------------------------------- 3

3.3.1 Low Level Design------------------------------------------------------------------------------------------------- 3

3.3.2 High Level Design------------------------------------------------------------------------------------------------ 3

3.4 Implementation / Development------------------------------------------------------------------------------------- 3

3.4.1 Language(s), Frameworks and Other Technical Requirements-----------------------------------------3

3.4.2 Code Review Strategy------------------------------------------------------------------------------------------- 3

3.5 Testing------------------------------------------------------------------------------------------------------------------- 4

3.5.1 Functional Requirements Testing----------------------------------------------------------------------------- 4

3.5.2 Non-Functional Requirements Testing-----------------------------------------------------------------------4

3.6 Deployment------------------------------------------------------------------------------------------------------------- 4

CHAPTER FOUR: CONCLUSION AND RECOMMENDATIONS-----------------------------------------------5

4.1 CONCLUSION--------------------------------------------------------------------------------------------------------- 5

4.2 RECOMMENDATIONS--------------------------------------------------------------------------------------------- 5

CHAPTER FIVE: REFERENCES AND APPENDICES-------------------------------------------------------------6

5.1 REFERENCES--------------------------------------------------------------------------------------------------------- 6

5.2 APPENDIX I:---------------------------------------------------------------------------------------------------------- 6

5.3 APPENDIX II:--------------------------------------------------------------------------------------------------------- 6

5.4 APPENDIX III: GANTT CHART--------------------------------------------------------------------------------- 6

6
CHAPTER ONE

INTRODUCTION.

1.1 Objectives of study

General Objective

The main purpose of this study is to automate the manual procedures of securing a bus ticket by the
passengers to make the process easier s and faster. Generally, listed below are the objectives of the study;

Specific Objectives

 Providing a web based bus ticket booking system where a customer will be able to check the bus
schedule, book a seat, and choose his preferred travel time without necessarily making queues at any
booking areas.
 Enabling customers to check the types and availability of buses online.
 Easing the payment procedures by obtaining a pin after payment is done to the designated banks/phone
payments.
 Enable customers cancel their booked reservation whenever they cancel or defer their journey.

7
1.2 Background information

Commuting by buses is the most common means of transport in the world today especially in the developing
countries. For this reason, bus companies and the customers in transport industry are demanding more kinds of
booking systems to support management and their operations.

Online ticket booking gives the customers an opportunity to choose their preferred vehicles and book tickets
according to their travel schedules from the comfort of their homes. This will be a bold step to improve and ease
customer service since they are forced to make long queues on the counter to secure themselves a ticket.

Therefore, the transport company at large will appreciate a system which can automate its operation in the
area of bus ticket booking in order to meet customers’ demands at all times. Currently, staff at the counters are
selling tickets manually to customers because they have no any online system to perform that task.

However, online bus ticket booking system enables the customer to buy bus ticket, make payment and ask
for information online easily. All this can be achieved by creating a website that will carry the booking system.

1.3 Problem statement

Currently, the type of system being is a manually-operated system for selling bus travel tickets to
customers. The main issue to be addressed in this proposal is that travelers have to make long queues to reach
the service counters in order to secure themselves a travelling ticket.

8
 1.4 Justification of study

The proposed research will investigate on building an online bus ticket booking system that will help the
transport industry in minimizing the counter manual work done by the staff in selling tickets and also make it
easy for customers to secure themselves tickets from anywhere and schedule their travel dates. Also, the system
will allow the transport system to have a centralized platform where all bookings, payments and any other
related information can be managed from, as opposed to the current manual system. Honesty and legitimacy will
be highly evident in the system since each customer will be required to create their own personalized accounts
where them only can access their data and have it secured with passwords or personal identification numbers.

Additionally, the proposed system will be able to show the bus varieties available for use by customers, their
departure and estimated arrival time, name of the driver of each specific bus and the routes they ply. Through
the proposed system, the company managers will also be able to monitor how the business is running and rectify
where there is need and improve where necessary.

1.5 Study Limitation

Due to the Long queues and overcrowding of the Bus booking entrances by clients who come to purchase tickets
for booking .Therefore the researcher will come up with a system that will enable ticket booking easy.

1.6 Problem scope

The proposed system will be implemented and tested in one of the bus transport companies to attest its
effectiveness and efficiency. For any database, we’ll use the MySQl database framework and PHP since it’s the
most efficient software as far as storing data is concerned.

9
 CHAPTER TWO: LITERATURE REVIEW

2.1 Introduction

This chapter contains global, regional and local literature review, and a summary of literature.

2.2 Global literature review

Ascendix January 4, 2022 states that “A bus ticket booking system is a web or mobile software solution that
brings high automation and personalized user experience to simplify the ticket booking and purchasing process
for customers”. The project, on the bus transport side, serves as a marketing strategy and aids in an efficient
processing and delivery of appropriate tickets.

Based on Pedone (2001), wide spread use of the internet has led to the emergence of variety of electronic
services. Electronic ticket or E-ticket is an example of such a class of e-service-tickets give evidence to their
holders to have permission enter a place of entertainment, use a means of transportation, or have access to some
Internet services. E-tickets give evidence to their holders to have permission to enter a place of entertainment,
use means of transportation or have access to some internet services

10
2.4 Local Review and Regional Review

Users can get the tickets by purchasing them from a web server or simply receiving from a

vendor or from another user who previously acquired them. E-tickets can be stored in a desktop

computer or personal digital assistants for future use. For some cases, like e-tickets non transferable example e-
ticket airline, it has to be validated to prevent duplication and ensure authenticity and integrity.

The validation process is called e-ticket problem. Here results in the server either accept or reject the e-ticket
and intended to prevent duplication which avoids multiple use of an e-ticket by the same or different users,
ensuring authenticity and integrity that e-tickets are only accepted if theyhave been issued by an authorized
source and have not been tampered with. In addition to privacy, it is desirable that e-tickets should not contain
any information associated with their holders.

The validation process is called e-ticket problem here, results in the server either accepts or rejects the e-ticket,
and intended to prevent duplication which avoids multiple use of an e-ticket by the same or different users;
ensuring authenticity and integrity that e-tickets are only accepted.

According to Pedone (2001), e-ticket validation problem in context in which users can’t be trusted and servers
may fail by crashing. Besides that, two specification of the ticket problems are the at most once and the at least
once e tickets problems. Both specifications may result in some e-tickets never being accepted or accepted
multiple times in execution with failures.

There were a few protocols that can be used to solve the e-ticket problem, which are quorum based e-ticket
protocol, Simple e-ticket protocol and the optimistic e-ticket protocol can be used to solve the at most once e-
ticket problem.

2.3

Electronic Payment Systems

According to Charalampos (2004) National and Kapodistrian University of Athens Electronic Payment Systems
and Marketing: Electronic payment systems can be considered to be merely the next—albeit significant—step in
a long line of changes in payment clearing systems. The electronic settling of accounts, for example, has long
been an integral part of payment systems using credit cards, debit cards, automatic teller machines, and prepaid
cards. What enables any payment mechanism to be processed electronically is the fact that unlike currency,
bills, or coins which carry monetary values, non-cash mechanisms are promises or contracts of payments.

11
 Case Study on Computer ticket

This is an existing OTBS for different entertainment categories such as sports, festivals styles music and travel.
Someone can book, even if he or she is not a member by clicking on the menu bar and choose the category of
entertainment he or she is interested in booking. After selecting the category, there is need of choosing the date
schedule of the event and the venue which is followed by the event schedule with ticket price, venue, date and
time and the number of tickets the clients wish to book.

Advantages of Online Ticket Booking

One of the major benefits that e ticketing will offer is that it does not require a paper ticket/record as a
confirmation of your booking. The confirmation of your booking deception in the organizer computerized
ticketing system in an electronic format. You need not to carry a paper ticket while travelling and hence there is
no fear of losing the ticket or forgetting it behind since they exist in electronic format. Helps minimize transport
costs by just logging on the net and performing all the necessary transactions and security together with
providing flexibility and convenience.

This type of making reservations reduces the risk of you losing your paper tickets since print outs of your e-
tickets can be taken anytime and anywhere. No queue for buying events tickets and customers can access more
information and find other deals online.

.Disadvantages of Online Ticket Booking

A computer crash could cause client reservation and other information to simply vanish. Most networks have
backup systems in place to prevent such an occurrence, and customer’s printouts of e-ticket documents can
guard against this, but it remains a possibility and has happened in the past.

Users need internet and Computer experience in order to access information.

Users need a credit card or some other format of payment in order to make their payments. If the website is
down you won’t be able to book online

12
Solutions

These new technologies should be used to more efficiently determine optimal offer prices, determine what price
to offer, buyers can now readily locate products at desire prices or consult market benchmarks Computers and
Internet are changing commerce because goods and services that are sold in stores, through mail order, or via the
telephone are today also bought and sold through various forms of e-commerce. EBay, uBid and Bid.com
represent one of the most successful categories of commerce is the Internet-based auction site.

13
 CHAPTER THREE : SYSTEM METHODOLOGY AND DATA COLLECTION

3.1 Introduction

The system of collecting data for research project is known as research methodology. The data may be
collected for either theoretical or practical research. For instance, for any project to be completed, it has to go
through stages called System Development Life cycle (SDLC) to study how a system can support business
needs, design the system, build it and deliver it to users. Information which was used for this study was carried
out by oral interview.

Requirements analysis

3.1.1 Interviews

This involved interviewing bus booking officials and other relevant persons in different divisions on information
concerning tickets. Through the interview, the researchers gave a chance to other respondents to ask all relevant
questions concerning the topic of the study. This gave the researchers an advantage of getting first hand
information from the respondents.

3.1.2 Review of existing documentation

Document review was used to understand the current system and get relevant literature of the ticket management
techniques that are being used. A number of documents were reviewed ranging from invoices, payment receipts,
and the printed tickets counter books.

3.1.3 Observation technique

Observation technique helped the researcher to physically observe the processes involved in booking of tickets
and the characteristics of these processes for example the speed of information flow and the number of
personnel involved.

14
3.1.4 Use of Questionnaire

In the questionnaire respondents read the questions, interpret what was expected and wrote down the answers. In
the case of questionnaires, there was no one to explain the meaning of the questions to respondents. This helped
the researcher in collecting information from a larger sample and offered greater anonymity.

3.2 System Requirements Specification

User Requirements

A number of staff members from the ticket stores of some ofthe distributors were approached by

the researcher during the system study and were asked how and what they would need the system

to be and the following were the findings:

The system should be easy to learn and adopt.

The system should be fast in producing results thus reducing processing time and increasing user

productivity.

The system should improve efficiency of information storage and retrieval. The system should allow users take
a few steps to get done with any task. The system should have an element of consistency especially the
interface.

The system should have an element of error validation. That is, a system that would detect a user entering
unusual commands or data format that is inconsistent with the database. The system should provide attractive
interfaces with easy navigation throughout the system.

15
3.2.1 Functional Requirements

These are requirements necessary for the system to function efficiently and effectively and they

include the following; The system should enable customers to register as members before they book. The online
Ticket booking System should also enable customers to view ticket availability, ticket cost, events schedules and
after booking successfully, an email can be sent to them.

The system should show venue, the start and end times of events, and ticket number. The system should allow
the administrator to upload new information so that the member can

check the availability of events.

The system should also allow the agent to view tickets booked by a member.

The system should be able to store the records for all members who have booked tickets

3.2.2 Non Functional Requirements

These are requirements that do not affect the functionality of the system. The system should allow user access
restrictions through a username and password.The system should be fast enough to satisfy the user.

User interface should be as simple and intuitive as possible. User interfaces should provide data validation
against user input.

Security Requirements

Before members can book a ticket, they have to create an account with the system with a unique username. Until
then they can only access limited sections of the system such as viewing available events.

The system particularly does not accept blank fields or non valid input. The system has a unique login section
for the admin who can view and carry out a series of activities. Users can logout at any time they fill like since
there are provisions for such on any authorized page.

16
System specifications

Software :

Operating system for the client PCs,

Database management system

Minimum system requirement :

Windows XP and later versions, Vista/Linux or any server windows and server 2005.

MySQL Server,

Hardware :

Processor

Processor speed

Hard drive

Minimum system requirement:

Intel Pentium 11 or above

800 MHZ or above Memory 128 MB

RAM or above depending on the Operating system.

10GB or above

17
3.3. Design
3.3.1 Low Level Design

Conceptual Design

Conceptual design is the first phase of a design where drawings are the primary factor focus. A

good conceptual design comprised of the creation of an idea, the exploration of the intentions of

an idea and the representation of an idea in form of a plan.

Logical design

There was need of coming up with a logical data model which contained all the needed logical

and physical design choices and physical storage parameters needed to generate a design in a

Data Definition Language, which was then used to create a database.

Logical design pertains to an abstract representation of the data flows, inputs and outputs of the

system. This was often conducted via modeling, which involved a simplistic and sometimes

graphical representation of an actual system. In the context of systems design, modeling could

undertake the following forms, including:

 a) Entity Relationship Diagrams

 b) Data flow diagrams

 a) Entity Relationship Diagrams

The E-R Diagram was used in data modeling to set up an entity relational model of the system.

This involved determining the relationships between the various entities in the system and

associating these entities with their attributes and attribute domains.

18
b) Data Flow Diagram

The Data Flow Diagram (DFD) was used to model the processes involved in the system to show

how data flows into and out of the system in a top-down manner by giving a graphical

representation of a system’s components, processes and how they will interface with each other.

3.3 Physical design

Physical design was the actual input and output processes of the system. This was laid down in

terms of how data is input into a system, how it is verified! authenticated, how it is processed,

and how it is displayed as output. Physical design, in this context, does not refer to the tangible

physical design of an information system.

3.4 System Implementation

a. A scripting language (PHP in particular) embedded in HTML was used to develop graphical

user interfaces (GUI5) that the users would interact with while logically interacting with

the server.

b. MySQL database management system was used to store, manipulate, retrieve data, querying

to generate reports like summaries on tickets being booked.

c. Apache WampServer was processing the user’s requests and sending information through the

web browser

19
3.3.2 High Level Design
Context Diagram

20
Data flow diagram

21
3.4 Implementation / Development
The proposal submitted in this study implement a bus ticket booking and management system.

3.5 Testing
Testing was carried out based on the relevant review of the system to find bugs such as incorrect

functions, ensure that it is complete and accurate which was followed by full system testing to

ensure that all units function effectively as a single system.

Validation was carried out by taking the system to the users to check whether it meets their

requirement

3.5.1 Functional Requirements Testing

3.5.2 Non-Functional Requirements Testing

Are qualities of the solution.they consist of the solution limitations or the implemtations constraints and external
factors such as system availability.

22
3.6 Deployment

The system map

The system map shows how users of the system logs in and the various activities they undertake

as shown below in figure

Update’s events

Administrator Update’s venues

Add agents

View tickets

User login Agent Confirms

Add events and venue

Member Order’s tickets

23
Home page

24
 Registered

25
26
27
CHAPTER FOUR : CONCLUSION AND RECOMMENDATIONS

4.1 CONCLUSION

The researcher was able to achieve the project’s intended objectives as follows:

The users of the system are able to book tickets and retrieve stored information about tickets

The system is also customizable for the Online bus booking revenue management needs

4.2 RECOMMENDATIONS
We recommend that in the future if other researchers have interest in Online bus booking Ticket
Management this project should be a starting point. Future work may consider all other sources of ticket
booking .

Training of booking staff on the use and functionality ofthe system should also be carried out.

We also recommend that many people use the system and enjoy the benefits associated with it.

In future, additional fünctionalities should be made on the system to cater for improvements in

using the OBBS(Online Bus Booking System).

28
CHAPTER FIVE: REFERENCES
5.1 REFERENCES

l. Michael K. Glass, Yann Le Scouarnec, Elizabettt Naramorc, Gary Mailer, Jeremy

Stola Jason Gerner. (2004). Beginning PHP, Apaclu, I{ySQL Web D*elopwnt

(Retrieved on: 2l SePtemb€r 201 l)

2. WikiPedia the free encYcloPedia

http://en.wikipedia.ore/wiki/Web-application (Accessod on:19 Oootober 201l)

3. Maraliner WebPage

http ://www.maral iner.com.my/Main/Main.asp?paeelD:002 (Accessed on: l9

Ocotober 201l)

4. Transnasioal WebPage

http://www.transnasional.com.my/destination.php (Accessed qr:14 OcCobcr 201l)

5. Wikipodia on Electnonic Tickeing

http://en.wikipedia.org/wiki/Electronic-ticket (Accessed on: l6 Ocdobcr 20ll)

6. Online web tutorial

http://en.wikipedia.ore/wiki/Electronic ticket (Acccssod on: l0 Februry 2012,

7- Plusliner WebPage

http ://www.ticket4u. com.m y/pl usl i ner/ (Accessed on: I Jmuary 2Ol2\

35

29
30
31