WACHEMO UNIVERSITY

ENGINEERING AND TECHNOLOGY

FACULITY
SCHOOL OF COMPUTING AND
INFORMATICS
DEPARTMENT OF INFORMATION
TECHNOLOGY

SYSTEM ANALYSIS AND

DESIGN PROJECT

PROJECT TITLE
ONLINE GEDA BUS
RESERVATION SYSTEM

SAD PROJECT
 GROUP 7&8
GROUP MEMBERS ID

1. EYOB DESTA…………................ 000786

2. MEKUANINT TEKLE…………….004863
3. MULUNEH ANILE….……………. 004656
4. DEREJE TEREFE…….………….. 004866
5. AGERU GEREMEW….………….. 004657
6.
7.
8.
9.
10.

Contents
Phase One: …………………………………………………..… 3
1.1 Background of Geda Bus ……………………………………… 4
1.2 Statement of problem …………………………………………… 4
1.3 Objective (general and specific) ………………………………4
1.4 Methodology ……………………………………………………….. 5
1.5 Feasibility …………………………………………………………….6
1.6 Project scope ………………………………………………………. 8
1.7 Importance of the project ………………………………………9

Phase Two: ……………………………………………………… 9

2.1 Over all description …………………………………………….. 9

2.2 Product perspective …………………………………………….. 9
2.2.1 System user interface ……………………………………….. 10
2.2.2 User interfaces ………………………………………………. 10
2.3 Product functions ………………………………………………10
2.3.1 User characteristics …………………………………………11
2.3.2 Specific requirements ………………………………………11
2.3.3 External interface requirements ………………………11
2.3.4 Functional requirements ……………………………..….11
2.3.5 Functions ………………………………………………………12
2.3.5.1 System features ……………………………………………12
2.3.5.2 Non – functional requirements …………………….12

ACKNOWLEDGMENT
Unlimited praise for God as the number of his creatures, the gratification of himself, the weight
of throne, and extension of his word.

I would like to express my deepest gratitude to my supervisor instructor Eyobed.B his

excellent guidance , caring , patience , providing me with an excellent atmosphere for doing
research , confidence in me . His comment and questions were very beneficial in completion of
this project. To you sir, I give you lots of thanks and respects.

Also I would like to thanks my group members for their continuous support and assistant
for their cooperative, indirect, or directly contribution in finishing this project.

ABSTRACT
Online Bus Ticket Reservation system is web based application that works within a centralized
network. this project presents a review on the software ‘’online bus ticket reservation system’’ as
should be used in a bus transportation system , a facility which is used to reserve seat ,
cancellation of reservation and different types of route enquiries used on securing quick
reservations . OBTRS is built for managing and computerizing the traditional database, ticket
booking and tracking bus and travel made. It maintains all customer details, bus details,
reservation details.

1.0 phase one

INTRODUCTION
 1. 1 background
Geda Bus transport system is an intercity coach company based in Addis Ababa, Ethiopia. It is
organized in 2009 according to E.C. Which is owned by Share Company registered with the
Federal Ministry of Trade and Industry under the Ethiopian commercial code. Headquartered in
Addis Ababa, Bole Area, friendship building. It can hold 1,000 shareholders and started by
having different branches like Nekemt, Jimma, Bale Robe, Gonder, Bahir Dar, Jima, Hawassa,
Dire Dawa, and Jijiga. Our project is to computerize ticketing system, so that the service
becomes fast. It replaces all the paper work it keeps records of all bills also, giving to ensure
100% successful implementation of the computerized Geda bus reservation system. Our
reservation system has four (4) modules those are:-

First module helps the customer to enquire the availability of seats in a particular sky bus at a
particular date.

Second module helps him/her to reserve a ticket.

Third module he/she can cancel a reserved ticket.

And in the fourth module, the customer will be able to forward his/her comment.

1.2. Statement of the problem

In Geda bus transportation system, manual system require a lot of resource like, man power ,
paper, pen and so forth. In this system, a lot of data might be occurred. For example, passenger
may loss his or her ticket also technical problems may occurs.

