DEDAN KIMATHI UNIVERSITY OF TECHNOLOGY FINAL YEAR PROJECT

DOCUMENTATION FOR FINAL YEAR OF STUDY IN BACHELOR OF

SCIENCE IN BUSINESS INFORMATION TECHNOLOGY

KIPTOO BARNOH RORIO

PROJECT TITLE:

DEKUT ONLINE BUS TICKET BOOKING SYSTEM.

A PROJECT SUBMITTED TO THE DEPARTMENT OF INFORMATION

TECHNOLOGY IN THE SCHOOL OF COMPUTER SCIENCE AND INFORMATION
TECHNOLOGY IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE
AWARD OF THE DEGREE OF BUSINESS INFORMATION TECHNOLOGY IN
DEDAN KIMATHI UNIVERSITY

2019

i
 DECLARATION
This is to certify that Dedan Kimathi online bus ticket booking system is my original work done
as a partial fulfillment of the requirement for the award of Bachelor’s Degree in Business
Information Technology of the Dedan Kimathi University of Technology. This project has not
been presented to any other institution for any award of Degree or Diploma.

Prepared by: Kiptoo Barnoh Rorio

Signature: ……………………… Date: ………………………

This research project has been submitted with my approval as the University supervisor. Mr.
Harry Opiyo, Dedan Kimathi University of Technology

Signature: ……………………… Date: ……………………

ii
 ACKNOWLEDGEMENT
I would first wish to acknowledge the Almighty God for a continued guidance through the whole process
from idea generation to actual implementation of the project.

Secondly, I would like to acknowledge my supervisor, Mr. Harry Opiyo for his counsel and continued
support throughout all steps of system development.

Finally, I wish to acknowledge my great friends and family for their prayers encouragement and
emotional support throughout the journey of system development.

iii
 ABSTRACT
This project addresses the study and development of an online Bus Ticketing system to enable
users, both the bus operators and the customers to make an online bus ticket sale/ purchase and
act as an operation tool for bus operators to operate their organizations effectively. Traditionally,
bus ticket purchase has been over the counter in bus terminals, however, today it has evolved
with rapid expansion of e-commerce. This system has focused on online bus ticket booking and
online bus ticket payment for customers, which saves much time and energy to complete the
process the traditional way. The objective of the project is to enable customers to check available
buses with their destinations and departure times, book a ticket for himself/herself with two more
students, make online payment and thereafter receive an e-ticket and a short messages service
notification.
The method of development used, Waterfall development method which ensures development of
a system within a shortest time possible and also tied up to user requirements throughout the
development process.

iv
 Table of contents
DECLARATION ......................................................................................................................................... ii
ACKNOWLEDGEMENT ............................................................................................................................ iii
ABSTRACT .............................................................................................................................................. iv
List of figures ............................................................................................. Error! Bookmark not defined.
CHAPTER ONE: INTRODUCTION ...................................................................................................... 1
1.1 Background of the study. .......................................................................................................... 1
1.2 Problem statement ......................................................................................................................... 3
1.3 Objectives ...................................................................................................................................... 3
1.3.1 General Objective ................................................................................................................... 3
1.3.2 Specific Objectives ................................................................................................................. 3
1.4 Research Questions ........................................................................................................................ 4
1.5 Justifications .................................................................................................................................. 4
1.6 Scope............................................................................................................................................. 4
1.7 Limitations .................................................................................................................................... 5
CHAPTER TWO: LITERATURE REVIEW ........................................................................................... 6
2.1 Introduction ................................................................................................................................... 6
2.1.1 Ticketing................................................................................................................................. 6
2.1.2 Analysis on exiting manual system .......................................................................................... 6
2.1.3 Payment .................................................................................................................................. 6
2.2 Case Studies .................................................................................................................................. 6
2.2.1 Case Study one: BUUPASS ................................................................................................... 6
2.2.2 Case Study two: BUS KENYA................................................................................................ 7
2.2.3 Case Study three: MADARAKA EXPRESS ............................................................................ 7
2.2.4 Case Study 4: BUSCAR ONLINE BOOKING ........................................................................ 7
CHAPTER THREE: RESEARCH METHODOLOGY ............................................................................ 8
3.1 Introduction ................................................................................................................................... 8
3.2Software Development Model ......................................................................................................... 8
3.3 Suitability of the Model ................................................................................................................. 8
3.4 Fact finding techniques ................................................................................................................ 10
3.4.1 Interviews ............................................................................................................................. 10
3.4.2 Observation........................................................................................................................... 10
3.4.2 Questionnaire ........................................................................................................................ 11

v
 3.5 Preliminary Data Processing and Analysis ................................................................................... 11
