1.

Title of the Project:

Online Bus Ticket Booking System

2. Introduction:

This Online Bus Ticket Booking System project will provide an Online Bus Ticket Booking

platform and thereby leverage the tedious manual ticket booking activity for a customer. We can

come up with features like saving favorite routes and providing discounts for the same. We can

provide a feature that will allow the customer to get a ticket booked without much hassle.

Initially, customers used to book tickets manually by queuing in lines at bus stations or go to travel

agents who in turn used to book tickets for them. This was actually a tedious process and was leading

to wastage of time. It also had issues like having incorrect names or other information used to book

tickets.

We can eliminate the drawbacks by developing an application which will allow customers to register

themselves and book tickets cancel tickets or postpone or propone travel dates with feasibility. This

actually is a welcome step for customers as they can access the application from anywhere and will

also avoid wastage of time that was caused due to the drawbacks in the previous way of booking

tickets manually.
 2

3. Objectives:

 Admin

 Employees

 Route Management

 Bus Staff Management

 Customer

 Manage Bookings

 View Bookings

 Cancellations

 Dashboard

4. Project Category:

WEB BASED APPLICATION:- A web-based application is any program that is accessed over a

network connection using HTTP, rather than existing within a devices memory. Web-based

applications often run inside a web browser. However, web-based applications also may be client-

based, where a small part of the program is downloaded to a user’s desktop, but processing is done

over the internet on an external server.

We describe the category of the project and how we should do project analysis of online bus ticket

booking system. Here you can learn that we should understand the problem properly before we start

2
 3

developing the project. Like in this project we first analysis the present ticket booking system and

find the problems in the existing online bus ticket booking system.

5. Project Platform:

An Online Bus Ticket Booking System, is an integrated set of interactive online services are as

following below:

 Admin

 Employees

 Route Management

 Bus Staff Management

 Customer

 Manage Bookings

 View Bookings

 Cancellations

 Dashboard

And others involved in traveling with information, tools and resources to support and enhance

traveling agencies and management.

This platform is a comprehensive system enabling secure, web-based training and e-learning

solution that employs a simple and intuitive user interface.

3
 4

6. Hardware & Software Requirements:

Hardware: Hardware includes the physical features, which are every part that you can either see or

touch, for example: monitor, case, keyboard, mouse and printer.

Software: The part which activates the physical components called software. It includes the features

that responsible for directing the work to the hardware. Software can be divided into the programs

and data.

Hardware Specification (Minimum):

Disc Space :40 GB

Memory :512 MB RAM

File System : 32 Bit/64 Bit

Software Specification:

Operating System (Server Side) :Windows 7/8/9.

Operating System (Client Side) :Windows 7/8/9.

Client End Language : HTML,CSS,jQUERY,JSP

Local Validation : PHP

Server Side Language :PHP

Database :My Sql 2000

Web Server :XAMPP server

Web Browser : Mozilla Firefox/ Chrome

4
 5

7. Data Flow Diagram:

Context 0th Level Diagram: This is the Zero Level DFD of Online Bus Ticket Booking System,

where we have elaborated the high level process of Bus Ticket. It’s a basic overview of the whole

Bus Ticket Booking System or process being analyzed or modeled. It’s designed to be an at-a-

glance view of Customer, Bus Route and Payment showing the system as a single high-level process,

with its relationship to external entities of Bus Schedule, Booking and Ticket Counter. It should be

easily understood by a wide audience, including Bus Schedule, Ticket Booking System, we have

described the high level flow of the Bus Ticket System.

Context 1st Level Diagram: First Level DFD of Online Bus Ticket Booking System shows how the

system is divided into sub systems (processes), each of which deals with one or more of the data

flows to or from an external agent, and which together provide all of the functionality of the Bus

Ticket Booking System as a whole. It also identifies internal data stores of Payment, Bus Route,

Customer, Ticket, and Ticket Counter that must be present in order for the Bus Ticket system to do

its job.

5
 6

Context 2nd Level Diagram:

DFD Level 2 then goes one step deeper into parts of Level 1 of Bus Ticket. It may require more

