ONLINE BUS TRAVEL

TICKET BOOKING
PROJECT PROFILE

Project Title Online Bus Travel Ticket Booking .

Project Aim Enables travelers to handle transactions with many
more advantages and relaxations
Developed For Balaji Tours And Travels
Front End ASP.NET 2010 with C# (2.0)
Back End SQL Server Express Edition (2008 R2)

Operating Windows 8 service pack –2

System
Internal Guide
External Guide
Cont…

Submitted To MCA Dept. ,UVPCE

Developed By Pinaki Patel
About Industry
 Name :Balaji Tours
 Address : 405,chunilal chambers,
C.G.Road,Ahmedabad
 This Tours & Travel Agency was inaugurated on 13th April,2000.
 It has Luxury buses.
 It provides small (2*2) Luxury and (2*3) buses on rent for marriage
purposes or for picnic (trips).
 Balaji Tours and Travel offer high class tours in India and abroad at
very affordable cost.
 Balaji Tours and Travel have produced hundreds of Company picnics
and special corporate events.
Hardware & Software
Requirement Specification
 Hardware Specification
Server:
Intel Pentium-IV Processor (1.8 GHz)
20 GB HDD
512 MB RAM
Client:
Intel Pentium-III Processor
10 GB HDD
128 MB RAM
Cont...

 Software Specification
Server:
Windows XP or above
.Net Framework 2.0
SQL Server 2005
IIS 5.0

Client:

Windows 9X
Microsoft Internet Explorer 5.0
System Analysis
 Existing System
Manual
Current System is not computerized, it's manual. In manual booking
system customer has to go to the traveling office and then he can get his
tickets.

Time Consuming
Sometimes he also has to spend a lot of time in queues also. It happens
that he can not get available seats in his desired bus

Dependent on Employee
The manual system is depend on more number of employees. The
different branches have to verify the available seats manually using phone.
Cont..
Insecurity
Travelers feel unsecured for tickets booked on phone. They have to
ring up employees many times to get confirmed about their tickets.
Cont..
 Proposed System

Computerized
New system is web based application. Customer can book the tickets
from his house.

Time Saving
Customer need not go to the travel agency for ticket booking & also he
may not have to wait in long queues.

Independent Of Employees
Customer can book his tickets on his own. He can view the bus timings
& check for seat availability.
Cont..
Security
Customer will get a confirmation message if the tickets are booked.
SYSTEM ANALYSIS
 FEASIBILITY STUDY
Measure of how beneficial or practical the development of an
information system will be to an organization.

TYPES OF FEASIBILITY STUDY :

Technical Feasibility
Economical Feasibility
Operational Feasibility
Schedule Feasibility
FEASIBILITY STUDY

Technical Feasibility :

Technical feasibility is normally under take to

find out whether the work can be done with the present
equipment ,current production ,existing software
technology and available personnel.
FEASIBILITY STUDY

Economical Feasibility :

Economic feasibility analysis normally determine the

cost and expected saving of each alternative that
may be have decide.
FEASIBILITY STUDY

Operational Feasibility :

Will the system be used if it is developed and

implemented?

Will there be resistance from users?

FEASIBILITY STUDY

Schedule Feasibility :

How reasonable is the project timetable?

SYSTEM DESIGN

SYSTEM FLOWCHART
 START

PASSENGER
ADMIN USER
TYPE
Y
Cancellation?
N
Attempts > 3 N
LOGIN

N
Booking ?
Y
CANCELLATION
Y
SELECT AVALABLE ROUTE
UPDATE ROUTE
SELECT BUS

UPDATE BUS DETAILS

BOOK TICKET

UPDATE FARE
SEAT ALLOCATION

PASSENGER INFORMATION

Confirmation

STOP
SYSTEM DESIGN

DATA FLOW DIAGRAMS

CONTEXT LEVEL DFD

Ticket/Service Details
Report
PASSENGER
ADMIN

ONLINE TRAVEL
TICKET
BOOKING
Inquiry/Booking/Payment Maintain Master Tables
 FIRST LEVEL DFD
 1.0
Uid/Pwd LOGIN Login Details
ADMIN LOGIN_MASTER
Verify & Rights Updated Uid/Pwd
Add/update/Delete Route Details
Access
Request for Rights Route Details/Acknowledgement
Add/update/Delete ROUTE_MASTER
Master Tables Add/update/Delete Bus Details
2.0
Bus Details/Acknowledgement BUS_MASTER
Details/Acknowledgment
MAINTAIN MASTER
Add/update/Delete Bus Details
TABELS FARE_MASTER
Fare Details/Acknowledgement

Master
Tables
Info.

