CAPSTONE PROJECT REPORT

(Project Term January-May 2023)

ONLINE BUS TICKET BOOKING

Submitted by

Solipuram Kranthi Kumar Registration Number :11912330

Yellu Madhukar Registration Number :11903309

Project Group Number: CSERGC0355

Course Code: CSE455-CAPSTONE PROJECT

Under the Guidance of

Mr. Anurag Singh

School of Computer Science and Engineering

1
PAC Form

2
 DECLARATION

We hereby declare that the project work entitled Online Bus Ticket Booking is an authentic
record of our own work carried out as requirements of Capstone Project for the award of
B.Tech degree in Computer Science and Engineering from Lovely Professional University,
Phagwara, under the guidance of Mr. Anurag Singh, during August to November 2022. All
the information furnished in this capstone project report is based on our own intensive work
and is genuine.

Project Group Number: CSERGC0355

Name of Student 1: Solipuram Kranthikumar

Registration Number: 11912330

Name of Student 2: Yellu Madhukar

Registration Number: 11903309

Solipuram Kranthikumar
Date:05/05/2023

Yellu Madhukar
Date:05/05/2023

3
 CERTIFICATE

This is to certify that the declaration statement made by this group of students is correct to
the best of my knowledge and belief. They have completed this Capstone Project under my
guidance and supervision. The present work is the result of their original investigation, effort
and study. No part of the work has ever been submitted for any other degree at any
University. The Capstone Project is fit for the submission and partial fulfillment of the
conditions for the award of B.Tech degree in Computer Science and Engineering from
Lovely Professional University, Phagwara.

Signature and Name of the Mentor

Designation

School of Computer Science and Engineering,

Lovely Professional University,
Phagwara, Punjab.

Date :

4
 ACKNOWLEDGEMENT

We would like to express our sincere gratitude to Mr. Anurag Singh,

Assistant Professor, School of Computer Science and Engineering, Lovely
Professional University, for his ongoing support and the resources he gave us to
finish our project on schedule.

We would like to express our sincere appreciation to our dear Dr. Max
Bhatia, Head of the Department, School of Computer Science and Engineering,
Lovely Professional University, for allowing us to complete this project.

We convey our heartfelt gratitude to my parents and family for their

unwavering support, dedication, comprehension, and love.

Finally, we would like to express our heartfelt gratitude to everyone

who directly or indirectly assisted us in the successful completion of this project
work.

Solipuram Kranthikumar

(11912330)

Yellu Madhukar

(11903309)

5
Contents
PAC Form 2
Declaration 3
Certificate
4
Acknowledgment
5
CHAPTER 1: INTRODUCTION
9
ABSTRACT
9
1.1 PROJECT BACKGROUND
10
1.2 PROBLEM STATEMENT
11
1.3PROPOSED SOLUTION
11
1.4OBJECTIVES
11
1.5PROJECT JUSTIFICATION
12
1.6PROJECT SCOPE
12
1.7PROJECT LIMITATIONS
13
CHAPTER 2: LITERATURE REVIEW
13
2.1 INTRODUCTION
13
2.2 EXISTING SYSTEMS
15
2.2.1. Mobile Ticketing (M-Ticketing)
15
2.2.2. SUMMARY AND CONCLUSION
16

6
CHAPTER 3: METHODOLOGY
16
3.1 INTRODUCTION
16
3.1.1 SYSTEM DEVELOPMENT METHODOLOGY
16
3.1.2 JUSTIFICATION FOR THE METHODOLOGY
17
3.1.3 DATA COLLECTION APPROACHES
17
3.4 DATA ANALYSIS TOOLS TECHNIQUES
18
3.5 FEASILBILITY STUDY
18
3.5.1 Social operational feasibility
18
3.5.2 Legal feasibility
19
3.5.3 Economic feasibility
19
3.5.4 Technical feasibility
19
3.5.5 Schedule feasibility
20
3.6 DEVELOPMENT TOOLS
20
3.6.1 Programming tools
20
3.6.2 Database tools
20
3.6.3 System modeling tools
20
3.7 SUMMARY
20
CHAPTER 4: SYSTEM ANALYSIS AND REQUIREMENT MODELLING
21

7
 4.1 INTRODUCTION
21
4.2 DESCRIPTION OF THE CURRENT SYSTEM
21
4.2.1 Overview of the current system
22
4.2.2 Problems associated with the current system
22
4.3 SYSTEM REQUIREMENTS
22
4.3.1 Functional requirements
22
4.3.2 Non-functional requirements
23
4.3.3 Domain requirements
23
4.3.4 Database requirements
23
4.4 SYSTEM MODELLING
24
CHAPTER 5: SYSTEM DESIG
29
5.1 INTRODUCTION
29
5.2 DESCRIPTION OF THE SYSTEM
29
5.2.1 Home page
29
5.2.2 About us page
29
5.2.3 Contacts us and addresses
30
5.2.4 Customer registration
30
5.2.5 User log in
31

8
 5.2.6 Customer booking