3.6 Resources .................................................................................................................................... 11
3.6.1 Hardware resources ................................................................................................................... 11
3.6.2 Software resources .................................................................................................................... 11
CHAPTER FOUR: SYSTEM DESIGN AND ANALYSIS ................................................................... 12
4.1. Introduction ................................................................................................................................ 12
4.2. Requirements analysis................................................................................................................. 12
4.2.1 Functional requirements ........................................................................................................ 12
4.2.2 Nonfunctional requirements .................................................................................................. 12
4.3. Data Analysis ............................................................................................................................. 13
4.3.1 Questionnaire analysis ........................................................................................................... 13
4.3.2. Observation .......................................................................................................................... 18
4.3.3 Interview ............................................................................................................................... 18
4.4 System Analysis .......................................................................................................................... 18
4.4.1 Use case analysis................................................................................................................... 19
4.4.2 Entity Relation Diagram......................................................................................................... 20
4.4.3 class diagram ........................................................................................................................ 21
4.4.4 Flowchart .............................................................................................................................. 21
4.4.5 Sequence diagram ................................................................................................................. 23
CHAPTER FIVE: SYSTEM TESTING ................................................................................................. 24
5.1 Introduction ................................................................................................................................. 24
5.2 Types of testing ........................................................................................................................... 24
5.2.3. Unit testing .......................................................................................................................... 25
5.2.4 Integration testing ................................................................................................................. 26
5.2.5 System testing ....................................................................................................................... 26
5.2.6 Acceptance testing ................................................................................................................ 27
5.3. Functional Testing and Results Samples ...................................................................................... 28
5.3.1. Login module for the android app ......................................................................................... 28
5.3.2. On the dashboard page ......................................................................................................... 30
5.3.3. Booking page ....................................................................................................................... 31
5.3.4. Payment page ....................................................................................................................... 32
5.3.5 The m pesa prompt ................................................................................................................ 33
5.3.4 The e-ticket after payment ..................................................................................................... 34

vi
 5.4. Web App .................................................................................................................................... 34
5.4.1. Login module for the web app ............................................................................................. 34
5.4.2 On the dashboard page .......................................................................................................... 35
5.4.3. Adding students page ........................................................................................................... 36
5.4.4. Adding buses page ............................................................................................................... 37
5.4.5. scheduling trips page ............................................................................................................ 38
5.4.6. Track of students who have booked tickets ........................................................................... 38
5.4.7 track of all payments ............................................................................................................. 39
CHAPTER 6: IMPLEMENTATION AND DEPLOYMENT ................................................................. 40
6.1 Implementation Strategy .................................................................................................................. 40
6.1.1 Introduction .......................................................................................................................... 40
6.1.2 System Specification Front end development......................................................................... 40
6.2: Deployment ................................................................................................................................ 40
6.3 Support and Training ................................................................................................................... 41
CHAPTER 7: CONCLUSION AND RECOMMED ATIONS ............................................................... 42
7.1. Discussion .................................................................................................................................. 42
7.2. Recommendations ....................................................................................................................... 42
7.3. Limitations ................................................................................................................................. 42
7.4. Conclusion .................................................................................................................................. 43
REFERENCES...................................................................................................................................... 44
APPENDICES ...................................................................................................................................... 45
Appendix I Time schedule ................................................................................................................. 45
Appendix II Budget ........................................................................................................................... 46
Appendix III Questionnaire................................................................................................................ 47

vii
 List of figures
Figure 3 1: Waterfall development model, the figure describes the waterfall development process in
each step ................................................................................................................................................. 9
Figure 4 1: Chart illustrates the number of students who have booked school bus transport verse those
who have not used. 13
Figure 4 2: Presents the feedback of the students on the school bus transport department services. .... 14
Figure 4 3: Describes the percentage at which students keep their tickets that is if ever lost bus ticket or
not. ....................................................................................................................................................... 15
Figure 4 4: Describes the frequency at which students use the school bus transport services. ............... 16
Figure 4 5: illustrates the availability of different patients to internet .................................................... 17
Figure 4 6: illustrates the availability of different patients to internet. ................................................... 19
Figure 4 7: database schema describing the layout of the database and how different entities are
structured . ........................................................................................................................................... 20
Figure 4 8: Class diagram: describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.4.4.4 Flowchart ................... 21
Figure 4 9: System flow diagrams describing the process flow and data in the system ........................... 22
Figure 4 10: Sequence Diagram ............................................................................................................. 23
Figure 5. 1: shows a login page of the mobile app 28
Figure 5. 2: shows the login error upon wrong credential provision ....................................................... 29
Figure 5. 3: The mobile app dashboard .................................................................................................. 30
Figure 5. 4: booking page....................................................................................................................... 31
Figure 5. 5: payment page ..................................................................................................................... 32
Figure 5. 6: m-pesa prompt ................................................................................................................... 33
Figure 5. 7: e-ticket ................................................................................................................................ 34
Figure 5. 8: shows a login page .............................................................................................................. 35
Figure 5. 9: shows the login error upon wrong credential provision ....................................................... 35
Figure 5. 10: shows the dashboard page ................................................................................................ 36
Figure 5. 11: The page showing where students are added to the system .............................................. 36
Figure 5. 12: The page for adding buses ................................................................................................. 37
Figure 5. 13: The page for scheduling trips ............................................................................................. 38
Figure 5. 14: The page where admin can keep track of all students who have booked the bus tickets .... 38
Figure 5. 15: The page that shows all the amount paid by students ....................................................... 39
Figure 1 Gantt chart: the Gantt chart describes various steps and the time they all consumed during the
whole process of developing the system 45
Figure 2 Budget: indicates the total amount of money used for the for setting up and running the project
.............................................................................................................................................................. 46
Figure 3 Questionnaire: showing the set of questions used to collect data from the various parts I carried
out the interview. .................................................................................................................................. 47