functionalities of Bus Ticket to reach the necessary level of detail about the Bus Ticket functioning.

First Level DFD of Bus Ticket Booking System shows how the system is divided into sub-systems.

The 2nd level DFD contains more details of Payment, Bus Route, Customer, Ticket, Ticket Counter,

Booking, and Bus Schedule.

6
 7

8. ER Diagram:

An entity relationship model is a detailed and logical representation of the data for an organization of

for business area. The entity relationship, which is also known as ER relationship is based on the

theory of real world which consist of a set of basic object, which are called entities and relationships

among these object.

The data model was developed to facilitate data base design by allowing specification of an

enterprise schema which represents the overall logical structure of a database. We will represent the

modeling concept of ER model which is higher level conceptual data. The ER-model does not

provide the overall database structure but it gives the intermediate step on the basis of which

database is designed.

7
 8

9. System Design:

The main part of designing client/server applications is to map the requirements identified into the

features provided by the environment.

Design Phase

The design phase focuses on the detailed implementation of the system recommended in the

feasibility study. Emphasis is on translating performance specifications into design specifications.

the design phase is a transition from a user oriented document (system proposal) to a document

oriented to the programmers or database personnel. The design process is a set of iterative steps that

allow the designer to describe all the aspects of the software to be built, based on the user

specifications. System design goes through two phase: The requirements analysis phase defines

WHAT a system must do and the design phase states HOW to do it.

Logical Design

We know that a data flow diagram shows the logical flow of a system defines the boundaries of the

system. Logical design specifies the user need at a level of details that virtually determine the

information flow into and out of the system and the required data resources. Logical design describes

the inputs, output, database and procedures. All in a format meets the user’s requirements.

Physical Design

It provides the working system by defining the design specification that tells programmers exactly

what that candidate system must do. In short it can state that physical design is the implementation of

the logical design.

Physical system design consists of the following:

 Specify input, output media

 Design the database and specify backup procedures.

 Design physical information flow through the system and a physical design walkthrough

 Plan system implementation

8
 9

10. Modules & Their Description:

 Admin:

It will be used by admin to create or manage Bus information and create bus staff

information. Link the bus staff to different buses that are managed. It will also have the

option to view all bookings that were done for all buses on a day or month or quarterly basis.

View all cancellations and rescheduled bookings. Will be able to confirm reschedule

bookings. Will be able to handle transactions related to cancellations.

 Employees:

The staff of website can register themselves and send an approval request to admin. Admin

will assign a role and approve the login. Once logged in they can view the no of bookings

requests. They will be able to update and confirm rescheduled bookings, also take care of

cancelled bookings and transactions.

 Route Management:

This module will be accessible to admin and employee both. Information related to all routs

will be added in this module. Information like From Where to Where, the distance between

two locations, stoppages in a route etc. Depending upon the distance saved bus travel time

will be calculated.

 Bus Management:

Will have options to add all information related to buses that are playing and then link it to

different routes. Bus features like A/C Non A/C, Two by Two or sleeper or Pushback etc will

all be added in this module.

9
 10

 Bus Staff Management:

It will be accessible to employees and admin both. It will allow saving info related to a bus

driver, cleaner, and attendant. Details, like name, phone no, email id, home address, alternate

address, an alternate contact number will all be saved for each and every staff.

10
 11

11. Process Logic of each modules:

 Admin:

Here admin controlled the everything for every customer, staff, and as well as employee

 Employees:

Here Employee can see the own details which is he or she wants.

 Route Management:

Here you can see every route of buses as well as distance between the destinations.

 Bus Staff Management:

Here you can the bus staffs where to have or where to send or in which route you wanted to send

them.

 Customer:

Here the customer can login and fill the whole details which are necessary for future

enhancement as well as future records.

 Manage Bookings:

Here admin and website staff manages the seat bookings.

 View Bookings:

Here admin can see only booking of tickets.

 Cancellations:

Here customer can cancel their ticket if they don’t want to go or other reasons.

 Dashboard:

You can see all things here.

11
 12

12. Data Dictionary:

The data dictionary is useful in case of development.

Table Name: AdminMaster

Primary Key: AdminID