Currently, the type of system being used at the counter is an internal system which is manually
used in selling the bus tickets. The problems facing the Company are that Customers have to go
to the counter to buy bus ticket or ask for bus schedule ,customers will also have to queue up for
a long time in order to secure a bus ticket a will also need pay cash when they buy the bus ticket.

1.3. Objective
1.3.1 General objective
The main purpose of this project is to automate the manual procedures of reserving a bus ticket
for any journey made through Geda Bus Transport Company (GBTC).This System is said to be
an automatic system and customers can select seats by themselves.

To develop online reservation and ticketing system that have been replaced the manual ticketing
system and offering, comfortable, and cost effective travel solution to the customer.

1.3.2 Specific objectives

 Providing a web based bus ticket reservation function where a customer can buy bus
ticket through the online system without a need to queue up at the counter to purchase a
bus ticket.
 To analysis the existing business process of ticketing and reservation system.
 To propose a new business process that has been automated.
 To implement the new developed system and increase the customer satisfaction.
 To analysis the implement process of increase customer expectation in effective and
efficient manner.
 Enabling customers to check the availability and types of busses online.
 Ability of customers to cancel their reservation.

 Manage reservations and seating effectively.

 Safe and secure payment gateway module.
 Detail reports for managing trips.
 Save time spent by standing in queue for purchase of you.
 Pay online using online payment facility.
 Take a ticket printout.
 Counter booking using online application.
 Generate detailed report of sales details.
 Manage various trips, rates and types.
 Allow users to reserve seats online.
 Allow user to pay for tickets online by integrating system with EBS and benefiting of
their services.

1.4. Methodology
In our views we are providing to or the aim is to change the current system to more applicable
one to give more services for the customers easily.
We decided to use object oriented because of the following reasons.

 It would facilitate code re use since it implements the concepts of object oriented method
like, inheritance, encapsulation and polymorphism. From development method, we use
prototyping and from testing method we use integration and system testing.

1.4.1. Method of Data Collection

For the first time we have met the organization of the Geda bus transportation system, we used
data collection method like interview and observation.

A ) Interview: AS an interview, we have contacted the manager and employers

of that organization and then exchanged some ideas of this system how it have been working and
the structure of this organization have in its implementation also the aim of they have to change
the current or manual system to an online system. As a general, we gathered so many data in
order to prepare our project by interviewing them.

b) Observation: At the time we have gone there, we have visited that

organization by moving here and there by which techniques this organization use to succeed its
function

c) Existing documents: To get more information about the project

we use earlier documents that help us to develop the project. During the analysis of documents,
we give a special consideration to those documents which can bring more features to the project.

1.5. Feasibility Assessment

1.5. 1.Technical Feasibility
Because of projects were going to expected greater return on their development, technical
risks were valuable tool to understand the sources and types of risks as well as their
management.
 Risk Name Risk Management

-Failure to attain expected benefits from -Reviewing /Feedback mechanism of the

the project project procurers

-Inaccurate project cost estimates -Allocating budgets for each task

-Inaccurate project duration estimates -Breaking tasks into section

-Failure to achieve adequately system -Applying new/modified procedure

performance levels.
-Failure to integrate with the existing -Using the version of them
hardware, or software

1.5.2. Schedule Feasibility

The project is intended to be with in fixed time interval. Unless and otherwise we may fall in
difficulty in cost estimation and as well as we may fall in the financial problem.

1.5.2.1. GANT CHART

2011(Mar-Jun)
No. Task Name P3,2011 Dec1,2012 Dec20,2012 Jan10,2012 Mar26, 2012 May
25,2012
1 Project
Description
2 Proposal
 submission
3 SRS

4 Design
Document
5 Implementation
Document
6 Operation
testing

 Gantt chart is more effective when we are seeking communication schedule.

Legend: Shows Task completed

Shows Task incomplete