viii
 List of tables
Table 5 1: Unit testing on login and registration module ........................................................................ 25
Table 5 2: Integration module showing how functions are integrated to function together ................... 26
Table 5 3: System testing ....................................................................................................................... 26
Table 5 4: Acceptance testing ............................................................................................................... 27

ix
 CHAPTER ONE: INTRODUCTION

Android-based applications have simplified the lives of many groups of people in terms of
service delivery to different group of people, therefore saving much valuable time. This platform
makes it easy for people to carry their transactions more conveniently in whatever place they are.
These applications are widely used to assist us in overcoming problems of transport with long
queues, ticket booking and payment. In past these operations were done manually and because of
this people had to walk to the bus office to book tickets and make payments, because of these
there were many people in the queues, you cannot get proper departure and arrival timing and
because of many people you need to book tickets in advance which was not possible. To make
there processes easy and convenient to users, an application will be developed therefore
problems are solved.
This document is written purposely in line with means development process of an online ticket
booking system for students’ projects, where all processes of bus ticket purchase and payments
are done online and verified.
1.1 Background of the study.
Transport or transportation is the movement of humans, animals and goods from one location to
another. In other words, the action of transport is defined as a particular movement of an
organism or thing from a point A to a point B. Modes of transport include air, land, water, cable,
pipeline and space (Transport - wikipedia, n.d.). Effective transport is vital for the economy.
Good transport connections have direct benefits to people, businesses, the environment, and the
economy overall. They can support innovation, help people access jobs, shape greener and
healthier places, and attract new firms. The prevalent view in various global circles is that man is
presently living in an
age growth of information gathering, processing and dissemination, popularly called the
information age. For this reason, managers and other users of information especially in transport
industries are demanding more kinds of information to support management and operations.
They must therefore respond to the increasing requirement for information and data management

The distance bus ticket booking has been one of the major concerns in the National Transport
Commission (NTC) and other transports commissions in new world. There is a growing demand
and trend in moving to online bus ticket booking systems. User’s (passenger) self-interaction in

1
ticket booking has been changing in a positive way with the introduction of these systems. With
the evolution of these new coming systems it will cause the traditional bus ticket booking space
to be changed.

At present the current bus transportation system use both manual tickets and digital ticketing
machine that printed tickets. Digital ticketing machine commonly practice in highway bus
transport service. These novel digital machines have the ability to store and process data and thus
provide the conductor with a number of significant statistics at the end of the day. For
illustration, the quantity of tickets delivered and the amount of money collected for each trip.
Beside the fact of the technique of give out tickets to commuters, the transaction is done
innocently in cash. As usually existing process easy to issues fake ticket and some cases balance
bus fare amount not return to commuters.
However, the Online Bus Booking System is an android based application that agree to
passengers to check bus ticket availability and buy bus ticket through the online payment
Electronic tickets, or e-tickets, gives evidence that their holders have the permission to enter a
place of entertainment, use a means of transportation, or have access to some Internet services.
The design of this online system will be beneficial to the Dedan Kimathi University of
Technology because it has not existed before. Dedan Kimathi university school bus transport
service owned by school whose primary purpose is to provide transport services to students who
stays far from school premises. The school will definitely appreciate a system which can
automate its manual operations in the area of bus ticket booking in order to meet students
increasing demand. Currently, staff at the bus ticket counter is using an internal system to sell
tickets at the counter and customers who are unable to buy bus ticket online at this moment
would have to queue up a long queue to buy bus ticket and ask for information and this brings a
lot of inconveniences to students.

would have to go to the counter to a buy bus ticket. Sometimes, customers’ needs
However, Online Bus Ticket Booking System enables the students to buy bus
ticket, make payment, and ask for information online easily.

Dedan Kimathi university transport department provides bus transport to students who reside at
Nyeri town, King’ong’o, Kamakwa and Embassy. Currently the system used is manual that is

2
students buy tickets in order to receive bus transport offered by school buses. Students are
required to deposit cash in banks or have an overpay in their fees to pick bus tickets from finance
department. Those students who are unable to access the tickets from finance can buy from
individuals with tickets in bulk.

The current system used has some inconveniences which are; non-students can use the bus
transport without being noticed since the only requirement for using the transport is a bus ticket,
students have to go to the bus park to check the availability of seats and this limits students who
have late classes or may not be around the bus park, the transport department do not know the
exact number of students who use the transport sine the bus leaves after it is full therefore other
students are not able to access the service.(Nwakanma, Etus, Ajere, & Agomuo, 2015)

1.2 Problem statement