Go For Visiting
PASSENGER 3.0 Request for Fare Details
Details of VISITING
Route/Fare/Bus/ Fare Details
Time Request for Bus Details
Bus Details
Master
Request for route Details
Tables
Info. Route Details
 Personal/ journey Passenger Details
information Acknowledgement
PASSENGER
4.0 Payment Info
Ticket TICKET
Acknowledgement
BOOKING

PASSENGER_MASTER
Acknowle-
dgement

Booked Ticket info. BANK_MASTER

Booked Ticket info.

BILL_MASTER

Request for Delete Booked Ticket info.

Cancellation 5.0
TICKET Delete payment info.
CANCLETION
Delete Passenger info.
 SECOND LEVEL DFD
PASSENGER Route Details
ROUTE_MASTER
Request for
Route/Bus/Fare Request for Route
Details Details

4.1
Bus Details
SELECT DESIRED
ROUTE/BUS/FARE BUS_MASTER
DETAILS
Request for Bus
Details

Fare Details

FARE_MASTER
Request for Fare
Details
THIRD LEVEL DFD
 Request for
Seat Seat Details
Allocation 4.1.1
PASSENGER SEAT BUS_MASTER
SELECTION
Updated Info
Response
Selected Seat
info.

Personal information
Passenger Details
4.1.2
Acknowledgement DETAILS PASSENGER_MASTER
FILLING
Acknowledgement

Personal information

Request
for Ticket 4.1.3 Booked Ticket
TICKET info.
BOOKING Bill_MASTER
Ticket confirmation
Ticket Details
SYSTEM DESIGN

DATA DICTIONARY
Table Name :- login_master
Description :- Contains login Details for administrator.

FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

Login_id varchar 40 Primary Key Unique login name for each user

Password varchar 40 Not Null Password of user

Table Name :- route_master
Description :- A Table which contains information regarding all
the routes.

FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

routeid int 7 Primary Key Unique identification number for each route

source varchar 25 Not Null City name from where journey will begin

destination varchar 25 Not Null City name up to where the journey will end.
Table name: - bus_master
Description: - Contains all the information regarding Bus And vacant seats

FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

bus_id int 2 Primary Key Unique identification number for each

type Bus

bus_type varchar 15 Not Null Name of the each bus type

capacity int 3 Not Null Capacity of bus

vacancy int 3 Not Null Available Vacancy

Table Name :- fare_master
Description :- A Table which contains information regarding Fare of
all the routes

FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

routeid int 7 Foreign Key Reference to route_master

bus_id int 2 Foreign Key Reference to bus_master

jdate varchar 8 Not Null Date of journey

jtime varchar 8 Not Null Time of journey

fare numeric 6,2 Not Null Fare of seat

Table Name: Passenger_Master
Description: Contains Personal Information regarding passenger.

FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

billno int 9 Foreign Key Reference to bill_master

cname char 20 Not Null Name of customer

age int 3 Not null Age of passenger
address varchar 80 Not Null Address of the passenger

phoneno varchar 15 Not Null Phone no of passenger

email varchar 50 Not Null Email address

Table name :- Bill_master
Description :- Contains information regarding passenger bill
FIELD NAME TYPE SIZE CONSTRAINT DESCRIPTION

billno int 9 Primary Key Unique booking identification number

jdate varchar 8 Not Null Reference Of fare_master

jtime varchar 8 Not Null Departure bustime

source varchar 25 Not Null City name from where journey will begin
destination varchar 25 Not Null City name up to where the journey will
end.
bus_type varchar 15 Not Null Type of bus

seat_nos int 3 Not Null seat nos Selected by passenger

total_bill numeric 9,3 Not Null Total bill

ENTITY RELATIONSHIP DIAGRAMS
 1
ADMIN Make
Issues
Booking

Manages

M
M

BUS
TICKET
M
M

Have

M
PASSENGER
BUS has Info
Book
to Book
Input Design
Output design
 Bus Fare Report

•Report Date:28/02/09

Source Destination Bus Type Journey Date Time Fare(Rs)

Ahmedabad Rajkot Ac two by two 03/02/09 10:15am 400.50
Mumbai Pune NonAc two by 04/02/09 11:00am 300.50
two
Ahmedabad jamnagr Ac two by two 08/02/09 10:00am 415.50
 Date Wise Report
Parameterized Report
•Report Date:10/02/21

•Enter Date:09/02/21

Source Destination Bus Type Journey Date Time Fare(Rs)

Ahmedabad Rajkot Ac two by two 09/02/09 10:15am 400.50

Mumbai Pune NonAc two by 09/02/09 11:00am 300.50
two

Ahmedabad Jamnagr Ac two by two 09/02/09 10:00am 415.50

Jamnagr Ajmer Ac three by 09/02/09 04:00pm 520.00

