Académique Documents
Professionnel Documents
Culture Documents
SCHOOL OF INFORMATICS
PROJECT TITLE: - ONLINE SKY BUS TICKETING RESERVATION SYSTEM
GROUP MEMBER
NAME
ABDISA DEMISSIE
IS/007/02
TUCHA KEDIR
IT/497/02
Advisor Name
IDNO
Vinod Chandran
Table of Content
CHAPTER ONE................................................................................................... 1
1. INTRODUCTION....................................................................................................... 1
1.1 Background....................................................................................................... 2
1.2 statement of problems...................................................................................... 2
1.3 objective............................................................................................................ 2
1.3.1 General objectives...................................................................................... 3
1.3.2 Specific objective........................................................................................ 3
1.4 scope of the project........................................................................................... 3
1.5 Limitation of the project.................................................................................... 4
1.6 Significance of project....................................................................................... 5
1.7 Methodology...................................................................................................... 5
1.8 System design and development......................................................................6
1.9 Development and Enviroment programming tools............................................8
1.10 Schedule of project.......................................................................................... 9
CHAPTER TWO................................................................................................ 13
2. SYSTEM REQUIREMENT AND SPECIFICATION DOCUMENT (SRS)...........................13
2.1 Purpose........................................................................................................... 13
2.2 Description of the existing system..................................................................13
2.3 Stake holders in Existing system.....................................................................13
2.4 Problem of existing system.............................................................................14
2.5 Comparison between Manual and Computerized ticketing system.................15
2.6 Feasibility study............................................................................................... 15
2.7 Application of the project...............................................................................18
CHAPTER THREE............................................................................................ 19
3. SYSTEM STUDY AND ANALYSIS.............................................................................19
3.1 Description of the Proposed System................................................................19
3.2. SYSTEM REQUIREMENTS................................................................................20
3.2.1 Functional Requirements...........................................................................20
3.2.2 Non-Functional requirement......................................................................21
CHAPTER FOUR.............................................................................................. 46
4. SYSTEM DESIGN................................................................................................... 46
4.1 Deployment modeling..................................................................................... 47
4.2 Database Design............................................................................................. 47
4.3 Relationship of the Database..........................................................................53
4.4 INTERFACE DESIGN.......................................................................................... 56
4.5.1 Navigation Tree......................................................................................... 56
4.5.2 User Interface............................................................................................ 58
CHAPTER FIVE................................................................................................. 68
5. CONCLUSION AND REFERENCE............................................................................. 68
5.1 Conclusions..................................................................................................... 68
5.2 Reference........................................................................................................ 68
LIST OF FRIGURES
2:
use
case
model
for
online
Sky
Bus
Ticketing
Reservation
system---------------------26
Fig 3: Member and Non Member customer ticketing reservation system Use
case model-----27
Fig 4: Class Responsibility and collaboration Domain----------------------------------36
Fig 5: sequence diagram for journey reservation--------------------------------------37
Fig 6: Sequence diagram for ticket withdraw------------------------------------------ 38
Fig 7: Sequence diagram for choose seat number-------------------------------------39
Fig 8: Class diagram for online Sky Bus Ticketing Reservation system
--------------------------------41
Fig 9: User Interface Flow Diagram---------------------------------------------------43
Fig 10: Ticket Reservation System activity Diagram-----------------------------------44
Fig: 11 Ticket Cancellation activities Diagram ---------------------------------------- 45
Fig 12: Deployment Diagram of Ticket Reservation------------------------------------47
CHAPTER ONE
1. INTRODUCTION
Traveling is a large growing business in Ethiopia. It becomes very difficult to
keep records for large number of items, customers and calculating bills. Sky Bus is
one of the travels but not much developed in Ethiopia. This is the project on the online
ticketing system of express sky Bus Company, which in most cases; the company has
problems with their ticketing and scheduling process. This project intends to computerize its
semi- computerized ticketing system to provide better customer service. Because of that, the
company can provide the easier way of travelling to the customer or passenger. The system is
sky Bus Ticket Reservation System.
We observed the working of the sky bus ticketing reservation system and after
going through it, we get to know that there are many operations, which have to do
manually. It takes a lot of time and cause many errors. Due to this, sometimes a lot
of problems occur and they were facing many disputes with customers. To solve
the above problem, and further maintaining records of items, seat availability, price
of per/seat, bill generation and other things, we offering this proposal of sky bus
reservation system.
This project is modularized a sky Bus ticketing system consists of all the activities
involved in producing a ticket which includes:
1 | Page
1.1 Background
Sky Bus transport system is an intercity coach or share company based in Addis
Ababa, Ethiopia. It is organized in 2000 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 3,000 share holders and started by having different
branches like Gondar, Bahirdar, Jimma, Hawassa, Dire-Dawa, Harar, Dessie and
Jijiga, sky bus proudly transports the most precious creature on Earth to those
destinations.
1.2 Statement of problems
System that are using by the staff at the counter currently is an internal system and
just used to sell the sky bus ticket at the counter (totally it is manual systems).
Customer has to go to the counter to buy sky bus ticket or ask for bus schedule.
Furthermore, customers need to pay cash when they buy the sky bus ticket and
sometimes needs to queue up long time to get the sky bus ticket. Besides that,
customer also not allowed buying sky bus ticket through telephone and the sky bus
company's telephone always-busy line and there is also a punishment when the
customer wants to reschedule or cancel their travel. The method to solve this
problem is to create an online buying sky bus ticket system. Customer can buy the
sky bus ticket over the Internet, 24 hours a day, 7 and the sky 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 the sky bus ticket.
The counter clerk has to manually calculate the total amount of the ticket sold and
send the daily report to the management. The daily ticket sale accounts form must
fill by the clerk daily and passed to officers on duty for verification.
1.3 Objective
The main purpose of the online buying sky bus ticket system is to provide another
way for the Transnationals customer to buy sky bus ticket.
2 | Page
To develop online reservation and ticketing system that have been replaced the
manual ticketing system.
1.3.2 Specific objective
To provide anytime anyplace service for the customer. Customer can buy
sky bus ticket 24 hours a day, 7 days a week over the Internet.
To enable customer to check the availability of the sky bus ticket online.
Customer can check the time departure and arrival for every Transnationals
bus through the system.
To minimize the number of staff at the ticket box. The numbers of staff at
the counter can be reducing after the online buying sky bus ticket system
launch.
To implement the new developed system and increase the customer
satisfaction
It replaces all the paper work
To Reduced search time
1.4 Scope of the project
The online sky bus system is an easy-to-use self-service system which enables the
customer to buys sky bus ticket online. Customer has to check the availability of
the sky bus ticket before they buy the sky bus ticket. After process buys sky bus
ticket is successfully, the customer can get the sky bus ticket by print out the sky
bus ticket and give the sky bus ticket to the sky bus driver when he/she wants to
take bus.
Besides departure place, arriving place, departure date, departure time and ticket
number, the sky bus ticket also wills states the seat number that assigned by the
system automatically.
Generally the scope of our projects includes the following points
A person should be able to:
1. Registered to the system through the first page of the application
2. See his/her current reservations on different sky buses along with the details.
3. Register to the system through the application
3 | Page
4.
5.
6.
7.
8.
9.
To develop an online sky bus reservation system all the needed requirements need
to be fulfilled. In the context of this project there are restrictions and drawbacks
which can be considered as limitations of the project. In general the limitations are:
Expensiveness when we say expensiveness, to use our website we have
to get an accessories and materials like computer, internet access, etc so for
those materials they are expensive.
Limited access when we use the website, there must be an internet
access. The place whose does not have an internet connection, there is no
chance to use our website.
Skill ability the website user or consumer who does not have knowledge
and skill ability how to use internet, so it does not consume our service.
Shortage of equipments
There may be a power fluctuation in the lab; this may cause not to finish
the project in the estimated schedules.
Our files and documents may be affected by a virus and worms.
4 | Page
The online sky bus is very important company for customer, sky Bus Company and all. It is
important to customer because customer can check availability of the sky bus ticket, buy sky
bus ticket.
Electronic ticket is different with traditional paper ticket because electronic ticket is safer,
faster, reliable and cheaper. Besides that, this concept can be used by others sky bus company
so that their customers will be easier. The profit for the sky bus company will be increased
because the online system will attract more customers and no need to hire many staffs at the
counter to sell sky bus ticket because ticket can be sold efficiency online.
1.7 Methodology
OBSERVATION
Observation is the first method used to gather information regarding the
development of an online sky bus reservation system. For this project we were visit
to observe the buying habit of passengers and also observe the selling of tickets by
the sky bus branch which is found in Hawassa. From the observation, we found
that the human traffic is extremely high.
INTERVIEW
Interview is the second method used to gather some information regarding an
online sky bus reservation system. Interview was conducted with the sky bus
personnel in Hawassa branch office.
5 | Page
There are many methodologies to carry out our system (project) but we have
chosen to implement the object oriented approach because of the following few
reasons:
It is one of the widely accepted method
The object-oriented approach combines data and processes
(called methods) into single entities called objects which can
be easy to show necessary operations.
Object-oriented approach makes system elements more
reusable, thus improving system quality and the productivity
of systems analysis and design.
Describes the real world by its objects, the attributes, services,
and relationships
Improved communication among users, analysis ,designer and
programmers
The ability to tackle more achieving problem domain
Increased
consistency
among
analysis
,design
and
programmers
the Waterfall software development life cycle, the implementation of the system is
preceded by requirements definition, analysis, design and development. The online
Sky Bus Ticketing reservation system is the project that done through a sequence
steps that is from concepts to the through design, implementation, testing,
installation, troubleshooting, and ends up at operation and maintenance and which
follows the sequence of registering first before coming to reserving tickets and
seats so the system is clear and obvious to the customer because of the reason that
waterfall have advantages of: Easy to use.
It is simple and easy to explain to the user.
The project requires the fulfillment of one phase, before proceeding to the
next.
7 | Page
Deployment Diagram
Gant chart
Design tool
Activity diagram
Class Modeling
Database design
B. system Development Environment
Software Requirements
Programming languages
:
PHP
MS Office tools
: MS-Word, PowerPoint
Script
:
CSS Java script
Data base or data retrieval quarries
:
MYSQL
Notepad ++
Adobe Photoshop
Microsoft Visio
E Draw max trial version
8 | Page
Start date
Week1
Last date
Week1
Out put
List of title
Week1
Week1
Week1 1
Week1
4.data collection
Week2
Week3
5.project proposal
Week2
Week3
Complete project
suggestion form.
Describing about
the project title
and its features
with advisor
Gathering data
from organization
and different
sources
Writing project
9 | Page
6.Mid term
presentation
7.system design
8.presentation on
the system design
Week4
Week4
Week 5
Week 8
Week7
Week8
9.Implementation
10.Testing
Week9
Week 13
Week12
Week14
11.Final document
submission
Week 15
Week16
12.Final
presentation
Week 17
Month
proposal
Presenting what
we have proposed
Designing
Final report
project or
presenting the
designed system
Implementing
Analysis the
existing system
Submitting the
written document
to advisor
Week17
December January
Februar March
April
May
June
Weak
y
Weak
Weak
Weak
Weak
Weak
Weak
Activity 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
project
1 2 3 4
proposal
system
design
presenta
tion on
10 | P a g e
the
system
design
Implem
. . . .
entation
Testing
Final
docume
nt
submiss
ion
Final
presenta
tion
Items
1
2
3
4
paper
CD
Pen
Transportat
ion
Call phone
Print
Miscellaneo
us cost
7
5
6
7
Total
Price (In
birr)
50.00
10.00
7.00
25.00
Quantity
10.00
15.00
35.00
2 times
15 pages
5 times
152.00
228.00
200
2
2
Group
11 | P a g e
CHAPTER TWO
2. SYSTEM REQUIREMENT AND SPECIFICATION DOCUMENT (SRS)
2.1 Purpose
tickets for the customers, which means the ticket sales counter clerk will put the
ticket aside. The customer has to come personally to the ticket counter one day
before the actual trip to collect the reserved ticket. Failing to do so, the ticket will
then be released to other passengers.
The ticket sales counter clerk has to manually calculate the total amount of the
ticket sold and send daily report to the top management. Matter becomes
complicated when several branches conduct the ticketing selling task for the same
bus at the time. The ambiguities let the management face operation and accounting
problems.
2.3 Stake holders in existing system
The main users of this product are those who have the right to access this
software. These users are sure to be literate with the computers.
The user types that would use the online sky bus reservation system are as follows:
Clerk: Clerk shall usually do anything on the site, in all pages. Clerk is also
responsible for updating 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 online sky bus reservation system.
To use this service people have the basic computer using ability. They shall see the
sky buses information which is belong to current time.
Manager The manager can access all the functions in this system, which
includes the bus operator information, view comment, member and staff account,
and reports.
2.4 Problem of existing system
The passenger must wait for their required bus which is time consuming
process, as it possible that sometimes there would be no buses available to
the desired place for a long period of time.
The passenger must reserve tickets directly. So they have to wait in long
queue and reserve tickets. This will be time consuming
Most of the records are maintained on paper.
Existing system is totally on book and thus a great amount of manual work
has to be done. The amount of manual work increases exponentially with
passengers
Lack of security of data (anyone is able to see, change or deleting existing
data).
2.5 Comparison between Manual and Computerized ticketing system
14 | P a g e
Feasibility analysis begins once the goals are defined. It starts by generating broad
possible solution, which are possible to give an indication of what the new system
should look like. This is where creativity and imagination are used.
Feasibility of a new system means ensuring that the new system, which we are
going to implement, is efficient and affordable. There are various types of
feasibility to be determined: Technical feasibility
Operational feasibility
Economic feasibility
TECHINCAL FEASIBILITY
This evaluation determines whether the technology needed for the new system is
available and how it can be integrated within the organization.
The projects were going to expected greater return on their development; technical
risks were also valuable tool to understand the sources and types of risks as well as
their management.
Risk Name
-Failure to attain expected benefits
Risk Management
-Reviewing /Feedback mechanism of
estimates
15 | P a g e
OPERATIONAL FEASIBILITY
Operational feasibility covers two aspects. One is a technical performance aspects
and the other is acceptance within the organization. Technical performance
includes issues such as determining whether the system can provide the right
information for the organization personnel, and whether the system can be
organized so that it always delivers this information at the right place and on time.
Operational feasibility must determine how the proposed system will fit in with the
current operations and what, if any, job restructuring and retraining may be needed
to implement the system.
ECONOMIC FEASIBILITY
This evaluation looks at the financial aspects of the project. It determines whether
the investment needed to implement the system will be recovered. Economic
feasibility concerns returns from the investments in a project. It determines
whether it is worthwhile to invest the money in the proposed project or whether
something else should be done with it. To carry out economic feasibility study, it is
necessary to place actual money values against any purchase or activities needed to
implement the project.
16 | P a g e
This project has great assumption to generate online sky bus reservation system in
Share Company of sky bus. This project connects people like customer and
company. Any people can investigate any online categorized services in his home,
working place or any where using internet including mobile internet.
The passenger goes to office personal when they want to travel to buy sky bus
ticket, check availability of seat and cancel or reschedule their travel. Our proposed
solution would eliminate those problems and make the system to be present online.
17 | P a g e
CHAPTER THREE
3. SYSTEM STUDY AND ANALYSIS
INTRODUCTION
System Analysis is a phase which is conducted before the development of the
Online Sky Bus Ticketing System web. System Analysis shows the requirement
or a description of the needs and desires for an information system. A
requirement may describe functions, features, and constraints. Thus, system
requirement defines the services provided by the system and prescribes
constraints for its operation.
3.1 Description of the Proposed System
The proposed system is recommended that an online sky bus ticket reservation
system a solution that attempts to solve many of the existing problems in the
current sky bus ticketing system. The system provides proper security and reduces
the manual work and it will help the user to reduce the workload and mental
conflict.
The objective of this system is to provide the organization a new system that
provides all the functionality specified by the organization, that is more users
friendly and less complex.
In effort to improve the existing sky bus ticket over the counter, observation on the
problems had been conducted. Therefore, the goal of the online sky bus ticket
reservation system is to provide a revolutionary way to interact effectively.
Effectives of online sky Bus Ticketing reservation system
Online sky bus ticket reservation is more efficient compared to buying a sky
bus ticket over the counter
Online sky bus is user friendly
It is more convenient
18 | P a g e
should also be provided throughout the system in order to guide users when
they encounter any problems.
B MAINTAINABILITY
Maintainability is the ease with which a program can be corrected if an error is
encountered, adapted if its environment changes, or enhanced if the
customer desires a change in requirement .
C RELIABILITY
Reliability is the extent to which a program can be expected to perform its
intended function with requirement precision.
This system should perform all its services and functions accurately and in
timely manner. This quality is essential as it indicates how far users will have
confidence in the implementation of this online sky Bus Ticketing System.
D RESPONSE TIME / SPEED
The system should be able the process any transaction at the highest speed
and avoid unnecessary interaction. As a low response time, the users may feel
frustrated and decide not use this system.
20 | P a g e
E SECURITY
This system should have security measures to minimize the risk of data exposure
to unauthorized people. Only the authorized users with the correct login and
password are allowed to access and manipulate the data kept in the database.
F USER-FRIENDLY
A user-friendly interface enables the users who are with or without technical
background able to operate and use this system. A user-friendly system will
satisfy users and allow interaction with this website and able to utilize this
system to the maximum.
Online Sky 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.
SYSTEM INTERFACES
The Online Sky 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.
USER INTERFACES
The Online Sky 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.
GOALS OF USER INTERFACE
21 | P a g e
23 | P a g e
The default communication protocol for data transmission between server and the
client is Transmission Control Protocol/Internet protocol (TCP/IP). At the upper
level hypertext transfer protocol (HTTP, default port=80, default of apache
port=8080) will be used for communication between the web server and client.
3.3 Use case
Use case defines set of interaction between actors and use case models
considerations. It is a tools used in system analysis to identify, clarify and organize
all system activities that have significations to the project. Use case diagrams are
diagrams used for capturing for functional requirements of the system. Each use
case diagram describes a behaviorally related sequence of transaction in a dialogue
between the user and the system.
24 | P a g e
Fig 2: use case model for online Sky Bus Ticketing Reservation
system
25 | P a g e
26 | P a g e
Fig 3: Member and Non Member customer ticketing reservation system Use
case model
Registration
Passenger
Allow someone to register to become a user.
The user must know how to register to the
system.
Post-condition
Basic course of action
Alternative courses
successfully.
1.1The users might miss to fill their personal
info.
A 1.2 Error message appears
A 1.2 Continue with step 1 in the normal
course events.
A 2.1 the system may failed to connect to
database
A 2.2 Shows error messages.
Reservation
Use case name
Actors
Reservation
Passenger and Clerk
28 | P a g e
Descriptions
Pre-conditions
Post- conditions
Basic course of actions
Alternative courses
User reservation
The user must be registered to the
system.
1. The passenger wants to reserve.
2
The passenger enter name and
password
3
The system check availability of
Ticket
4 The system allow for passenger to
reserve.
5 The system display availability of
Ticket.
6 The passenger enters his/her
information.
7 The system verifies the entered
information.
8 The system checks validity of Ticket.
9 Validity of message displayed to
passenger
10. The passenger reserve ticket.
A 2.1users can enter their names
wrongly.
A 2.2 Error massage appears
A 2.3 Continue with step 2 in the normal
course events.
Seat
29 | P a g e
Actors
Descriptions
Passenger
Verify availability of seat
Pre-conditions
Post-condition
Basic course of Action
Alternative courses
system
A 2.1users entered seat id wrongly
A 2.2 Error message appears.
A 2.3 continue with step 5 in the normal
course events
Description
Pre-conditions
Post- conditions
Basic course of action
system.
Post-condition
Basic course of action
Alternative courses
Payment
Passenger
Paying money for available (selected)
seat(s)
The passenger must be registered to
32 | P a g e
system.
Post-condition
Basic course of action
Alternative courses
Login
Table of use case description for login
Use case Name
Login
33 | P a g e
Actors
precondition
Basic course
action
System
2.Displays form
4.Verifies username
and password
5.use case ends
Post condition
User access to the system close window or logout
Domain modeling is the task of discovering class that they represent things and the
concepts to the problem space for the project.
34 | P a g e
35 | P a g e
36 | P a g e
Basicaction
course of Reserve
Login
screen
Passenger
Journey:journey
Passenger:Passenger
Journey
JourneyMainmenu
<<UI>>
<<controller>>
Journey
reservation
name and
1.want2.Enter
to password
reserve
1.Thereserve
passenger
want
to
journey
2.The
enter
namepassenger
and password
<create>
name
Password
3.The system
shows
information
to passenger
3.show
information
4.The system
show
journey
4.show
journey
information
information
5.choose
seat
5.The passenger
choose
number
the journey
6.The
systemof
display
the
6.display of
availability
journey
availability
journey
7.The system
show
the
availability
of seat
number
<create>
8.The seat
passenger
choose
get schedule()
number
get journey()
9.The
system
verify
the
7.show
available
of
passenger entry
seat number
10.validityto
ofpassenger
message
8.choose
seat10.displays
displayed
number
valid message
11.The reservation
passenger accept
9.verify
11.accept
reservation
37 | P a g e
Withdraw Ticket
Main menu
Login screen
Ticket
passenger
Withdraw ticket
1:want
to withdraw
1.Thewithdraw
passenger
Want to
2:Enter name and password
ticket
2.The passenger
<create>
info enter his/her
Name
3.The system
withdrawal
form to shows
passengers
Password
4.The
passenger
enter 3.show form
required
information
5.The passenger
click4.Input
submit full info
to database
6.The system
search
passenger
5.Passenger submit
info from
database
6.search
7.The
system
check
reserved
ticket
from
database
7.check
8.The system
inform
withdrawal
to passenger
8.Withdraw info
9.The passenger
withdraw
ticket is successful
9.Withdraw
from database
38 | P a g e
39 | P a g e
Classes are show as boxes with three sections, the top one indicates the name of
the class, the middle one lists the attributes of the class, and the third one lists the
process of the activity in this class.
The class Diagram below shows the class of our system, their inter relationship
(including inheritance and association) and the operations and attributes of each
classes.
40 | P a g e
system
3.7 User Interface Flow Diagram
User Interface is communication channel that end-user can interact with a system.
All knowledge against a system occurs in compliance with the interaction of the
user and interface. Therefore, according to development environment of the
application changes rapidly, we became to need interface design to support
complex interaction between human and computer. In this documentation, we
suggest user-centered design models to standardize user interface prototype and
supports flexible development in by customizing it.
42 | P a g e
Activity diagram shows the conditional logic for the sequence of system activities
needed to accomplish a business process. It clearly shows parallel and alternative
behaviors that can be used to show the logic of a use case. In our system, we
identified some activity diagrams to clearly show the activities in the system. The
43 | P a g e
following activity diagrams show activity diagrams, registration and which are the
main tasks of the system.
44 | P a g e
45 | P a g e
CHAPTER FOUR
4. SYSTEM DESIGN
System design is the transformation of the analysis model into a system design
model. The purpose of this document is to provide an overview as to how to
actually build the proposed system and to obtain the information needed to derive
the actual implementation of our system. During the last phase we, the team has
extensively worked on the system analysis to understand what will be built. In
many ways, this is a continuation of that work, only here we draw the system
closer towards implementation. In this part of the document, we have used include
the following diagram to understand our system.
Goals of Design
The goal of the system design is to manage complexity by dividing the system in to
smaller manageable piece. Some of the goal is listed below:
Security: - the system should be securing an authorized user.
Modification: - the system should be modifiable to modify different services
depending on the need of the institute.
Flexibility: the system is able to change to suit new condition or situation
Efficiency: the system must be doing what it is supposed to do efficiency without
any problem.
46 | P a g e
Deployment modeling is used to show the hardware of the system the software that
is installed in the hardware and also the middleware that is used to connect the
disparate machines to one and other. It also shows how the software and the
hardware components work together.
47 | P a g e
chosen
DBMS.
48 | P a g e
Data Dictionary
i.
Field
Id
Type
Int
size
9
constraints
Primary key
Description
Bus ID
fld_bustype
fld_busregnumber
varchar
varchar
20
15
Null
Foreign key
Bus Type
Bus
registration
NOT Null
NOT Null
Null
Null
NOT Null
number
Bus Origin
Bus destination
Number of seats
Number of seats sold
Number of seats
NoTNull
Not Null
Not Null
Not Null
Not Null
available
Adult fare
Child fare
Bus return origin
Bus return destination
Bus return journey
Not Null
date
Bus return journey
Null
time
Bus return journey
Null
seats
Bus return journey
fld_origin
fld_destination
fld_seats
fld_sold
fld_available
fl_adultfare
fld_child
fld_rorigin
fld_rdestination
fld_rdate
fld_rtime
fld_rseats
fld_ rsolds
varchar
varchar
Int
Int
Int
varchar
varchar
varchar
Varchar
varchar
varchar
Int
varchar
25
25
10
10
10
15
15
15
15
15
10
10
10
sold
ii.
Field
size
constraints
Description
49 | P a g e
Id
totalseats
Varchar
Varchar
selectedseats
Varchar
9
10
10
Primary key
Null
Seat ID
Total number of
NOT Null
seats
Selected seats
constraints
Primary key
Null
NOT Null
Description
Company ID
Company name
Company
NOT Null
Username
Company
Type
Varchar
Varchar
Varchar
varchar
size
9
20
20
20
Password
iv. Table Name: Feedback
Field
Id
Fld_username
Fld_subject
Fld_message
Type
Int
varchar
varchar
varchar
size
9
constraints
Primary
Description
ID
10
10
20
key
Not Null
Null
Not Null
Username
Subject
Message
Size
9
constraints
Primary
Description
ID
20
20
key
NOT Null
NOT Null
Subject
Message
Type
Int
varchar
varchar
50 | P a g e
Type
Int
Varchar
Size
6
15
constraints
Primary key
Not Null
Description
Destination ID
Destination
constraints
Primary key
Not Null
Null
Not Null
Description
ID
Username
Subject
Message
Type
Int
varchar
varchar
varchar
Size
9
25
25
25
Type
Int
varchar
varchar
Int
varchar
varchar
varchar
Size
9
25
25
10
15
15
25
constraints
Primary key
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Description
ID number
Username
Password
Age
Address
Contact number
E- Mail address
constraints
Description
Type
Size
51 | P a g e
id
fld_ticketnumber
fld_busnumber
fld_username
fld_origin
fld_destination
fld_returnadults
fld_returnchilds
Int
varchar
varchar
varchar
varchar
varchar
Int
Int
9
20
20
25
20
20
10
10
Primary key
Primary key
Primary key
Not Null
Not Null
Not Null
Null
ID number
Ticket number
Bus number
Username
Bus origin
Bus destination
Bus
return
Null
number of adults
Bus
return
number
fld_address
varchar
fld_totalamount
varchar
fld_contact
fld_returnjdate
fld_returnjtime
fld_payment
varchar
varchar
varchar
varchar
25
25
25
25
25
25
Not NULL
Not Null
NULL
NOT NULL
NOT NULL
NOT NULL
of
children
Address
Total amount
Contact
Bus return date
Bus return time
Payment
The following are some of the entity used in our projects. Those
are: Passenger,
52 | P a g e
53 | P a g e
54 | P a g e
The Structure Design of Online sky Bus Ticketing System web portal shows a
birds eye view of the entire system. Generally the Online Sky Bus Ticketing
System web portal allows easy accessibility to obtain information. Customer can
browse the web portal to obtain various types of information such as bus schedule
information, promotions, latest news, forums, feedback and star rating for bus
operators. On the other hand the Administrator would be able to assess the system
to update the portal on bus schedule information, promotions, latest news, forums,
feedback, and report generation.
55 | P a g e
HOME
CONTACT US
BOOKING CANCELLATION
FEEDBACK
ABOUT US
USER INSTRUCTIONFAQ
LOGIN
CLERK
MANAGER
PASSENGER
SEARCH DESTINATION
REPLY FEEDBACK
SELECT DESTINATION
MODIFY/UPDATE SKY BUS
SCHEDULE
ADD SKY BUS SCHEDULE
DELETE
SKY BUS SCHEDULE
SELECT SEAT
PURCHASE TICKET
PRINT TICKET
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDBA
CK
USER
INSTRUCTION
56 | P a g e
FAQ
LOGIN
PAGE
Single
Return
Departure:
Arrival:
LOGIN HERE!
First name
Password
Create Account
Here:
searc
h
57 | P a g e
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDB
ACK
USER
INSTRUCTION
FAQ
Registration Form
User Name
password
Confirm password
E-mail
Address
Contact Number
submi
t
Reset
58 | P a g e
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDB
ACK
USER
INSTRUCTION
FAQ
Login Here!
Passenger ID
First Name
password
Regist
er
cancel
59 | P a g e
HOME
CONTACT
US
ABOUT US
BOOKING
CANCELLA
TION
FEEDBACK
USER
INSTRUCTI
ON
FAQ
First Name
Last Name
Postal code
city
Contact Number
60 | P a g e
Age
Sex
source
Destination
Price
Date
submit
cancel
61 | P a g e
HOM
E
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDBA
CK
USER
INSTRUCTION
FAQ
source
Destination
Travel Date
Seat Number
Next
62 | P a g e
HOM
E
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDBA
CK
USER
INSTRUCTION
FAQ
63 | P a g e
submit
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDBA
CK
USER
INSTRUCTION
FAQ
Passenger
ID
First
Name
Last
Name
Postal
code
City
Sourc
e
Destinatio
n
Emai
l
Price
Age
64 | P a g e
cancel
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDBA
CK
USER
INSTRUCTION
FAQ
65 | P a g e
Passenger
ID
First
Name
Last
Name
Postal
code
City
Sourc
e
Destinatio
n
Emai
l
Price
Age
66 | P a g e
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDB
ACK
USER
INSTRUCTION
FAQ
67 | P a g e
HOME
CONTACT
US
ABOUT
US
BOOKING
CANCELLATION
FEEDB
ACK
USER
INSTRUCTION
FAQ
Destinati
on
Departu
re time
Adult
Fare
Child
Fare
Statu
s
No. of
Adults
No. of
Childs
Bus
Numb
er
Onwar
d Date
2C
2B
3C
3B
4C
4B
5C
5B
6C
6B
7C
7B
8c
8B
1A
2A
3A
4A
5A
6A
7A
8A
9c
9B
9D
9A
Bu
y
68 | P a g e
CHAPTER FIVE
5. CONCLUSION AND REFERENCE
5.1 conclusions
After literature review, research and case study on the proposed system, we found
that sky Bus Ticket Reservation System is a potential system in Ethiopia.
The application software Online sky Bus Ticketing Reservation System has been
prepared with great excitement and enthusiasm. It required a lot of efforts and hard
work, which was possible only by team work. The characteristics of this software
which make it more effective and efficient from existing system are as follows:
It provides an efficient security system to the software
All work is computerized, so, no man power is required
It is easily understandable and reliable
The users requirement is fulfilled
The application provides platform independent software
5.2 reference
1. Stephen, R. (2005) Object Oriented and classical Software Engineering
2.
3.
4. Software engineering text book and object oriented software engineering book.
5.
70 | P a g e