Software Engineering

Habesha Online Bus Ticket Reservation system

Project Proposal

Group Name
 Natnael Zewde - Nsr/1973/11
 Natnael Yohannes –Nsr/6400/11
 Sumeya Yusuf -Nsr/8887/11
 Zeyneb Redwan – Nsr/4143/11

Submitted to – Axumawit T.
Submission date – April 22 , 2021
1. Introduction

1.1 Background

Bus ticket booking during the offline era posed various difficulties to the customers as well as
the bus operators. Offline ticket booking reduced the scope of customers to choose different
options based on their travel criterion. It also increased the franchising cost for the bus operators.
At the same time, the bus operators were also finding it difficult to monitor their bus seat filling
information. Many small and medium bus service organizations do not have their own online bus
ticket booking system. Online Bus ticketing system web portal is a total internet ticketing
operations offering the benefit of total in-house management of bus schedules, ticket bookings,
ticket sales, report generation, and other business functions associated with ticket sales.

1.2 Description

Habesha Online Bus Ticket Reservation System is a Web based application that works within a
centralized network. This project presents a review on the software program “Online Bus Ticket
Reservation System” as should be used in a bus transportation system, a facility which is used to
reserve seats, cancellation of reservation and different types of route enquiries used on securing
quick reservations. HORBS is built for managing and computerizing the traditional database,
ticket booking and tracking bus and travel made. It maintains all customer details, bus details and
reservation details.

Habesha online bus reservation system (HOBRS) is a web-based application which is designed
to automate the online ticket purchasing through an easy-to-use online bus booking system. The
manual reservation is presently very strenuous and also consumes a lot of time by having to stay
on a long queue. for this reason, an efficient system is to be proposed in this paper to ease the
issue of the bus reservation by allowing visitors to check bus availability, buy and pay bus ticket
online. This system can be used by the users in performing online reservation via internet for
their all-business purposes. Users can use this program directly on their websites and no need to
install it. HOBRS also allows the visitors to choose the type of bus (sheger, anbesa, higer for
short distance and gold, selam,.. for long distance within the country) the customer prefers to use.
Bus reservation system mainly deals with maintenance of records of each passenger who had
reserved a seat for a journey. It also includes maintenance of information like schedule and
details of each bus. Also, we get to know that there are many operations, which they have to do
manually. It takes a lot of time and causes many errors.

Bus Ticket Reservation System enables the customer to buy bus ticket, make payment, and ask
for information online easily. Furthermore, staff can sell bus ticket using Bus Ticket Reservation
System after check bus ticket availability for the customer and print the bus ticket to the
customer that queue up in the counter. The method to solve this problem is to create an online
buying of bus ticket system. Customer can buy the bus ticket over the Internet, 24 hours a day, 7
days a week and the bus ticket can't be lost, stolen or left behind. In addition, the online system
lets the customers check the availability of the bus ticket before they buy bus ticket.
Furthermore, customers don’t need to pay cash only.

The aims of this system are:

 To provide a web-based buying bus ticket function. Customer can buy bus ticket through
the online system and no need to queue up to buy bus ticket in the counter.
 To provide anytime anyplace service for the customer. Customer can buy bus ticket 24
hours a day, 7 days a week over the Internet.
 To enable customer to check the availability of the bus ticket online. Customer can check
the time departure and arrival for every bus through the system.
 To ease the bus ticket payment by online. Customer has to pay for the bus ticket by
Credit/Debit Card.
 To minimize the number of staff.
2. Statement of the problem

In most cases driver information, passenger information and bus information are kept in a file.
Therefore, it is quite hard for them to search the driver information when needed. Moreover, it
uses a lot of papers and data is lost because no backup provided for the data. Some of the data is
quite hard to read because the form was filled up manually. Other problems that occur in Bus
Information is tracking its maintenance record. Most of the bus will be maintained at list four
times in year. By using a manual form, each bus must have its own maintenance record file.
Problems that occur to this manual system are to store the maintenance record file and to find it
back. It takes quite a time in order to find the correct maintenance record needed.

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 and will also need to pay cash when they buy the bus
ticket.

3. Objective of the project

3.1. General Objective

The main objective of HOBRS is to eliminate the manual reservation system. Making the
reservation system, fast, user friendly avoid the unnecessary delay in reservation. The new
system needs to develop that can handle lots of records and reports efficiently.

The main purpose of this study is to automate the manual procedures of reserving a bus ticket for
any journey made through HOBRS. This system is said to be an automatic system and
customers can select seats by themselves.
3.2. Specific Objective

Specific objectives of this project will consist of:

 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.
 Enabling customers to check the availability and types of busses online. Customer can
check the time departure for every ITC bus through the system.
 Easing bus ticket payment by obtaining a bank pin after payments is made to the various
designated banks.
 Ability of customers to cancel their reservation.
 Admin user privileges in updating and canceling payment, route and vehicle records.
 To minimize the number of staff.

4. Project Scope