Currently the process being used by the school transport department is manual. The challenges
with this current system is that it poses insecurity to students as the only requirement for using
the transport is the bus tickets, students have to physically walk to bus park to check seats
availability, transport department cannot know the exact number of students using the transport
and it causes inconveniences as one has to pick tickets from the school finance or buy from
students with more tickets after depositing cash in school bank accounts. Students are also
required to have tickets in bulk to cater for to and from to avoid looking for tickets daily.

1.3 Objectives

1.3.1 General Objective

To develop both an android application and web application that student can use to book tickets
and make online payments.

1.3.2 Specific Objectives

i. To analyze the current system used by universities and colleges to provide for transport
for their students.
ii. To design, develop and implement a web and mobile application that enables students to
book buses and make payments online and also the school transport department in
managing the transport activities.

3
 iii. To test the applicability and the efficiency of the bus booking system in enabling students
to book buses and make payments online.

1.4 Research Questions

i. What is the current system used by the university to transport students?

ii. How can a system to automate bus ticketing be designed, developed and implemented?
iii. Does the system work efficiently?

1.5 Justifications

Currently students who have paid for the tickets pick tickets in bulk to cater for couple of days or
more. Those who cannot access them at the finance department go around looking for students
with more tickets to sale them a few.

The system will be appropriate for solving the problems faced by the students and the transport
department. The students book the ticket using the application and the transport department keep
track of all transactions done.

The application will be appropriate as students can easily and conveniently book the ticket at any
place in school without need to go to check on the bus park. The application will also help in
ensuring security to students using the application, as there are cases of insecurity threats in
Kenya. It will also help the Transport department in scheduling the trips and time. There will be
no more buying of tickets in bulk and buying tickets from colleagues in case one cannot get from
the finance department.

1.6 Scope
The application is meant to serve students who want to use the school bus transport. These are
mostly students who reside far from school in residential in Nyeri town, King’ong’o, Embassy,
Kamakwa and Nyaribo. It will be easily accessible since most of students have phones and are
able to access internet. The application will also be used by the school transport department to
make schedules of travels and keep track of the transactions taking place. It will also help the
transport department to make estimates of the students using the transport.

4
1.7 Limitations
Every student must have an android phone.

Data connectivity is required.

5
 CHAPTER TWO: LITERATURE REVIEW
2.1 Introduction

The main purpose of this chapter is to review the development of online bus ticketing system in
Dedan Kimathi University. This chapter will look into issues concerning the development of
online bus ticketing system in school.(ONLINE BUS TICKETING SYSTEM, 2007)

2.1.1 Ticketing
According to Oxford dictionary, a ticket id defined as “a piece of paper or card giving the holder
a right to admission to a place or event or to travel on public transport.” (Oxford English
Dictionary, 2005). Generally, a bus ticket consists of all activities involved in producing tickets
which includes producing tickets, booking tickets and selling tickets, total tickets produced for a
trip, tickets sold and income earned through sale of tickets. There are two types of ticketing
system that is manual system and computerized system.

2.1.2 Analysis on exiting manual system

Ticketing in Dedan Kimathi university of Technology is conducted manually. Students who have
paid the transport fee picks the tickets from the school finance and gives it to the conductor
before the bus leaves. Those who cannot access the tickets from the finance office can buy from
friends with tickets in bulk and willing to sell. The bus conductor has to manually calculate the
total amount of tickets sold after receiving them from students and send the report to the
transport department

2.1.3 Payment
Online payment offers users the convenience of submitting their payments on the application.

2.2 Case Studies

2.2.1 Case Study one: BUUPASS
This system provides an online platform for customers to book tickets for various buses
including easy coach and modern coast. The user can book a seat from any place and one is able
to know when the bus will make its departure. One makes payment online over the application
thus reducing inconveniences of travelling to bus terminals to make bookings. This website
shows places where one has to go as it serves in major cities and towns in Kenya. There are

6
contact details and blog section where customers are able to interact with the bus operators.
([Link] - Online Bus Ticket Bookings, n.d.)

2.2.2 Case Study two: FlixBus

This is a mobile application developed to help bus travelers to make online bookings with
different bus companies in Europe. This system has a form where one can enter the departure
place for example Berlin, Germany and the destination for example Munich, Germany. The bus
user will then have to look for bus of his/her preference that is bus with lowest prices, shortest
routes or earliest departure. After that the bus user will add to cart and book the bus. (Bus travel
through Europe | FlixBus, n.d.)

2.2.3 Case Study three: MADARAKA EXPRESS

Kenya Railways is a State Corporation established by an Act of Parliament (Cap 397) of the
Laws of Kenya, and commenced operations on January 20, 1978.

The Mombasa-Nairobi Standard Gauge Railway is a standard-gauge railway in Kenya that

connects the large Indian Ocean city of Mombasa with Nairobi.

This is an application developed to help the users wishing to get the service of KRC at ago
provided by the Standard Gauge Railway. It helps the users to book tickets, check availability of
tickets, check the status of the tickets, station and finally how to book your tickets. This
application is compatible to all users therefore many users can easily access it. (Madaraka
Express -Travel Kenya -Online Booking, n.d.)

2.2.4 Case Study 4: BUSCAR ONLINE BOOKING