1.5.3Economic Feasibility:
Since the system is being automated to avoid extreme problems of customer in canceling tickets,
this in turn helps them to increase their satisfaction than they get can before. For the project we
are working on, we have the following benefits and costs.

1.5.3.1. Benefits:
A) Tangible Benefits:
The main advantage of this project was going to be computerized in order to reduce
resources used for manual operation and it will save time that can be spent during manual
system.
B) Intangible Benefits:

The intangible benefits we have pointed out in the system development are:

 Increased speed of activity,

 Increased flexibility,
 Increased customer morale, and
 More timely information.
1.5.4 Operational Feasibility
It is a measure of how well a proposed system solves the problems and takes advantage of the
opportunities identified during scope definition and how it satisfies the requirements identified in
the requirements analysis phase of system development. Process-in an online ticketing system,
first the passengers data should be gathered like address, name, depart time, depart date, from
location, to location and etc. Evaluation –by comparing the previous system, the new online
ticketing system can satisfy all the customers need?

Implementation- to implement an online ticketing system, we need to know the

hardware recourses we have also customers suggestions.
Résistance – try to omit or avoid systems that make customers ambiguous or confuse.
Strategies – here, our aim of developing these systems rather than the previous is to
make all customers applicable or fully satisfied with it.
Adapt and review- developing the system in a simple way with which every customers
can understand that can have instructions and so he/she can register on it within a short
time.

1.6 Management Issue

1.6.1 Team Configuration and
Management
In our project, we have five (5) members where each of us has specified work and also the
project is supervised by one of our members.

The following are the types of tasks and as well as the responsibility each of us can have.

Task Name Group Name

Project manager Eyob Desta and Mekuanint Tekle

System Requirement And specification (SRS) Zewude Mengesha and Dereje Terefe
Analysis and Design Muluneh Aniley,Amanuel Degel and
Seblewongel Oycha
Implementation And Testing Ayantu Gamora,Seid Hassen,Ageru Geremew
and

Project manager:
Eyob Desta and Mekuanint Tekle manage our project in such a way that he arranges all
important tasks for each of us.

System and requirement specification

The person responsible for this task gathers all resources by which we can do this project
(Zewude Mengesha and Dereje Terefe).

Analysis and Design:

Here, the accountability of this person was to analyze and design the project as it properly met
user need (Muluneh Aniley,Amanuel Degel and Seblewongel Oycha)

Implementation and Testing

This task is done by Ayantu Gamora ,Seid Hassen and Ageru Geremew to bring the project to an
end and so that will be tested.

1.6.2 COMMUNICATION PLAN

While we are working on our project, we use the following techniques in order to meet one
another and then exchange our suggestions or ideas. Those techniques are listed in the following
table.

Number Techniques
1 E-mail account
2 Mobile phone
3 Schedule(time table)
 1.7. Scope
The scope of Online Geda Bus Tour and Travel Ticket Reservation system is the boundary that
we are performing online tasks in the Reservation system.

A Customer should be able to:

1. Registered to the system through the first page of the application.

2. See his/her current reservations on different Geda buses along with the details. View
current travel plans of the Geda bus transport systems
3. Make reservation.
4. Withdraw reservation.
5. Able to choose the seats
6. A message should be sent to the concerned person about the confirmation of the ticket to
the specified system.
7. A calendar should be there which helps the person to select dates. It should also show the
public and nation holidays.
8. The system should automatically show the schedule for the corresponding seat and
amount of money needs to be pay for selected seats.

1.8. Importance Of the project

The main purpose of our system is to develop computerized system rather than manual system. It
gives many benefit for customer fast and easy way it helps to the customer to save there times
and money in Geda Bus reservation system.

1.9. Opportunities
 Attract more customers.
 To create work opportunities to the people
 Decrease spent resources like, manpower, time and etc.
 Increase user satisfactions

2.0. Phase two

Purpose
The purpose of the software requirements specification document is to maintain all the functions
and the Online Geda Bus Ticket Reservation system. Besides, it contains the detailed
descriptions of all the requirements specified before.

Definitions, Acronyms and abbreviations