31
5.2.7 Administrator log in
32
5.2.8 Administrator update of the booking
32
5.2.9 Administrator update of payment
33
5.3 SCREENSHOTS
33
5.5 INTERFACE DESIGN
40
CHAPTER 6: SYSTEM IMPLEMENTATION
43
6.1 INTRODUCTION
43
6.2 TOOLS USED FOR CODING AND TESTING
43
6.2.1 Coding tools
43
6.2.2 Testing tools performance test
44
6.3 SYSTEM TEST PLAN
45
6.4 USER ACCEPTANCE TESTING
45
6.5 PROPOSED CHANGE-OVER TECHNIQUES
46
CHAPTER 7: CONCLUSIONS AND RECOMMENDATIONS
47
7.1 RECOMMENDATIONS
47
7.1.1 Reduction in strictness of the Time deadlines
47
7.1.2 Provision of project finances to the students
47

9
 7.1.3 Compelling some institutions to pave way for the students to develop
47
7.1.4 Future improvements
48
7.2 CONCLUSION
48

10
 CHAPTER 1: INTRODUCTION

ABSTRACT:

The Online Bus Ticket Reservation System is a web-based application that allows visitors to
check bus ticket availability, buy bus ticket and pay the bus ticket online. This system is
established for all the home/office users after gaining access from the administrator. Chapter
I is Introduction. It describes the project background, problem statement, objectives, scopes,
project significance and expected output of the proposed system. Chapter II is Literature
Review and Project Methodology. It describes facts and findings for electronic ticketing,
describes methodology that are used to develop the system, state out project requirements,
explain action plan prior to the end of the project and attach Gantt chart. Chapter III is
Analysis. It is concerned with first studying the existing system, then using the information
gathered to define the requirements for a new system. Besides that, analysis follows the
problem recognition and feasibility phases and must be completed before the design phase
can begin. Chapter IV is Design. It defines the results of the analysis of the preliminary
design and the system architecture, DFD, Data Dictionary, Data Normalization, Entity
Relationship Diagram are established. Besides that, it describes a plan to implement the
requirements. Furthermore, details on computer programming languages and environments,
machines, packages, application architecture, distributed architecture layering; memory size,
platform, interfaces, and many other engineering details are established in Chapter V. Chapter
IV is Implementation. It describes software development environment set-up, software
configuration management and implementation status for Bus Ticket Reservation System.
Chapter VI is Testing. It concerns test plan, test strategy, test design, test results and analysis
are used to test Bus Ticket Reservation System. Conclusion is chapter used to conclude and
summary all the Chapters. Currently, using online services to get information is becoming
more and more common. Due to its wide audience and simple accessibility, the internet is
perfect for use as a tool for marketing and information dissemination. Although the internet
has some negative effects, its positive effects outweigh these and are very beneficial for all
users. The purpose of this program for purchasing tickets is to handle any problems that

11
customers could have ordering tickets or looking for information about tickets or other
problems. With the internet, information about anything can be found quickly and
effortlessly. Smartphones and computers, which are hugely common in the present period,
may be used to access the internet. A dynamic and extensive information system can be
created using the internet, which is a very effective tool. Based on the many advantages, a
"Design of a Bus Ticket Reservation System" was developed, and features offered by the
internet. System for booking tickets online and on time. Version 8 of Macromedia
Dreamweaver, PHP, and MySQL were used to create this web-based application. This
information system was developed to make it simple for consumers to purchase tickets and to
obtain any other information quickly and easily they might require, including departure
times, the kind of vehicle being used, the kinds of routes that are available, and other
information the client may desire.

1.1PROJECT BACKGROUND:

This chapter tries to provide an overview of the project's background, problem

description, objectives, scopes, importance, and anticipated system output. The Bus
Ticket Booking System is the system. This project focuses on the online ticketing system
of the contemporary coast bus operator, which frequently has issues with its scheduling
and ticketing procedures. To offer better customer service, this project plans to
computerize its semi-computerized ticketing system. As a result, the business may
provide the consumer or passenger with a simpler mode of transportation. E-tickets serve
as proof that the owners are authorized to visit a venue for entertainment, utilize a mode
of transportation, or use certain Internet services. The quickest and easiest way to take a
bus is to purchase a ticket online using the bus company's bus ticket reservation system.
The internet platform is a new one.

Because it is just now becoming established in bus companies worldwide, including in

Kenya. Currently, employees at the bus ticket counter sell tickets at the counter using an
internal system. The customer must travel to the counter to purchase a bus ticket because

12
 they are now unable to do it online. Customers may have to wait in a big queue to
purchase bus tickets and get information. In addition, the customer does not permit
purchasing a bus ticket over the phone, and Transnational's phone line is constantly busy.
The clients are severely inconvenienced by this. The consumer may quickly purchase bus
tickets, make payments, cancel reservations, and request information online thanks to the
online bus ticket reservation system. Additionally, employees can use the Bus Ticket
Reservation System to sell bus tickets after checking the availability for customers and
printing the tickets for those who are waiting in queue.

1.2PROBLEM STATEMENT:

The system that the workers at the counter are using now is an internal one that is
only utilized to sell bus tickets at the counter. To purchase a bus ticket or get a bus
timetable, a customer must approach the counter. Additionally, consumers must pay in
cash when purchasing bus tickets, and they occasionally may wait a long time in queue.
In addition, customers are not permitted to purchase bus tickets over the phone, and the
bus company's phone line is constantly busy.

1.3PROPOSED SOLUTION:
The establishment of an online bus ticket purchasing system is the solution to this
issue. Bus tickets be purchased online anytime, day or night, and they cannot be
misplaced, stolen, or left behind. Additionally, buyers may check the availability of bus
tickets online before making a purchase.

1.4OBJECTIVES:

The online system's key goals are as follows:

13
  To offer online bus ticket purchasing capabilities. There is no need to stand in line
to purchase bus tickets at the counter when using the online method.
 To make it possible for customers to check the bus ticket's availability online.
Through the system, customers may view the departure and arrival times for each
bus operated by Transnational.

 To make purchasing bus tickets online easier. The customer must use M-Pesa
money services to pay for the bus ticket.

 To lower the number of employees working at the point of sale. After the debut of
the online bus ticket purchasing system, the number of employees at the counter
may decrease.

1.5PROJECT JUSTIFICATION:

As was noted in the preceding section, the online system is only beginning to take
hold in the nation's transport network. For the firm's clients, the bus company, and
everyone else, it is crucial. Customers value it because they can use it to check the
availability of bus tickets, purchase them, cancel them, and pay for them online. E-tickets
are distinct from traditional paper tickets because they are safer, quicker, more
dependable, and less expensive. Additionally, other bus companies might use this idea to
satisfy their clients. The bus firm will make more money since the online method will
draw in more people and because selling bus tickets online is more efficient than hiring
lots of personnel to work the counter. Additionally, based on the margin returns, the
owner can plan the bus routes. By comparing bus performance, this is accomplished. The
route, operational expenses along a certain route, and the frequency of breakdowns per
bus are only a few of the comparative criteria in this module.

1.6 PROJECT SCOPE:

14
 The program is a web-based one. By entering onto the customer portal, customers
may see the available buses for a certain route and the available seats.

The employees may compare bus performance and keep track of other associated
business performance concerns by signing into the system through the staff portal.

1.7PROJECT LIMITATIONS:

 User acceptance:
Because they worry about losing their jobs, some staff members may not be in
favor of the counter system becoming online.

 Computer literacy level:

It's possible that the target audience won't have the necessary ICT abilities to
make use of the system as planned. By providing to train their consumers, this
might result in expenditures for the business.
 Limited system testing:
Ineffective unit and system testing might result in usability problems like
delays in some modules.

CHAPTER 2: LITERATURE REVIEW

2.1 INTRODUCTION

One of the industries that has done the best job in mobile application optimization is
tourism. Buell, Campbell, and Frei (2010) estimate that 50% of the current tourist
recommender systems are mobile-friendly. There are four primary kinds of mobile travel
applications available in the tourist sector: "Online Booking," "Information Resources,"

15
"Location Based Services," and "Trip Journals." (Smirnov, Kashevnik, Shilov, Teslya, &
Shabaev, 2014) The "Online Bookings" category. These programs enable travelers to book
reservations online for a variety of services, such as bus transportation, car rentals, hotels,
and airline tickets. Typically, before a trip, travelers request applications from this group. In
accordance with (Gunduz & Pathan, 2013), online sales of light tickets accounted for 32% of
all online sales, hotels, and tours for 26%, and event management tickets for 20% of all
online sales worldwide. In the United States, 79 percent of mobile phones are used for
internet purchasing purposes. Customers rely on their applications for more social
communication, business transactions, and neighborhood connection. The findings of these
studies indicate that as providers of products and services, airlines, bus lines, and travel
agencies should increase their ticket offerings via mobile shopping. Additionally, the
technology known as self-service technology (SST) will make service delivery simpler and
more efficient when the consumer offers the service independently. In the process of
replacing the conventional customer-employee interaction, self-service technology allows the
customer to provide the service independently (Wang, Harris, & Patterson, 2012).
Additionally, customers don't need to go to a company office to inquire about banking
transactions, ticket information, or bill payment thanks to this service, which makes it easier
for customers to meet their demands and saves them money, time, and effort. The second
reason for using self-service technologies is to facilitate transactions. With the help of this
technology, customers may make purchases, pay bills, or place online orders without having
to speak with staff first. Self-help is the third goal of self-service technology. The consumer
is given the opportunity to study, gain knowledge, be trained, and render their own service
thanks to these SSTs. Additionally, self-service technologies are advantageous to both
businesses and consumers. SSTs are an efficient way to increase accessibility, ubiquitous
obtainability, time and money savings, and anxiety reduction. Electronic ticketing systems,
sometimes known as e-ticket systems, are now especially well-known among travelers
everywhere. Due to several benefits that customers may obtain through electronic ticketing,
such as avoiding lines at ticket booths, this method has replaced the conventional one. The
emergence of the internet coincided with the beginning of the electronic ticketing system, but
there were already several paper-based or smart card-based ticketing systems in operation.