This system provides a platform for customers to make online bus booking. One searches for the
bus by selecting the routes that is where the bus is leaving and where it is heading. You
thereafter make payment using the M-pesa and the seat is reserved. The customer is able to
check on the departure time then avail himself or herself at the bus station. (BUSCAR online
ticket booking portal, n.d.)

7
 CHAPTER THREE: RESEARCH METHODOLOGY
3.1 Introduction
Refers to the process of collecting information and data and a theoretical analysis of the findings.
Therefore, the management of every project is paramount in successfully coming up with an
elaborate working system. I will use various methods and procedures in the process of initiating,
planning, executing, control and closure.

3.2Software Development Model

The software development method that I will use to guide me during the development process is
the waterfall development model. The waterfall method emphasizes that a logical progression of
steps be taken through the software development life cycle (SDLC), more like the cascading
steps down an incremental waterfall. The logical nature of the sequential process used in
waterfall method remains a common process in development.

3.3 Suitability of the Model

Waterfall model is easy to manage due to rigidity of the model. Each phase has specific
deliverables and a review process. Phases are processed and completed one at a time.

8
Figure 3 1: Waterfall development model, the figure describes the waterfall development process in each
step

The sequential phases in waterfall model are –

3.3.1 Requirement gathering and analysis – all possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification document.

3.3.2 System design - The requirement specifications from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.

3.3.3 Implementation − with inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality, which is referred to as Unit Testing.

3.3.4 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is tested for
any faults and failures.

9
3.3.5 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.

3.3.6 Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment. (SDLC-Waterfall
model, n.d.)

3.4 Fact finding techniques

Fact finding involves the discovery and establishment of the facts of an issue. In study
of system development, the researcher needs to collect facts and other relevant
information about the system to be developed. There are several techniques used to
collect the data. The following are the fact finding techniques that I used to collect the
data used in this system development.

3.4.1 Record review

In this method, the analyst seeks for information related to the system which is
published in sources like the internet, newspaper, magazines, journals, documents, etc. I
prefer this method to the others because it provides much information needed in this
study and its cheaper, since I only need to access internet within a short period to get
access to relevant materials. It is also affordable to access Dedan Kimathi University
library for some additional materials to better my study.

3.4.2 Observation

This method involves closely monitoring what is happening in the area of study. I
visited the bus park and I was able to see how the process goes on. Either each student
using the service must have a ticket from finance or buy from an individual, which is
tedious moving up and down asking for tickets to be sold. I was able to know that
provided you have a ticket you just enter the bus without any security checking.

10
 3.4.2 Questionnaire
In this method, the analyst gives out a set of printed or written questions with a choice of
answers, devised for the purposes of survey on the area of study. I prepared a set of
printed questions and present to students using the bus transport to answer them.

3.5 Preliminary Data Processing and Analysis

The objective of preliminary data analysis is to edit the data to prepare it for further analysis,
describes the key features of the data, summarize the results.

After collection of data I tabulated the findings using the bar graphs and the pie charts.

3.6 Resources
The system development process required tools to facilitate the smooth running of
procedures and activities of development.

3.6.1 Hardware resources

1.8 GHz or faster processor. Dual core or better recommended

4GB of RAM

Hard disk space up to 130 GB of available space

3.6.2 Software resources

Android Studio IDE

MySQL database

XAMPP control panel

Windows operating system

11
 CHAPTER FOUR: SYSTEM DESIGN AND ANALYSIS
4.1. Introduction
This chapter gives details on the analysis and design of the Dedan Kimathi online bus
ticket booking system. The system requirements will provide the functional and Non-
functional requirements of the system. Design of the system is carried out according
to the features and operations of the system which includes the user interface,
database schemas, code and other documentation. Designing of the system mainly
focuses on the user and ensuring the system will be user friendly and interactive.

4.2. Requirements analysis

These includes:

4.2.1 Functional requirements

a) Students can be added to the system; admins can log in to the system.
b) Students are able to book buses.
c) Students are able to check seats availability.
d) Students are able to check bus availability.
e) The admin able to update buses every day.
f) Admin is able to add students into the system.

4.2.2 Nonfunctional requirements

a) Security

Data like password detail of the admin and students should be confidential, to make this
data safe there is need for highly secured algorithm.

b) Availability.

The application should be available for 24hours a day. Whatever the traffic is, the availability
of the application should not be affected.

c) Performance.

It should be high enough that the user should not wait long enough for any
required.

12
4.3. Data Analysis
During development of the system I used the following data collection tools.

• Questionnaires.
• Observations
• Interviews.

4.3.1 Questionnaire analysis

1. Have you ever used school bus transport?
Yes=9/12*100=75%
No=3/12*100=25%

Figure 4 1: Chart illustrates the number of students who have booked school bus transport verse those
who have not used.

13
 2 How are the services if yes?
Good=3/12*100=25%
Average=3/12*100=25%.
Poor=6/12*100=50%.

Figure 4 2: Presents the feedback of the students on the school bus transport department services.

14
2 Have you ever lost your bus ticket?
Yes=8/12*100=60%
No=4/12*100=40%