Description : To store the details of admin

Serial Fields Datatype

No
1. AdminID Integer
2. Name Varchar
3. EmailID Varchar
4. Contact Integer
5. Address Varchar

Table Name: ManagerMaster

Primary Key: ManagerID

Description : To store the details of General Manager

Serial Fields Datatype

No
1. ManagerID Integer
2. Name Varchar
3. EmailID Varchar
4. Contact Integer
5. Address Varchar

Table Name:EmployeeMaster

Primary Key: EmpID

Description : To store the details of Employee

Serial Fields Datatype

No
1. EmpID Integer
2. Name Varchar
3. EmailID Varchar
4. Contact Integer
5. Address Varchar

12
 13

Table Name: ClientMaster

Primary Key: ClientID

Description : To store the details of Clients

Serial Fields Datatype

No
1. ClientID Integer
2. Name Varchar
3. EmailID Varchar
4. Contact Integer
5. Address Varchar

Table Name: BusMaster

Primary Key: BusID

Description : To store the details of Property

Serial Fields Datatype

No
1. BusID Integer
2. Busnumber Varchar
3. No. of Seats Integer
4. Type Varchar

Table Name: BookMaster

Primary Key: BookID

Description : To store the details of Payment

Serial Fields Datatype

No
1. BookID Integer
2. SeatNo. Varchar
3. JourneyDate Date
4. BusNumber Varchar

13
 14

Table Name: PaymentMaster

Primary Key: PaymentID

Description : To store the details of Payment

Serial Fields Datatype

No
1. PaymentID Integer
2. BookID Varchar
3. Date Date
4. TransactionNo Varchar
5. Status Varchar

14
 15

13. Limitations & Advantages:

Constraints:

User interface is only in Bus i.e. no other Bookings option is available. User can login only with his

assigned username and password i.e. no guest facility is available. Limited to HTTP/HTTPS.

Feasibility Study

What are the user’s demonstrable needs?

User needs a web-based system, which will remove all the above-mentioned Problems that, the user

is facing. The user wants a web-based system, which will reduce the bulk of paperwork, provide ease

of work, flexibility, fast record finding, modifying, adding, removing and generating the reports.

How can the problem be redefined?

We proposed our perception of the system, in accordance with the problems of existing system by

making a full layout of the system on paper. We tallied the problems and needs by existing system

and requirements. We were further updating in the layout in the basis of redefined the problems. In

feasibility study phase we had undergone through various steps, which are described as under:

How feasible is the system proposed?

This was analyzed by comparing the following factors with both the existing system and proposed

system.

Cost
The cost required in the proposed system is comparatively less to the existing system.

Effort
Compared to the existing system the proposed system will provide a better working environment in

which there will be ease of work and the effort required will be comparatively less than the existing

15
 16

system.

Time

Also the time required generating a report or for doing any other work will be comparatively very

less than in the existing system. Record finding and updating will take less time than the existing

system.

Labor

In the existing system the number of staff required for completing the work is more while the new

system will require quite less number of staff.

16
 17

14. Future Scope:

To solve these problems they required a computerized system to handle all the works. They required

a web based application that will provide a working environment that will be flexible and will

provide ease of work and will reduce the time for report generation and other paper works.

The main purpose behind the proposed system is to provide a comprehensive computerized system,

which can capture, collate and analyze the data from these wards and evaluate the impact of the

program.

We can also provide SMS based alert and email notifications for bookings. The Wallet can be

developed to handle discounts on the point’s basis. It can also be used to provide referral code

concept for referring friends.

Chat features can be included in the application to chat with customer care. We can come with a

feature that will allow the customer to save favorite routes and provide discounts for same.

Introduce coupon management for providing which customers can use to avail discounts.

17
 18

15. Bibliography:

 Website Design & Development, ANIL KUSHWAHA, Kindle Edition.

 PHP & MySQL, VIKRAM VASWANI, Kindle Edition.

 HTML, CSS, JavaScript & jQuery, OMAR FARUQ, Kindle Edition

Websites references

 https://www.php.com

 https://www.w3school.com

 https://www.mysql.com

 https://www.tutorialpoint.com

18