16
All ticketing systems have advantages and disadvantages, and the budget has already
classified the advantages and disadvantages of various ticketing systems.

2.2 EXISTING SYSTEMS:

2.2.1. Mobile Ticketing (M-Ticketing):

According to Skarcia, Belani, and Illes (2009), mobile ticketing (m-ticketing) is widely
described as the ordering, purchasing, delivery, and use of goods and services using mobile
technology such as Wireless Application Protocol (WAP). A relatively new and developing
sector of the rapidly expanding e-commerce market is mobile ticketing. By 2013, it is
predicted that 400 million mobile users worldwide would use their phones for tickets,
bringing the total value of gross mobile ticketing transactions to $92 billion (Eicher et al.,
2012). The future of mobile ticketing has been a focus of research for many years. M-
ticketing enables a client to buy a ticket using a mobile phone application that is authentic
and valid. Users of the mobile ticket can save digital tickets on their phones thanks to the
value-added services offered by the application. As a result, the consumer's ticket will be less
likely to be lost and will be paperless, durable, affordable, and environmentally friendly.
According to Ceipidor et al. (2013), the mobile ticketing procedure may generally be broken
down into the following steps:

 Registration: To sell tickets online, a firm must register with complete details about
its products and services.

 Provisioning: Permit a mobile application to communicate with users so that a

purchase may be made.

 Validation: The electronic validation system between the business and the customer is
used to validate and legitimate the ticket.

17
  Checking the ticket: The controller must confirm and approve the sale of the mobile
ticket and display it as the passenger's legitimate ticket in accordance with the
conditions stated on the ticket.

2.2.2. SUMMARY AND CONCLUSION:

The mobile bus ticketing system (MBTS) is undoubtedly one of the world's best
opportunities for lowering costs and improving traveler accessibility. With the help of this
initiative, the flow of tickets will be processed more slowly, less paper will be used, and
travelers will have more freedom and flexibility to change their trip plans in urban areas.
Other significant drawbacks of this method include the fact that a mobile ticket cannot be
misplaced or stolen, unlike a ticket sent by mail, which runs the risk of being sent to the
wrong address. Customers' lives will be made simpler by MBTS, and they may use the
service on their own time, anywhere, and using any device.

CHAPTER 3: METHODOLOGY

3.1 INTRODUCTION:

The planning for the execution phase must be completed. Only if the right approach is
chosen can this be accomplished. To ensure that all project life cycle tasks are completed
without taking any short cuts, methodology is crucial. The use of methodology enables
system developers to complete the whole system one step at a time. The selection of a
technique for the Modern Coast Bus Company's installation of an online bus ticketing system
is covered in the part that follows.

18
3.1.1 SYSTEM DEVELOPMENT METHODOLOGY:

All phases of the system development lifecycle (SDLC) were completed for this system.
A waterfall technique was used to design this system in accordance with the characteristics of
the system and the data gathered. The steps of this process were feasibility analysis,
specification design, requirement analysis, coding, testing, integration, and maintenance.
Every phase had a clearly defined beginning and end and needed a distinct amount of work.
Each level must be finished before moving on to the next.

3.1.2 JUSTIFICATION FOR THE METHODOLOGY:

Because each step had to be finished before the next one could begin, and no phase could
be left unattended, the waterfall technique developed a full-quality system and an error-free
system. However, based on the information gathered on user needs, there was no question as
to what needed to be built because the user demand was well understood. Like other
techniques, such as fast prototyping methods, the method was also less expensive since there
was no need to repeat a procedure after it was finished, which reduced resource waste.

3.1.3 DATA COLLECTION APPROACHES:

Appropriate data collection techniques were required to acquire data from the Modern
Coast Bus Ticket Booking System and its users. Among these methods were the following:

3.1.3.1 Observation:

This required the researcher to travel to the area of investigation, keep a close watch on
how the organization under study functions, discover any potential operating system flaws,
analyze the issues, and create a remedy based on the observations. This method was used
because it offers first-hand knowledge that is dependable and accurate and because it gave a
summary of the system. It is the method that works the best.

3.1.3.2 Interviews:

19
 This is an in-person interview between the system analyst (interviewer) and the system's
users. When there were few replies, this was employed to explain and confirm the
information obtained. This method was crucial because it allowed for the enrichment of the
data necessary for the quality processing of some data that could not be obtained through
direct observation without the use of interviews.

3.1.3.3 Questionnaires:

A questionnaire is a list of questions created by the person gathering data on a piece of

paper and sent to individuals who then answer the questions in private without the
interviewer present. After finishing, the respondent will provide the data collector with the
answers. This method was crucial since some respondents lacked the confidence to answer
questions posed by the interview panel, therefore a questionnaire was the best option for
them.

3.4 DATA ANALYSIS TOOLS TECHNIQUES:

Data analysis is the process of analyzing data by applying logical and analytical
reasoning to each individual piece of available data. After being obtained and evaluated, data
from multiple sources was analyzed to draw a conclusion. The acquired data or facts were
used to evaluate the present system. The following were some of these tools: Use of charts
and tables.

3.5 FEASILBILITY STUDY:

The goal of the feasibility study was to evaluate the existing system and decide if a new
system should be implemented to replace it or not. It tended to examine the viability of the
present system. In essence, a cost-benefit analysis was used to examine the viability of a new
system. It covered: Schedule feasibility, technical feasibility, economic feasibility, and
operational feasibility.

3.5.1 Social operational feasibility:

20
 This is a gauge of how successfully a proposed system addresses the issues, seizes the
opportunities, and complies with the needs found during the requirements analysis stage of
system development. It addressed how the system affected the culture of the organization
today. The planned development projects' compatibility with the current business
environment and goals in terms of the development timetable, delivery date, corporate
culture, and existing business processes were the focus of the operational feasibility
evaluation. Desired operational results were communicated during design and development
to guarantee success. These included factors that depended on the design, such as cost,
sustainability, affordability, usability, predictability, usability, usability, and others. There
were to be realized behaviors. To satisfy the requirements, system design and development
requires the proper and timely application of engineering and managerial efforts. When a
system's technical and operational features are built into the design, it may best fulfil its
intended function. As a result, operational feasibility is a crucial component of systems
engineering and must be considered from the beginning of the design process. It was
determined that the Modern Coast Bus Ticket Booking System solutions were trustworthy
and versatile, making them operationally viable.

3.5.2 Legal feasibility:

This investigation was done to see if the suggested system will violate any laws. The
Local Data Protection Acts must be followed by these data processing systems. The new
system's legal implications were examined, and then the Modern Coast Bus Ticket Booking
System took the necessary steps to safeguard the interests of its customers. This step of the
Modern Coast Bus Ticket Booking System Solutions was completed successfully, and the
system was determined to be workable.

3.5.3 Economic feasibility:

The goal of the economic feasibility analysis was to ascertain what positive economic
effects the suggested system would have for the organization. All the anticipated advantages
were quantified and identified. Usually, a Cost-Benefit Analysis (CBA) was conducted as
part of this evaluation. The online bus company booking system for Modern Coast was

21
unquestionably determined to be commercially viable, and there is little chance that it would
soon lose its utility.

3.5.4 Technical feasibility:

The evaluation's main goal was to comprehend the technological resources now available
in the ticket booking industry and how well they would work with the suggested solution.
This was done to evaluate the new system's hardware and software requirements. It also
examined if the existing facilities were sufficient for implementing the new system.

3.5.5 Schedule feasibility:

A project's schedule's viability is a measure of its timeliness. If the project took too long
to finish before it was beneficial, it would fail. This calls for making an estimation of the
system's development time and determining if it can be finished within a specific time frame
utilizing techniques like a payback period. It was evident from the system's timetable that the
project could be completed on schedule because it would only take about 3 months, which
was a short time for such a system.

3.6 DEVELOPMENT TOOLS:

3.6.1 Programming tools:

For coding, PHP and HTML were chosen since they worked well with web-based
applications. While CSS was used to style the web pages and create aesthetically pleasing
and user-friendly system interfaces, JAVASCRIPT was also utilized for scripting reasons.
The code was edited using the NOTEPAD++ editor.

3.6.2 Database tools:

The database was created and connected using XAMPP, which also includes
PhpMyAdmin for hosting and managing databases.

3.6.3 System modeling tools:

22
 During the development phase, system modelling tools such use case diagrams, data flow
diagrams, and sequence diagrams would be developed.

3.7 SUMMARY:

It is clear from the presented approach that each phase in the system development
lifecycle must be completed by every system. The above-mentioned technique was applied
throughout the system development, which aided in the creation of a booking system that
would meet the demands of both the Modern Coast organization and its customers.

CHAPTER 4: SYSTEM ANALYSIS AND REQUIREMENT

MODELLING.

4.1 INTRODUCTION:

This chapter will analyze the present system in use for the Modern Coast Bus Ticket
Booking System and do any necessary analyses. Identifying whether a new system is
necessary or not is the main goal of this. The chapter also provides system requirements
through a variety of models that help one better understand how the present system operates.
The chapter makes use of modelling techniques including DFDs, flowcharts, use case
diagrams, and others.

4.2 DESCRIPTION OF THE CURRENT SYSTEM:

4.2.1 Overview of the current system:

Now, Modern Coast Bus Ticket Booking technology lacks specifically created
technology to improve bus business online booking. This suggests that there is no interaction
of any sort between the bus company and the passengers. Most of the time, to reserve a place
for service, anyone desiring to buy tickets must select one of the following three possibilities:

23
  Visiting the bus company's location to conduct the necessary research before making
a reservation.

 Reaching out to the management of the bus company via a communication channel to
ask questions regarding the bus company and the booking process.

 Consultation with anyone who has experience with the Modern Coast Bus ticket
booking system or who has expertise of the bus firm is being conducted.

4.2.2 Problems associated with the current system:

The primary drawback of the existing system is the lengthy distance potential consumers
must go to use the Modern Coast Bus Ticket Booking System. Due to the time consumption
that results, an automated method would be beneficial. The limited amount of information
that may be provided while making a reservation over the phone may result in service
delivery issues. All of these are tiresome and time-consuming tasks. Another issue is that
clients are unable to evaluate the status of their projects unless they speak with the manager
personally, which takes time away from both sides.

Prospective clients might not always be aware of the bus company's specific location outside
of visiting it. The new system, which offers all pertinent information about the bus business,
including its location, contacts, and others, clearly resolves this issue.

4.3 SYSTEM REQUIREMENTS:

An automated system was necessary to be able to automate the manual procedure at

Modern Coast Bus Ticket Booking System. Users of this system can make reservations while
at distant locations. As a result, numerous conditions must be met to develop a system that
will enable this. They will be divided into three categories: functional, non-functional, and
domain requirements.

24
4.3.1 Functional requirements:

These conditions are necessary for the system to function. These criteria primarily focus
on what the system ought to do. They consist of:

 For access to the system's services, users must register by setting up accounts.
 Password authentication for users.
 Two database views are available on the system, and the super administrator has
greater rights than the other users. By using password and username validation and
verification, the system must validate people accessing data in the system. For these
functions, a login dialogue box will be utilized.
 The following user groups are permitted access to the system's data: I) The
Administrator, II) Clients Members will only be permitted to examine the database's
contents; the super Admin will oversee making changes to the database.

4.3.2 Non-functional requirements:

Through the provision of the system's quality attributes, these requirements concentrate
on how the system functions or should behave. These prerequisites consist of:

 The system needs to be capable of supporting an infinite number of users

simultaneously.
 Documentation: Before the system goes online, it will be documented, and users will
have access to PDF instructions.
 Recover-ability: The system will consistently be backed up in case data is lost for
whatever cause, allowing for its recovery.
 Design restrictions: MySQL will be used as the backend database for the app.
 Without internet, the system won't function.
 Only registered users will be required to log in to the system.

4.3.3 Domain requirements:

 This technology will not be able to function in locations without internet connectivity.

25
  The user must also have access to a computer or laptop, a smartphone, or any other
device with internet connectivity to utilize the system.
 These individuals with elementary computer skills will use the system.
 If persons without visual problems are not there to help, those with visual
impairments will not use the system.

4.3.4 Database requirements:

 It will be necessary to have a shared data store. This indicates that the new system
will need a database for information storage and retrieval in order to process and
provide feedback.
 To store the numerous entries that users will make into the system, the database will
need several tables.

4.4 SYSTEM MODELLING:

Users may better comprehend the data flow for the current system of operation at Modern
Coast Bus Ticket Booking System by using diagramming tools in this area. Given that the
system is manual, the data flow diagram is shown in Fig below.

UML DIAGRAM

USER:

26
Fig-1

27
ADMIN:

Fig-2

28
FLOW CHART:

Fig-3

29
ACTIVITY DIAGRAM:

Fig-4

30
DATA FLOW DIAGRAM:

Fig-5

31
 CHAPTER 5: SYSTEM DESIGN

5.1 INTRODUCTION:

This chapter's objective is to evaluate the mechanism that was suggested for the Modern
Coast Bus Ticket Booking mechanism by thoroughly detailing it. It also focuses on the
system's process design, which uses a variety of modelling methods to describe how the
system works.

The chapter also discusses the database design of the system with a focus on logical,
conceptual, and physical models. The chapter's last focus will be on the user-friendliness of
the newly proposed system's interface.

5.2 DESCRIPTION OF THE SYSTEM:

The proposed system will have a structure like the one discussed below.

5.2.1 Home page:

Any user who enters the site's address into a web browser will land on the system home
page. The main page includes general details such the title, welcome messages, the bus
business's fundamental principles, its mission, and a few pictures of the bus company.
Additional links include those to pages for log-in, registration, admin login, services offered,
about us, and contacts.

5.2.2 About us page:

This page provides comprehensive details about the Modern Coast Bus Ticket Booking
System, its areas of expertise, and the terms and circumstances of working with them. In
addition, the page offers the user links to register and log in for easier navigation.

32
5.2.3 Contacts us and addresses:

The bus company's location, its phone numbers, and its postal addresses are all shown on
the contacts page along with other pertinent contact information. Once more, the register and
log in links on this page point users to the proper pages.

5.2.4 Customer registration:

The user is required to fill out a form on this page to register for the Modern Coast Bus
Ticket Booking System. The following input fields are included on this form:

 Frist name
The user must specify his or her preferred first name.
 Last name
The user chooses a different last name than their first name.
 Username
A name is given by the user that will be used to log into the account.
 Email Address
The user must enter a working email address that can be used for communication.
 Contact
This is the user's phone number, which could be used to get in touch with the bus
company.
 Password
The user must enter this secret set of values for authentication, which may be a
combination of integers, alphabets, and other special characters.
 Confirm password.