Figure 4 3: Describes the percentage at which students keep their tickets that is if ever lost bus ticket or
not.

15
3 How often do you use the school bus transport?
often=5/12*100=40%.
Average=6/12*100=50.
Hardly=1/12*100=10%

Figure 4 4: Describes the frequency at which students use the school bus transport services.

16
4 Do you have access to the internet?
Yes=11/12*100=50%
No=1/12*100=50%.

Figure 4 5: illustrates the availability of different patients to internet

17
4.3.2. Observation
I participated in watching the students’ activities in order to obtain facts about the day
to day activities in the school. The reason why I used this technique was
i. To obtain first hand and reliable information from students and
administrator.
ii. I could see exactly what is being done especially for tasks that are
difficult to explain in words.

4.3.3 Interview
I used interviews to aid me to understand in a detailed manner how the process and the
operations the school bus transport tackled currently. This information laid a firm foundation on
how to design my system through the user experiences I got from respondents.
4.4 System Analysis
System analysis and design deal with planning the development of information
systems through understanding and specifying in detail what a system should do and
how the components of the System should be implemented and work together.
System analysis is conducted for the purpose of studying a system or its parts in
order to identify its objectives. It is a problem solving technique that improves the
system and ensures that all the components of the system work efficiently to
accomplish their purpose. Analysis specifies what the system should do. It is a
process of planning a new business system or replacing an existing system by
defining its components or modules to satisfy the specific requirements.

18
4.4.1 Use case analysis
Use case diagram is a representation of users’ interaction with the system that shows the
relationship between the user and the different use cases in which the user is involved.

Figure 4 6: illustrates the availability of different patients to internet.

19
4.4.2 Entity Relation Diagram

Figure 4 7: database schema describing the layout of the database and how different entities are
structured .

20
4.4.3 class diagram

Figure 4 8: Class diagram: describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.

21
4.4.4 Flowchart

start

Do you have an
No
account?

Get an Account yes

login

No

Successful
login?

Yes

View profile Check Buses Available Make Booking

No

Update profile Yes Update Make Payment

Stop

Figure 4 9: System flow diagrams describing the process flow and data in the system

22
4.4.5 Sequence diagram

Figure 4 10: Sequence Diagram

23
 CHAPTER FIVE: SYSTEM TESTING

5.1 Introduction
The system has gone through several testing steps, all of them are aimed at evaluation of the
system to determine how best or poor the system takes in the input for processing and eventually
giving the output. While testing my system, I used various techniques for testing to ensure a
verifiable procedure of development and giving valid output as per the statement of the
functional and non-functional requirements.

5.2 Types of testing

Testing is used to identify defects in the program and is used to help judge whether or not
software is usable in practice. The system was subjected to verification and validation to ensure
that it confronts and meets user requirements. It was also subjected to a thorough test to ensure
that it was reliable, fast enough and to see its ability to cater to the high number of students. It
was also tested to ensure it was conforming to the requirements and functioning as expected. The
parameters used during testing of the functionality of the system are as follows,
I. Reliability.
This test was conducted to mainly ensure that the system does not give in into traffic and
no delays due to the high traffic of data.
II. Correctness of the system.
This test was to ensure that each user gets the information or access to the information he
or she is authorized to access.
III. Completeness of the system.
This was carried out to ensure the system meets the functional and non-functional
requirements as specified before.
IV. Flexibility/Scalability.
This was for the backend part where the system was tested to ensure the capability of
holding more data during the extension of the system.
V. Constraint Validation
The password strength is one of the constraints a system should carry so as to ensure
secure and strong passwords are implemented. The students will be registered by the
administrator and they are able to log into the mobile app using the registration number
or the national id as the password.

24
5.2.3. Unit testing
This system was tested unit by unit through running the different sections of code, I e Login
module for authentication, booking for a bus ticket by students and making of payments.

Module Expected Results Actual Results

Log in module Grant access to the correct credentials The system logins one to the system if
after comparison with the existing data they provide correct credentials and
in users table. gives an error message to wrong
credentials given.
Booking This test was carried out to ensure Capture and submit the data to the
module correct details given that will act as database.
input in producing receipts.
Payment This test was carried out to ensure that The M pesa is prompted on the screen and
module one is able to make payment after students can enter the amount of money
booking a bus. that is reserved for bus ticket .
Ticket module Receive an e-ticket after booking and One will receive an e-ticket which
making the fare charges. will be accessed at the navigation
menu of the system
Admin login Grant access to the correct credentials The system logins one to the system if
after comparison with the existing data they provide correct credentials and
in users table. gives an error message to wrong
credentials given.
Add students, This test was carried out to test that the Captures and submits data to the
buses, trips administrator can add students and database.
module buses to the system through backend
website.
Bookings and Test carried to help admin keep track Keep track of those students who have
total fare of all students who have booked tickets booked tickets and the total fare paid.
at particular time and fare collected.

Table 5 1: Unit testing on login and registration module