The online system is an easy-to-use self-service system which enables the customer buys bus
ticket online and pays the bus ticket through Credit Card. Customer should check the availability
of the bus ticket before they buy the bus ticket. Besides departure place, arriving place, departure
date, departure time and ticket number, the bus ticket also wills states the seat number that
assigned by the system automatically. The customer has to sit in the bus according to the seat
number. The customer does not need to go to bus ticket counters and stand up in long queue to
buy tickets.

We can classify the system into three subsystems. The first subsystem is a bus reservation as
well as advanced booking system to keep track of reservation and seat availability. The second
subsystem is the tracking and selling tickets which charges for the journey. The third subsystem
is a general management service which generates reports to control all bus operations and allow
modification of subsystem information.

Users can access the reservation and booking system. Staff members can access tracking and
selling ticket systems and the general management system will be restricted to the managers.
Our bus management system has 7 different types of modules

1 Reservation module

2 Maintenance module

3 Travel module

4 Repairing module

5 Payment module

6 Ticket Module

7 Bus schedule module

5. Methodology

It is important to fulfill the planning of the implementation phase. This can only be done if
proper methodology is selected. Methodology is important to make sure all project life cycle
activities are being carried out without any shortcuts.

5.1. Description of Proposed System

The system is very simple in design and to implement. The system requires very low system
resources and the system will work in almost all configurations. It has got following features:

 It will ensure data accuracy.

 Records will be efficiently maintained by DBMS.

 Availability of seats can be enquired easily.

 Passengers can also cancel their tickets easily.

 Minimum time needed for the various processing.

  It will provide better Service.

Using case diagram

The case diagram clearly shows who can do what.

3.2 System Development Methodology

According to the nature of this system and the data collected, a waterfall methodology was used
to develop this system. Each phase required a different amount of effort and every phase had a
well-defined starting and point. Every phase had to be completed before beginning the next
stage.
The waterfall methodology was worthwhile because this approach produced a complete quality
system and error-free system due to the fact that every phase had to be completed before the next
one began thus leaving no phase unattended.

6. Cost of the project

For this project we will be using the COCOMO which is a cost estimate mode for software
projects and often used as a process of reliability predicting the various parameters associated
with a project such as size, effort, effort, cost, time and quality.
Our project type is an organic since the team is adequately small, the problem is well understood
and has been solved slightly in the past and also our team members have a nominal experience
regarding the problem.
The size for the different modules and the overall system is estimated to be:
Data entry: 0.5KLOC
Data update: 0.5KLOC
Query: 0.7 KLOC
Data Report: 1.0 KLOC
Total: 2.7KLOC

Database size: High 1.08

Storage: High 1.06
Programmer capability: Low 1.17
Use of software tools: High 0.91

The initial effort will be

Ei=a*(KLOC) ^1.05
Ei=3.2(2.7KLOC) ^1.05
Ei=9.07PM
The effort adjustment factor
EAF=1.08*1.06*1.17*0.91
EAF=1.22
The final effort
E= EAF*Ei
E=9.07*1.22
E=11.06PM
Habesha online bus registration system’s size is estimated to 2.7 KLOC which is between
2KLOC and 8KLOC.

Product design
• f(X0 ) = 16% = 0.16
• f(X1 ) = 16% = 0.16
• X = 2.7KLOC
f(2.7) = 0.16+((0.16-0.16)/8KLOC - 2KLOC)*(2.7KLOC-2KLOC)
f(2.7) = 0.16

Detailed design
• f(X0) = 26% = 0.26
• f(X1 ) = 25% = 0.25
• X = 2.7KLOC

f(2.7) = 0.26+((0.25-0.26)/8KLOC- 2KLOC)*(2.7KLOC-2KLOC)

f(2.7) =0.259

Code & unit test

• f(X0) = 42% = 0.42
• f(X1 ) = 40% = 0.4
• X = 2.7KLOC

f(2.7) = 0.42+((0.4-0.42)/8KLOC- 2KLOC)*(2.7KLOC-2KLOC)

f(2.7)=0.418

Integration
• f(X0) = 16% = 0.16
• f(X1 ) = 19% = 0.19
• X = 2.7KLOC

f(2.7)=0.16+((0.19-0.16)/8KLOC- 2KLOC)*(2.7KLOC-2KLOC)
f(2.7)=0.1625

Effort Estimate
ü System Design: 0.16 *11.06 = 1.77PM
ü Detailed Design: 0.259 * = 2.86PM
ü Code and Unit Test: 0.418 * 10.22 = 4.62 PM
ü Integration: 0.1625 * 10.22 = 1.8PM
 7. Project Scheduling

Gantt chart

Task name Durati Ap. Ap.2 Ap.26- Ap.28- May. 3- May.19 Ma.24-26
on 22- 4-25 27 May.2 18 - 23
23
Feasibility 2 days
analysis

Requiremen 2 days
t analysis
Project 2 days
planning
System 5 days
design
Coding 16
days
Testing 5 days

System 3 days
installation
 Network Diagram

 Summary of activities

Letter Task Time Predecessor

required
A Feasibility 2 days -
analysis

B Requireme 2 days Feasibility analysis

nt analysis
C Project 2 days Requirement analysis
planning

D System 5 days Project planning

design

E Coding 16 days System design

F Testing 5 days Coding

G System 3 days Project planning ,

installation Coding , Testing