It is necessary for the user to type the password again to verify that they understand
what they just typed as the password and to see whether they made a mistake.
 Register
This is a submit type of input that enables users to provide the server database their
registration information.

The link to log in is once more present on the website for easy navigation.

33
5.2.5 User log in:

For users who assert to have an account with the Modern Coast Bus Ticket Booking
System, this page serves as an authentication page. It provides a form with two input areas,
each of which has the following information:

 Username
The user must enter the username they submitted on the form to create their account
precisely as they did on that form. Any change will lead to a mistake.
 Password
During registration or account creation, the user was required to input and confirm
their password. The user is informed that the password is wrong if they use a different
one.
 Login:
The user must click this submit button to provide the database server their log-in
information. A log-in error will be generated if the database changes in any way.

5.2.6 Customer booking:

Here is a User’s are only able to book for the booking "space" period on this page if they
have registered with the Modern Coast Bus Ticket Booking System. It provides a booking
form that the user must complete. Consequently, the input fields consist of:

 Category The user selects the band, choir, or artist category for the musical
presentation.
 Presenter The individual making the reservation must specify the kind of music. For
instance, the Yatta lads
 Location The user must input their home address in the location area.
 Type of reservation the user must choose if the booking is audio, video, or audio-
visual from the list.
 Dates of booking the customer should choose the actual booking dates.

34
  Time-From-To This is the time frame within which the reservation will be made on
the scheduled date. It offers a time. Example: 10:00 – 11:00
 The bus company's nature must be determined from the two available alternatives
since the modern Coast bus ticket purchasing system might be fixed or mobile.
 Book The user must click the book button after entering the necessary information to
send the information to the database server.

5.2.7 Administrator log in:

Only the system administrator will use this page. The following input fields on a form
will be filled out by the user:

 Username
The admin must provide their username exactly as it appears in the administrator’s
table. Any change will lead to a mistake.

 Password
The admin is expected to enter the password as it is in the admin’s table in the
database.
Any variation in password will result in admins logging in error during submission.
 Login
The administrator must click this submit button to send the log-in information to the
server database table. A log-in error will be generated if the database changes in any
way.

5.2.8 Administrator update of the booking:

The admin gets access to the booking and registration information for customers when
they log in. All legitimate bus company reservations are activated by the administrator, who
then posts the progress of each reservation on the users' progress view page. The admin also
deletes inaccurate information.
35
5.2.9 Administrator update of payment:

In this, the administrator checks the payments by accepting or rejecting them. Any
fraudulent payments are removed.

5.3 SCREENSHOTS:

ADMIN LOGIN:

Fig-6 Admin Login

36
BOOKED LIST:

37
 Fig-7 List of Booked Passengers

LOCATION LIST:

Fig-8 List of Locations

38
BUS LIST:

Fig-9 List of Buses

39
USER LOGIN PAGE:

Fig-10 User login page

40
USER SIGNUP PAGE:

Fig-11 User Sign up page

41
FINDING SCHEDULE:

Fig-12 Find Bus

42
SCHEDULE:

Fig-13 Schedule page

43
SEAT AVAILABILITY:

Fig-14 Availability check

44
BOOKING CONFIRMATION:

Fig-15 Confirmation page

45
 CHAPTER 6: SYSTEM IMPLEMENTATION

6.1 INTRODUCTION:

The newly created system is discussed in this chapter before it is integrated into the
business's operations. Consequently, I will look at the software used to code the system, as
well as the system test plan and actual testing, before outlining an appropriate changeover
strategy that the company should follow to put the system into use.

6.2 TOOLS USED FOR CODING AND TESTING:

The following tools were crucial for the project throughout the coding of the full system.

6.2.1 Coding tools:

Editing:

I used the Dreamweaver program to edit the code while it was being written in the various
languages covered below.

Programming languages:

I employed the following web programming languages for creating the code:

 PHP:
Hypertext Pre-Processor is referred to as PHP. It is an extremely potent programming
language that can be utilized for both online and mobile application development.
Most of the functional needs of the system, including variable definitions and query
declarations, were implemented using PHP as my primary programming language.

 Html5:
Html, or Hypertext Mark-up Language, stands for. I mostly utilized HTML to format
and display text codes in these writings.

46
  CSS:
Cascading Style Sheets, or CSS. This language is quite effective for formatting web
pages and has been incredibly helpful to me with my project. It helped me arrange the
user interface in a way that would appeal to more users.

 Java scripts:
Java scripts were quite important in the addition of several functionalities to my
system. These featured sliding images, which are much more obvious on the system
homepage.

 SQL:
It stands for structured query language as an acronym. I connected the PHP code to
the database and ran the various queries using SQL as the programming language.

6.2.2 Testing tools performance test:

This test assesses the effectiveness of the system under development to determine
whether it is resolving the desired issue. The tests that will be run on this system are listed
below.

 Unit testing:
This necessitates testing of the separate components that make up the complete
system. Since each unit was examined separately, this testing strategy was intended to
aid in the identification of errors.

 Stress testing:
This testing technique constantly examines how a system responds to unique
circumstances. I tested the system with erroneous input data, such as blank input
fields, and it was unable to continue the execution.

47
  Actual system testing:
After the system has been fully developed, this is done to the entire system to test
how it functions in general. This system will be put through this test to see if the
earlier-stated goals have been met or not.

 Functional testing:
Using input and output data, the program's features are tested. This will be done to
test the operation of the program's many functions, and any unexpected behavior will
be found and fixed appropriately.

6.3 SYSTEM TEST PLAN:

The system was tested in every way possible, with different data inputs such as integers
(INT), variable characters (VARCHAR), Date Time, and others being utilized, and the
outcomes being seen.

6.4 USER ACCEPTANCE TESTING:

Any incorrect data input during testing changed the anticipated outcomes, and the system
validation features might notify the user of any incorrect inputs. For feedback and acceptance
testing, the system was also made available to potential users. I received a favorable reaction
from these users, who accepted the system as a replacement for labor-intensive manual
processes in Modern Coast Bus Booking System manufacturing. After the development
process was complete, acceptance testing was carried out. Users were given the system for
their feedback, and once they approved it, the system was said to have complied with their
needs. This system underwent user acceptability testing at a later stage of development to
provide prospective users and clients with a chance to provide feedback.

48
6.5 PROPOSED CHANGE-OVER TECHNIQUES:

There are typically four methods for implementing the system in an organization. These
are the parallel approach, phased approach, pilot approach, and direct changeover. I carefully
considered the four system implementation strategies before deciding on the phased
operation.

Phased changeover

Operation in phases takes place in many stages. The new system must typically be
implemented in modules. It combines both the parallel method and the direct transition.
Since the system is new and the number of users is uncertain currently, I plan to implement it
this way. It would be important to take it and implement it module by module until the last
module of the system proves to be effective and well-operational as required. The possibility
of faults or failures in this system may have also motivated me to utilize it because those
risks will only apply to a certain module or a few of the modules that have already been built,
rather than the entire system. Like its usage, its implementation costs may be less than those
of other ways, such as the direct approach, which demands the simultaneous implementation
of the entire system. Phased operation operates in many stages or phases. Phased operation is
the implementation of a new system in modules or phases. This also combines direct
changeover and parallel operation, much like a pilot operation. However, in this method,
some users receive the entire system as opposed to all users, who only receive a portion of it.

Phased operation is less costly than complete parallel operation, and the risk of mistakes or
failures is restricted to the implemented module alone. However, in some circumstances
where the system entails many distinct phases, the phased operation can be more expensive
than a pilot approach. When the development process is complete, the system is given to the
users for feedback, and once they accept it, the system is said to have satisfied the user's
requirements. Later stages of development will include user acceptance testing for this
system to give prospective users and clients a chance to provide feedback.

49
 CHAPTER 7: CONCLUSIONS AND RECOMMENDATIONS

7.1 RECOMMENDATIONS:

I would like to suggest the following to mitigate the project's risks and challenges and
achieve improvements in future developments.

7.1.1 Reduction in strictness of the Time deadlines:

Since some of the problems with this system involve brand-new ideas, I would advise
allowing the students to start working on their projects early so they can develop their ideas
and finish ahead of schedule and adhere to the requirements.

7.1.2 Provision of project finances to the students:

I would suggest that some special funding be provided to act as the support for the
students who encounter challenges during the creation and research process because some of
the students are unable to meet the threshold necessary for data and requirement collecting.

7.1.3 Compelling some institutions to pave way for the students to develop:

Higher-level institutions should compel those institutions that have been a significant
bottleneck in the development of projects to release and reduce the constraints they have over
their intellectual property, such as API (Application Programming Interface).

50
7.1.4 Future improvements:

Since my system did not capture everything that was necessary, I would like to suggest
the following areas for future development:

 A feature that enables system administrators to communicate with customers.

 Features that let customers offer comments and feedback.

 Integrating M-pesa with the system to allow users to pay through the system.

7.2 CONCLUSION:

There are no doubt bus company services are the only ones covered by the current
reservation systems; the mobile bus company service feature is not available. As a result, this
is more expensive for the customers than having the bus business come to them, which
occasionally includes a band or a 20-person singing group. Therefore, the suggested system
offers a module to choose the bus company's nature, such as mobile or fixed, and these aids
the clients in placing an order for the bus company to visit them. This will cut out wasteful
spending and time.

With the new suggested system, the issues with the present system will be resolved. The
issues with the manual approach are effectively solved by this design since the suggested
solution is a clear automation of the present Modern Coast Bus Ticket Booking approach
system. Additionally, the new system has been created with a user-friendly graphical user
interface that will make the entire booking process simpler. Despite a few difficulties, the
implementation process was a success because I was able to develop a system that not only
worked but also received positive user feedback. It was a tremendous experience for me to
see this project through, and without the practical experience I gained, this would not have
51
happened. This is a crucial component of my education that has aided in my comprehension
of the ideas underlying several web scripting languages as well as my familiarization with the
course's general market expectations.

52