25
5.2.4 Integration testing
This type of testing shows whether different modules of the system can be brought together to
perform as a unit. For instance, administrator adds students to the system, add buses to the
system and performs the trip scheduling process. On the other hand, the students can be able to
see buses and trips available, book available bus, make payment and receive an e-ticket.
Test Expected Results Actual Results
Booking module. The student books a bus Booked successful if all the
ticket by logging in to the requirements are done that is
android application system, choosing a trip and making
checks on all available buses payment.
and trips, select appropriate
trip for self, book for himself
and two more people if need
be and the make necessary
payment. The student the
receives an e-ticket.
Administrator module The admin adds students to Works well as is can be
the system, add buses and accessed by students on the
schedule the trips. app.
Table 5 2: Integration module showing how functions are integrated to function together

5.2.5 System testing

System testing was applied to confirm the conformance of the whole system to the requirements,
tests the harmony existing in between the different modules in achieving the ultimate objective
of the development process. This includes coordination of different roles, i.e., addition of
students, buses and trips to the system and booking process all the way to making payment and
receiving an e-ticket.
Test Expected Results Actual Results
System testing The system proved to have Able to meet both the
met the functional and requirements as specified.
nonfunctional requirements
having achieved the
objective.

Table 5 3: System testing

26
5.2.6 Acceptance testing
This testing can be viewed and categorized into two: one, a smoke test that was used as an
acceptance test prior to introducing new build to the main testing process before integration.
Secondly, acceptance testing performed by the students, around the school on their own devices.
I specifically used this test to check if I had met user requirements in the development of the
software aesthetically and also in terms of functionality.
Test Expected Results Actual Results
Acceptance testing The system gives, friendly The several users got satisfied
user interface on both the with the system features since
android app and the admin it is easy to use, and an
web app with good attractive interface.
navigation features.

Table 5 4: Acceptance testing

27
5.3. Functional Testing and Results Samples
5.3.1. Login module for the android app
The student logs into the system with the correct credentials that is national id number or the
registration number and a password.

Figure 5. 1: shows a login page of the mobile app

28
Figure 5. 2: shows the login error upon wrong credential provision

29
5.3.2. On the dashboard page
If the student login with correct credentials he or she will be directed here.

Figure 5. 3: The mobile app dashboard

30
5.3.3. Booking page

The student the selects the bus which heads towards his or her destination. For example, if
heading from Nyeri town to school he will or she selects it.

Figure 5. 4: booking page

31
5.3.4. Payment page
Then student the selects the Book for me button to book a ticket and is therefore directed to
payment where he/she enters the phone number and clicks on the payment button and prompted
to enter the m pesa pin to make payment

Figure 5. 5: payment page

32
5.3.5 The m pesa prompt
Once the student enters the phone number and clicks pay, the m pesa prompt will appear on the screen
and he can enter the PIN to make payments.

Figure 5. 6: m-pesa prompt

33
5.3.4 The e-ticket after payment
This is an e-ticket that will be used at the school bus terminal. The students will access it the
system menu and are able to download. An SMS notification will also be sent to students for
clarification purposes

Figure 5. 7: e-ticket

5.4. Web App

5.4.1. Login module for the web app
The login module includes a form which takes the inputs e-mail address and password to ensure
only authorized access. It returns a dashboard page if valid user credentials are supplied else it
returns an error.

34
Figure 5. 8: shows a login page

After input of details, the system checks in the system database with the matching credentials.
Wrong credentials return, Invalid Login attempt error message

Figure 5. 9: shows the login error upon wrong credential provision

35
5.4.2 On the dashboard page
Displays a list of activities one should undertake in the system. It’s helpful for easier user
navigation in the system hence increase the user friendliness of the system.

Figure 5. 10: shows the dashboard page

5.4.3. Adding students page

Figure 5. 11: The page showing where students are added to the system

36
5.4.4. Adding buses page

Figure 5. 12: The page for adding buses

37
5.4.5. scheduling trips page

Figure 5. 13: The page for scheduling trips

5.4.6. Track of students who have booked tickets

Figure 5. 14: The page where admin can keep track of all students who have booked the bus tickets

38
 5.4.7 track of all payments

Figure 5. 15: The page that shows all the amount paid by students

39
 CHAPTER 6: IMPLEMENTATION AND DEPLOYMENT

6.1 Implementation Strategy

6.1.1 Introduction
Having the requirements being quite clear. I started on the implementation of the findings. It is in
this stage that I did acquire and developed the programs that will help meet the expectations of
the system. Moreover, I developed the interfaces that will interact with the students and
administrator of the system. The admin user, the manager of the system, the students who are to
use the system to book the bus tickets and make online payments.
6.1.2 System Specification Front end development
Android
I. Android studio IDE
Web app
I. Html
II. Bootstrap, JavaScript
III. CSS
Backend development
I. PHP MYSQL
Software requirements
I. Visual studio community 2015

6.2: Deployment
Deployment includes all set of activities that makes the software available for use by the target
clients and users of the system. The general deployment process consists of several interrelated
activities with possible transitions between them. Deployment activities include: release,
installation, activation and deactivation, adapt, update, built-in, versions and tracking.
6.2.1 Deployment System Requirements
This being an online application, the following were the requirements to have it fully deployed.
I. Internet connectivity
II. Mobile phone
III. A hosting service

