Online Bus Ticket Reservation System For Abay Bus Transport
Online Bus Ticket Reservation System For Abay Bus Transport
Online Bus Ticket Reservation System For Abay Bus Transport
ADVISOR: ------------------------
MAY, 2021
Bahir Dar University, Bahir Dar Institute of Technology
DECLARATION
We declare that this project is our original work and has not been presented for a degree in any
other university.
This project has been submitted for examination with my approval as university advisor.
First and foremost, we would like to thanks our Almighty GOD for giving all the capabilities
to do things and helped us from the start to the end. Next to GOD We wish to express our
sincere gratitude to the Faculty Of Computing, for providing as an opportunity to perform our
project work on “Online Bus Ticket Reservation System For Abay Bus Transport” .We
sincerely thank our project Advisor, Mr.------------------ for his diligence in advising and
guiding us to through the right path, from the inception until the completion of this document.
Additionally we would to thanks for our entire friend for sharing many useful ideas. Finally,
we have also a great pleasure for employees of Abay Bus Station especially Mr. ________
and Mr. ------------------- for spending their precious time with us and giving us the
information we were searching for.
1
ABSTRACT
The project which is the team aim to build is an online bus reservation system for Abay Bus
Transport P.L.C which is a web based application that allows customer to check availability
of ticket online at any time at any place and enable there customer to reserve a seat online
without going to the office physically. After the finishing of this project the company will get
many advantages such as it will provide a good service to their customer this will lead the
company to be profitable and it makes the data handling of the company organized. In recent
year all projects are done by using an object oriented method because of its convince to build
a good and reliable system so we choose this method for our project to be successful. As we
used object oriented system development methodology under this methodology there are
three development methodologies from those iterative system development methodology is
convenient to do our project successfully.
2
Table of Contents
ACKNOWLEDGMENT......................................................................................................................... 1
ABSTRACT............................................................................................................................................ 2
ACRONYMS .......................................................................................................................................... 5
LIST OF TABLES .................................................................................................................................. 6
LIST OF FIGURE................................................................................................................................... 7
CHAPTER ONE ..................................................................................................................................... 2
INTRODUCTION .................................................................................................................................. 2
1.1 BACKGROUND .......................................................................................................................... 2
1.2 STATEMENT OF PROBLEM ..................................................................................................... 3
1.3 LITERATURE REVIEW ............................................................................................................. 3
1.4 OBJECTIVE ................................................................................................................................. 4
1.4.1 General Objective ...................................................................................................................... 4
1.4.2 Specific Objective ...................................................................................................................... 4
1.5 MATERIALS AND METHODS .................................................................................................. 5
1.5.1 Site of the study ......................................................................................................................... 5
1.5.2 Method of data collection .......................................................................................................... 5
1.5.3 System Implementation Tools ................................................................................................... 5
1.5.3 Tools or instrument .................................................................................................................... 6
1.5.4 Development methodology ........................................................................................................ 6
1.6 SIGNIFICANCE OF PROJECT ................................................................................................... 7
1.7 SCOPE AND LIMITATION ........................................................................................................ 8
CHAPTER TWO .................................................................................................................................... 9
SYSTEM REQUIRMENT SPECIFICATION ....................................................................................... 9
2.1 INTRODUCTION ........................................................................................................................ 9
2.2 CURRENT SYSTEM ................................................................................................................... 9
2.2.1 Overview .................................................................................................................................... 9
2.2.2 Problems Of Current System ................................................................................................... 10
2.3 PROPOSED SYSTEM ............................................................................................................... 10
2.3.1 Overview .................................................................................................................................. 10
2.3.2Goals Of Proposed System ....................................................................................................... 10
2.3.3 Functional Requirements ......................................................................................................... 11
2.3.4 Non Functional Requirements ................................................................................................. 12
2.3.4 Constraints ............................................................................................................................... 13
3
2.3 SCENARIOS .............................................................................................................................. 13
2.4 SYSTEM MODELS ................................................................................................................... 15
2.4.2 Use case model ........................................................................................................................ 15
2.5.3 Object model ............................................................................................................................ 27
2.5.4 Dynamic model ........................................................................................................................ 31
REFERENCE ........................................................................................................................................ 41
4
ACRONYMS
ADMIN: Administrator
5
LIST OF TABLES
Table 1: Scope of the project…………………………………………………………………..8
Table 6: List of Actors and Use Cases associated with the new system………………….…17
Table 10: use case description for check ticket availability use case………………………..22
Table 11: use case description for ticket cancelation use case……………………………….23
Table 12: use case description for view schedule use case………………….……………….24
Table 13: use case description for generate report use case………………………………….25
Table 14: use case description for add route use case…………………………….…………25
Table 15: use case diagram for delete route use case………………………………………..26
Table 17: use case description for assign bus to the journey……………………………….28
6
LIST OF FIGURE
Figure 1: use case diagram………………………………………………………………18
7
CHAPTER ONE
INTRODUCTION
As there are many problems face human being throughout their life it is obvious to solve
many of the problems using computers. When saying this as the computer is the modern
technology problem solver any one can solve his/her problem by developing the software that
make its work computerized. So we have prepared a project as a precondition for solving
many of the problems of Abay bus ticket System that is implemented manually. Therefore,
this work that manually performed needs to be automated to reduce the problem happened.
The project includes the background of the company and also the systems performed are
described. In addition, the conditions like the problems in the company, our objective, scope
of the project and cost are clearly specified.
Finally, the tools and techniques we will use and the schedule is summarized as possible as to
finish in the given time by using own methodologies.
1.1 BACKGROUND
Abay Bus Transport P.L.C Company was established in 2006 by Amhara Development
Association (ADA) to address the nation-wide need for public transportation. The company
launched operating reliable bus transport services with a Abay Bus uses modern chinise Yutong
bus and other model to deliver it's services to their customers. All of their buses are fitted with Air
Conditioner as well as they have enough legroom for your comfort.. Abay Bus Transport P.L.C
was legally constituted on Tir 29, 2006 E.C with Registration No. 0014/87 Abay Bus
Transport P.L.C buses are luxurious tourist buses with a capacity of 51 seats which are
equipped with Air conditioner, fridge, monitor, & safety belt so that passengers are
entertained by DVD/VCD music/film, Cake & soft drink or plastic packed water/Juice while
travelling.[1]At present the company is rendering service from Addis to Bahir dar , Debre
markos, Fenote Selam , Koso Ber, Gonder, Debre Tabor,Debre Birhan, Dessie&weldeya on
daily basis. The headquarter, bus terminal and garage of Abay Bus has been established in
Addis Ababa and Bahir Dar with branch offices in all capitals. Buses departing from Addis
Ababa to all the capitals providing all necessary information and entertainment services to the
satisfaction of the passengers are expected to serve as the ambassadors of the region.[2]
2
1.2 STATEMENT OF PROBLEM
Abay bus Transportation Company uses manual system which requires a lot of resource like,
man power, stationary materials and so forth. And also the system is slow and inaccessible to
their customer.
From the point of view of customer the current system is very wasteful which require a lot of
time and money. For example if a person wants to reserve a place in the bus he must go to the
office his/her time and money are lost.
The team attempt to review different researchers which wrote about online bus ticket
reservation system so we described below:
Wee kim li in his project, which is done in 2007, define Bus Ticket Reservation System is
company online system, which enable Customer to check availability bus ticket buys bus
ticket, and pay bus ticket online. It makes the customer easy to get bus ticket online instead of
queue up to buy the bus ticket.[3]
Hasanhuseyinkoyunand Ayseorhan in there project which is done in June 2012 conclude that
about bus reservation system Designing a web site is making passengers convenient.
Passengers do not have to search the area when they went to travel, business. They will reach
directly to company online. Information of bus and availability of a seat of all about your
business can be reachable everywhere. Passengers find your information when they need
where there is an internet connection. In web sites, there is communication information, so if
the passengers want to quick help they can reach easily, they can go wherever they want
immediately. Designing a web site can save money on printing and postage costs for
brochures, coupons, flyers, specials, newsletters and other mailings. You do not have to write
it down route, bus services, departure date, departure time all the information can be entered
on the website.[3]
The main activity of a bus reservation system is reserving a seat for passengers who:
3
Duygukandemir and Hasankarpuzciin there project which is done in December 2012 online
bus ticket reservation system is a strong system that used to make reservation easier, faster
and safer which is useful to make passengers happy and do not make companies embarrassed
against customer.[4]
Most projects try to solve the problems happen that are related with manual ticket system by
making all work computerized but in our case we are not intend to make the whole system
computerized because in our case there is no money transaction which is online money
transfer.
1.4 OBJECTIVE
To develop online reservation system that will replace the manual ticketing system.
In addition to general objective the project will also contains the following specific
Objective:-
4
1.5 MATERIALS AND METHODS
The method of Requirement gathering that is used on this project includes phone interviews
and document analysis to collect/ gather information and data of the existing system to
develop new system.
Phone interview: we contact the organization and then exchange some ideas about their
current system, how it has been working and the structure of this organization. As a general,
we gather enough data in order to prepare our project.
Server side scripting: hypertext pre-processor (Php), we have select Php for server side
scripting because it has the following advantages;
Familiarity many of the language constructs are borrowed from C and Perl and in many cases
Php code is almost indistinguishable from that found in the typical C or Perl program. Php
has resource allocation machines and it can support object-oriented programming.
Although Php is compatible with wide Varity of web server we are used apache Server.
Database: Structured query language (MYSQL) rises to become one of the most popular
database servers in the world. This popularity is because of the servers speed, robustness and
flexible. MYSQL has arguable become Php most popular database counterpart.
Static webpage: hypertext mark-up language (html) is highly flexible with cascading style
sheet (CSS).
5
1.5.3 Tools or instrument
In the process of developing the system we use different hardware tools and software tools.
Hardware tools
Laptop or desktop
Cd
Flash disk
Software tools
The team will follow Object Oriented System Development methodology (OOSD). Object
oriented methodology define system as a collection of interacting objects.
6
The modeling method the team plan to use is unified modeling language (UML) which used
to Model the functions of the system (use case modeling), Find and identify the business
objects, organize the objects and identify the relationship between them and finally model the
behavior of the objects.
The team use iterative system development methodology because of its flexibility which
means through the process of developing the system if error is occur we can back to the
previous phase and correct the problem.
7
1.7 SCOPE AND LIMITATION
In this section the team identify the scope and limitation the project so the following table
shows the scope and limitations of the project.
8
CHAPTER TWO
2.1 INTRODUCTION
System analysis involves the study of an application area to fully understand the problem
being posed. Activities are focused on developing a comprehensive knowledge of the existing
system, its strengths and weaknesses and the reasons for the need to restructure, replace, or
automate the existing system.[5]So in this chapter the team discuss about current system,
proposed system and at last system model.
2.2.1 Overview
Currently Abay Bus Transport P.L.C uses a manual ticketing system which is a passenger
can reserve ticket by going to the ticket office physically and after waiting a long queue the
ticket attendant asks question. These questions are listed below:
After the question is completely answered the ticket attendant gives the ticket to the
passenger. Currently company store passenger information’s inform paper file which is put in
the shelf.
9
2.2.2 Problems Of Current System
As we mentioned in section 1.3 the current system has several problems which is described
below:
The details information of the passenger is traditionally paper based and maintained
on paper.
Finding out details regarding any information is very difficult because information
in paper based form.
Existing system require great amount of manual work has to be done. The amount
of manual work increases rapidly with increase in bus services.
Needs a lot of working staff and extra attention on all the records.
It is time consuming.
It is wasteful which means it require a lot of cost.
It causes data loss because there is no proper handling of data.
It is not easily accessible.
The passengers must wait for their required bus without reserving
2.3.1 Overview
The proposed system is a web based application which provides information regarding the
bus timings as per request of the user. The user enquires bus services from a particular
source, specifying the date and time and details about the available buses can be viewed in a
time sorted fashion. Also provides the facility to reserve tickets by online. If the reservation is
successful, the server will send back a reservation code to the customer.
The modern computerized system is developed with the aim to overcome the drawbacks of
manual system. The proposed system has got many advantages. People from different parts
of the region can register very easily. The new system is more personalized which means a
passenger require to a user account to access the fruit of the system. We do this to secure the
system from unauthorized act of the system users.
10
The goal of the proposed system is to provide the organization a new system that provides all
the functionalities specified by the organization except automating payment system. The
administrator has options for adding items in to bus details, assigning bus, updating schedule
and adding route. Security features are also enhanced in the system by protecting
unauthorized use of the system through denying system service to those who don’t have user
account. The goals proposed system are listed below:
Functional requirements are statement of services the system should provide, how the system
should react to particular inputs and how the system should behave in particular situation.
Below is the functional requirements of the system are listed:
The system enables Administrator to add, update, routes and dates of bus.
The system allows passenger register to become a member of the system.
The system allows a registered user to reserve tickets online.
The system allows cancelling the reserved ticket.
The system allows checking the availability of bus in the required route easily.
The system should store all information of the passenger and every bus.
The system allow user to see bus departure and arrival of every bus.
The new system should be able to detect input syntax errors such as input of
characters where numbers are expected. The system should ignore the faults inputs
and generate error message
11
2.3.4 Non Functional Requirements
Non-Functional requirements describe user visible aspects of the system that are not directly
related with the functional behavior of the system. But it can support and give more quality
for the new system
The Online Abay Bus Ticket Reservation system shall be designed as a web based that has a
main user interface. Format of main screen shall be standard and flexible. The system should
be user friendly designed.
Pages shall be connected each other in a consistent way. Operations can be done with the
system shall be repeatable.
The system should provide an easy-to-use graphical interface so user can easily learn
how they use the system. So, little knowledge on how Web pages can be accessed is
required for user to use.
The system should be user friendly so that users can use it easily without confusion.
The web interface should be intuitive and easily navigable Users should be able to
understand the menu and options provided by the system
To use the system a user must first register to system and log in to the system but if
unregistered user try to reserve without having registering the system doesn’t allow the user
to use the system.
The authorization mechanism of the system will block the unwanted attempts to the server
and also let the system decide on which privileges may the user have. The system has
different types of users so there are different levels of authorization.
12
2.3.4.4 Performance requirement
Response time of the System should be minimum. The system should show no visible
deterioration in response time as the number of users or reservation data increases.
The system does not taking up too much space in memory to store system’s data.
The OBTRS is a web based application so anyone can use the service from any place if
his/her computer has internet connection. So the system must be able to communicate users
from any place.
2.3.4 Constraints
Time constraint:-The time allotted for the project was not enough to complete the
project.
2.3 SCENARIOS
In section the team discuss in detail about scenarios which is a concrete, focused, informal
description of a single feature of the system from the viewpoint of a single actor. The team
identifies scenarios based on the scenario identification criteria’s. These identified scenarios
presented below:
13
1) Making reservation
Table 3: scenario for making reservation
Scenario name Making reservation
Participating instance Passenger
Flow of event 1. If the passenger want to make
reservation, open the OBTRS and
activate reservation function from
the system.
2. The passengers enter the departure
city and destination city and
submit the input and waits the
response.
3. The system processes the input
information and gives back the
reservation id and other important
information.
4. Passenger receive the confirmation
of his/her reservation.
2) Adding route
Table 4: scenario for adding route
Scenario name Adding route
Participating instance Administrator
Flow of event 1. If administrator want to add route
to system open system and activate
the add route function.
2. Administrator fills the required
information then submits input
information and wait the response.
3. The system processes the input
information and then gives back
the message successful addition of
route to the system.
14
4. Administrator receives the result.
3) Updating schedule
Table 5: scenario for updating schedule
Scenario name Updating schedule
Participating instance Ticket clerk
Flow of event 1. If the ticket clerks want to update
the schedule of the journey, open
the system and activate the update
schedule function.
2. Ticket clerk fill the required
information and then submit the
input and wait the response.
3. The system process the input
information and then gives back
the message successful addition of
route to the system.
4. Ticket clerk receive the result.
In this section we will discuss about scenarios of the system, use casemodelling, object model
and dynamic model of the new system.
The use case modeling first step is to identify Actors and use cases associated with the
system. The following table specifies the actors and use cases that a group member have
identified with in the proposed new system.
Table 6: List of Actors and Use Cases associated with the new system.
15
Actor Use case
Administrator Log in
Generate report
Add/ Delete/View route
Add/Delete bus
Register ticket clerk
Add/Delete news
View comment
Ticket clerk Log in
Add/Delete/Update schedule
Make/Delete/View reservation
Add/Delete driver
View route and registered passenger
Passenger Register
Log in
Reserve ticket
Check availability of ticket
Cancel ticket
View schedule
16
The second step is to construct the use case model which graphically depicts the interaction
of the system with the external environment. The following figure specifies the use case
model of the system.
The third step is to document each of the above use case courses of events to determine the
requirement use cases as described in the following section. So the following consecutive
tables show the use case documentation for each of the use cases that has identified in the
above use case diagram. Each table contains the use case name, the actor which initiates and
interacts with the use case, description of the use case and typical course of events that show
the interaction between the actor and the use case which enable the team to easily depict the
functions of the proposed system.
17
1) Register
18
2) Log in
19
3) Reserve ticket
20
AC3
If ticket is not available the system
does not allow reservation.
Special requirement A ticket must avilable
4) Cancel ticket
Table 10: use case description for ticket cancelation use case
21
Special requirements A passenger must reserve ticket
Table 11:use case description for check ticket availability use case
22
6) View schedule
Table 12: use case description for view schedule use case
23
7) Generate report.
Table 13: use case description for generate report use case
8) Add route
Table 14: use case description for add route use case.
24
Basic course of action 1. Admin launches the system.
2. The system displays the homepage.
3. Admin log in to the system.
4. Admin browses’ the add route page
5. The system displays the requested
page.
6. Admin fills the required data then
submit the form.
7. The system displays message
successfully compilation of use case.
8. End of use case.
Alternative course of action AC1:
If admin fill incorrect data the system
display error message and the add
route form.
Special requirements
9) Delete route
Table 15: use case diagram for delete route use case
25
6. Admin fills the required data then
submit the form.
7. The system displays message
successfully compilation of use case.
8. End of use case.
Alternative course of action AC1:
If admin fill incorrect data the system
display error message and the delete
route form.
26
If admin fill incorrect data in to the
update schedule form the system will
display error message and the update
information page.
In this section the team discuss all about the object modeling of the system which include
identifying class which the system constitute and drawing their relationship using class
diagram.
1. Passenger
Table 18: data dictionary for passenger
Field name Data type Field size Constraint Description
Fname Char 25 Not null The first name of passenger
Lname Char 25 Not null The last name of passenger
Username Varchar 20 Primary Username of passenger
key
Password Varchar 20 Not null Password of passenger
Phone Number Int 20 Not null Mobile or home phone
number of the passenger
Address Char 30 Not null Address of the passenger
Age Date/time - Not null Date of birth of the
passenger
2. Administrator
Table 19: data dictionary for journey
27
3. Reservation
Table 20: data dictionary for reservation
4. Route
Table 21: data dictionary for route
5. Schedule
Table 22: data dictionary for schedule
28
6. Bus
Table 23: data dictionary for bus
7. Account
Table 24: data dictionary for account
29
2.5.3.2 Class diagram
30
2.5.4 Dynamic model
Dynamic model is represented by sequence diagram, state chart diagram and activity diagram
so in the preceding section we briefly discuss about these diagrams.
The following figure shows the high level sequence diagram of the system. The figure shows
the high level interaction of the actors with the system that specifies the work flow the
system.
31
Sequence diagram for update schedule
32
Sequence diagram for add route
33
Sequence diagram for Reservation
34
In this part the team used to model the behaviors of the objects by drawing the state diagram.
The state diagram depicts the state of objects as their attributes change from one state to the
other state. So the following diagrams is state chart diagram:
35
Activity diagram for log in use case
36
Figure 9: Activity diagram for reservation
37
Figure 10: activity diagram for view schedule
38
launch system access hompage log in
access system
Valid entry
39
Figure 12: activity diagram for update schedule
40
REFERENCE
[1] http://www.Abaybus.com/companyprofile.html
[2]http://www.Abaybus.com/companyprofile.html
[3]http://xa.yimg.com/kq/groups/27443320/1842024007/name/Bus.pdf
[4]http://www.Abaybus.com
41