two
Mumbai Pune NonAc two by 09/02/09 04:00am 300.50
two
Source And Destination wise Report
Parameterized Report
•Report Date:28/02/21

Enter Source : Ahmedabad Enter Destination : Jaipur

Source Destination Bus Type Journey Date Time Fare(Rs)

Ahmedabad Jaipur Ac two by two 09/02/09 08:15am 400.50

Ahmedabad Jaipur NonAc two by 12/02/09 11:00am 400.50

two

Ahmedabad Jaipur Ac two by two 20/02/09 10:00am 415.50

Ahmedabad Jaipur Ac three by 25/02/09 04:00pm 415.50

two
Passenger Bill Report
•Report Date:28/02/21

Bill no Source Destination Journey Date Time Bus Type Seat No.s Total Bill

1 Mumbai Puna 10/02/90 10:00am Ac two by 4,5 850.00

two
2 Jaipur Ajmer 11/02/09 11:15am NonAc 9 1000.00
three by
two
3 Ahmedab Jaipur 20/02/09 10:00am Ac two by 4,15 800.00
ad two
Passenger Details Report

•Report Date:28/02/21

Passenger name Age Address Phone number Email-ID

Patel Yogesh 20 5,sardarnagar,gat 9987654346 Yogesh_1@yaho

lodiya,Ahmedaba o.com
d,pin-567435
Patel Minaxi 25 7,saurabh app. 9256786546 Minaxi_2@yahoo.
maninagar,ahmed co.in
abad,pin-678543
Payment Details Report

•Report Date:28/02/21

Card Number Card Type Expire Date Bank Name Balance

345678 Debit 20/08/09 HDFC 40000

456782 Visa 03/05/09 Bank Of Baroda 80000

678956 Master 22/10/09 State Bank Of 43000

India
Process Phase
Description
 PASSENGER SIDE:
The Passenger does not have to login. He/She can
easily book their tickets and get confirmation. The Web
Side provide facilities to Passenger

   Online Booking
   Ticket Availability Inquiry For Specific Route, Bus, Date
and Time
 Ticket Fare checking
   Ticket cancellation
 ADMINISTRATION SIDE:
An administrator is a person who is the owner of
the travel agency. He can perform the following tasks:-

    Add/Delete Route, Bus and Fare Details

   View Passenger and Bill Details
 Algorithm
Administrator Process:-
1. Admin logins in the system.

2. Check whether admin is authorized or not from login database.

3. If authorized then he gets all his rights.

4. Manage all the Routes, Bus ,Date, Time, Fare and view Passenger
and Bill Details

5. If unauthorized then set message “Unauthorized User”.

Passenger booking Process

1. Can check the cost of traveling.

2. Can select the Route, Bus, Date, Time of traveling .

3. Can book their tickets.

4. Will get a confirmation message and Details when their ticket is

booked successfully.

5. Can Cancel their tickets.

Scope for System
Future Enhancement
 If you see at the first glance than you will find it
to be complete but I want to make it still mature
and fully automatic. The expansion which I have
thought of are:

 E-Mail facility for sending Ticket to passenger.

 Online Payment with Credit Card / Debit Card.
Limitations
• The website can not provide Registration to the
passenger
Testing
 Once design has been completed, the software
development entered into testing phase.

 Software must be tested to uncover as many

errors as possible before delivery to customer.

 Testing involves operation of a system or

application under controlled conditions and
evaluating the results.
TESTING METHODOLOGY
 There are two method of testing
1) White-Box Testing
2) Black-Box Testing

 White-Box Testing
White-box testing is concerned with the
implementation of the program. The purpose is to
try out different programming and data structures
used in the program. This test examination
of the code rather than the specification
  Black-Box testing
Black-box testing is also known as functional
testing. It is check the function implemented in the program

Black-box testing attempts to find error such as

1) Interface Error
2) Incorrect or missing function
3) Error in data structure or external database
access
 Unit Testing:
• Individual components are tested to ensure that they operate
correctly. Each component is tested independently without
other system components.

 Module Testing:
A module is a collection of dependent components
such as object class, an abstract class data type or
some looser collection or procedure and functions. A
module encapsulates related components so that it can
be tested without other system module.
 System Testing:

The sub-system are integrated to make the

entire system. The testing process is concerned with finding errors
which normally results from unanticipated interaction between sub-
system and components. It is also concerned with validating that the
system meets its functional and non-functional requirements.
 CONCLUSION

• The website provides help to the passenger for selecting

desired Route, Bus, Date and time for Travel Ticket
Booking

• An administrator can Add/Delete Route, Bus and Fare

Details, and View Passenger and Bill Details
REFERENCES
Book:
 Analysis & Design of Information System

 Asp.Net Unleashed

Web Side:
 www.redbus.in

 www.rajnationalexpress.in

 www.google.co.in