40
6.3 Support and Training
Having most students with mobile phones and how to operate them will make easy transition
into using the mobile system. Most students have mobile phone and knows how to operate them
on their own and this will aid a lot in using the system.
It calls for user education of different groups of people how to handle the system by use of
presentations and personal training. Once the training is complete, the continued support of the
system will be provided, which will ensure that the system achieves its objectives and any errors
realized in the process is corrected. The support activities will enhance the maintenance of the
system which will result in debugging any module that develops errors and bugs that arise as the
deployment process is ongoing.

41
 CHAPTER 7: CONCLUSION AND RECOMMED ATIONS
7.1. Discussion
It can be observed that computer applications are very important in every field of
human endeavor. This system is a step up on the way to achieve an efficient, reliable and
effective way of securing the way Bus ticketing is done. This system is an automation of the old
system and above all it shows its uniqueness on comparison to them that already existed through
ticketing process. It will also reduce the workload of the staff, reduce the time used for making
reservation at the bus terminal and also increase efficiency. The application also has the ability to
update records in various files automatically thereby relieving the company’s staff the stress of
working from file security of data
7.2. Recommendations
Research and development are continuous processes; this is the same in computer and software
development. However, this work is recommended for Dedan Kimathi University school
transport department, since their operation are still carried out manually, it can also be useful to
other Bus Transportation industries whose processes are still manually done. The system can
contribute more on those bus representatives handling the account if it can generate reports by
trip so that they will no longer go to a certain module to check the buses and its details.
To reverse the above problems and realize improvements in succeeding developments, I would
make the following recommendations.
I. The internet connection should be extended to the most remote areas to enable a wide
range of population to gain access to the system from all over the school.
II. The system can be deployed on a mobile phone, android or IOS, so to accommodate
the rising numbers of smartphones.
III. The institution can look into facilitating the project through financing the perfection
of the android and web application to maximize the utilization of buses available.

7.3. Limitations
The development of this system has faced some few challenges
I. Information source- information required to develop the application was not readily
available on the internet.
II. Unavailability and uncooperative respondents- it was hard getting respondents from
the various students and other respondents who could set aside time and respond to
the questions that were urgent in the development of the system.
III. Financial incapacitation- there was a lot of finances required in printing of
documents, questionnaires and purchase of internet bundles.

42
7.4. Conclusion
The system will generally help the students access to online transport booking services by
setting standard high in terms of efficiency, governance and accountability of the operations.
This project has helped me familiarize with market expectations. Above all I have learnt to
deliver within a short period of time which will come in handy in my career.

43
 REFERENCES

Bus travel through Europe | FlixBus. (n.d.). Retrieved April 19, 2020, from FLIXBUS:
[Link]

BUSCAR online ticket booking portal. (n.d.). Retrieved April 19, 2020, from BUSCAR:
[Link]

[Link] - Online Bus Ticket Bookings. (n.d.). Retrieved April 19, 2020, from Buupass:
[Link]

Madaraka Express -Travel Kenya -Online Booking. (n.d.). Retrieved April 19, 2020, from Madaraka -
Online Bookinng: [Link]

SDLC-Waterfall model. (n.d.). Retrieved April 19, 2020, from tutorialspoint:

[Link]

Transport - wikipedia. (n.d.). Retrieved April 19, 2020, from Transport:

[Link]

Nwakanma, I. C., Etus, C., Ajere, I., & Agomuo, U. (2015). Key words : OBTRS , Electronic Ticketing , ITC ,
Reservation , Transportation Background of Study The prevalent view in various global circles is
that man is presently living in an. International Journal of Computer Science and Statistics, 1(July
2018), 1–17.
ONLINE BUS TICKETING SYSTEM. (2007). (June).

44
 APPENDICES

Appendix I Time schedule

.
Tasks Time in months

May June July August September October November December

Requirements
Gathering

Analysis

System Design

Coding

Testing

Documentation

Figure 1 Gantt chart: the Gantt chart describes various steps and the time they all consumed during the
whole process of developing the system

45
Appendix II Budget

Particulars Item Price

1. A computer 50,000/=

2. Internet 5,000/=

3. Research 42,000/=

4. Printing and binding costs 5,000/=

5. Software licenses 15,000/=

Total amount 117,000

Figure 2 Budget: indicates the total amount of money used for the for setting up and running the project

46
Appendix III Questionnaire

Sample respondents Response

Question
1. Have you ever used school bus Yes 9 Yes [ ]
transport? No 3 No [ ]

2. How are the services? Good 3 Good [ ]

Average 3 Poor Average [ ]
6 Poor [ ]
3 Have you ever lost your bus ticket? Yes 8 Yes [ ]
No 4 No [ ]

4 How often do you use the school bus Often 5 Often [ ]

transport? Average 6 Average [ ]
Hardly 1 Hardly. [ ]
5 Do you access to the internet? Yes 11 Yes [ ]
No 1 No [ ]

Figure 3 Questionnaire: showing the set of questions used to collect data from the various parts I carried
out the interview.

47