Administrator: the one who manages and maintains computer systems and software.

Online Geda Bus Ticket Reservation System (OGBTRS).

Server: The main computer on a network

SRS: software requirements specification

User: people who open the Online Geda Bus Ticket Reservation System (OGBTRS) web site
and the administrator of the (OGBTRS) web site.

Web: The network of computers that forms the internet.

Overview of the Existing Systems:

2.1. Over all Description

This section describes the functions of the project and their aims. It also includes the constraints
and the requirements of the project.

2.2 Product Perspective

Online Geda Bus Ticket Reservation System provides a group of works with interface
environments. Also there will be a database which will keep all the records that done by user
while visiting the page.

2.2.1. System Interfaces

Online Geda Bus Ticket Reservation system is connected with company server database, thus no
more connection with other systems is needed. No system interface is needed during the
development of this project.

2.2.2 User Interfaces

The Online Geda 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 shall be
user friendly designed.

Pages shall be connected each other in a consistent way. Operations can be done with the system
shall be repeatable.

2.3 Product Functions

The user of Online Geda Bus Ticket Reservation System are able to:-

1. Registered to the system through the first page of the application.

2. See current reservations on different Geda buses along with the details.

3. Able to choose the seats which are available for a certain class.

4. Message should be send to the concerned person about the confirmation of the ticket to the
specified system user.

5. A calendar should be there which helps the person to select dates. It should also show the
public and nation holidays.

6. The system should automatically show the schedule for the corresponding seat and amount of
money needs to be pay for selected seats.

7. The user registered to the system.

2.3.1 User Characteristics

The user types that would use the OGBTRS are as follows:

Clerk: Clerk shall usually do anything on the site, in all pages.

Clerk is responsible for updating and the maintenance of the web site content such as
adding/removing information about the company, adding/removing links onto the main bar,
adding/removing Medias in the content menu, adding/removing/updating links on the calendar
and the menu changing the logo.

Customer: customers are people who shall use OGBTS. To use this service people have the
basic computer using ability. They shall see the Geda buses information which is belong to
current time.

2.3.2 Specific Requirements

2.3.3 External Interface Requirements
Interface external to the Online Geda Bus Ticket Reservation System can be explained as “user
interfaces”.

2.3.4 Functional Requirements

Functional requirements are descriptions of activities and services a system must provide. These
requirements describe the interactions between the system and its environment independent of its
implementation. The environment includes the user and any other external system with which the
system interacts. Each is a statement of exactly what the system must do.

The following are the functional requirements associated with the new system.

FR1. Allow someone to register to become a member.

FR2 .Allow all registered users to purchase tickets for Reservation.
FR3. The system will send out automated emails to validated users.
FR4 .The user signup form should test that the form is filled in by a human and not a computer
program.
FR5 .Allow manager/clerk view:
  comment
FR6 .The system will allow passengers to search for reservation by:
 Depart Date
 Depart Time
 Source
 Destination

FR7 .The system will allow Manager/Clerk to make changes to certain settings including:
 Database
 Username
 Password
 Database Name

2.3.5 Functions
2.3.5.1 System Features
For users to have a complete understanding about the system, system feature is the main
thing to be considered.

2.3.5.2 Performance Requirements (Non

Functional Requirements)
Nonfunctional requirements describe user-visible aspects of the system that are not directly
related with the functional behavior of the system. These requirements do not directly affect the
performance of the system but are nevertheless important .They are concerned with security,
performance, internationalization, usability, maintainability, reliability, modifiability, efficiency,
portability (across operating systems) testability, understandability.

The system performance is adequate. However, Online Geda Bus Ticket Reservation Systems
working with the user internet connection, 60% of the performance is up to the client side.

The following are the non-functional requirements associated with the new system.

 The system must be error free while operating with a huge set of data.
 The system must be user friendly

 The system must be able to communicate users at different location.

 The system must recover immediately when a user enters erroneous data.

 The system must have a good response time.

 The system must be compatible with any environment.

 Maintainability & extensibility