1 of 78

ONLINE TRAVEL� TICKET BOOKING

2 of 78

PROJECT PROFILE

Project Title

Online 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 2005 with C# (2.0)

Back End

SQL Server Express Edition (2005)

Operating System

Windows XP service pack –2

Internal Guide

Mrs. Vishnuba Chavda

External Guide

Mr.Kaushal Barot

3 of 78

Cont…

Submitted To

MCA Dept. ,UVPCE

Developed By

Pinaki Patel

4 of 78

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.

5 of 78

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

​

​

6 of 78

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

​

7 of 78

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.

8 of 78

Cont..

Insecurity

Travelers feel unsecured for tickets booked on phone. They have to ring up employees many times to get confirmed about their tickets.

​

9 of 78

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.

​

​

10 of 78

Cont..

Security

Customer will get a confirmation message if the tickets are booked.

​

11 of 78

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

12 of 78

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.

​

13 of 78

FEASIBILITY STUDY�

​

Economical Feasibility :

​

Economic feasibility analysis normally determine the cost and expected saving of each alternative that may be have decide.

​

14 of 78

FEASIBILITY STUDY�

​

Operational Feasibility :

​

Will the system be used if it is developed and implemented?

​

Will there be resistance from users?

15 of 78

FEASIBILITY STUDY�

​

Schedule Feasibility :

​

How reasonable is the project timetable?

​

16 of 78

SYSTEM DESIGN

SYSTEM FLOWCHART

17 of 78

START

USER

TYPE

LOGIN

UPDATE ROUTE

UPDATE BUS DETAILS

UPDATE FARE

STOP

SELECT BUS

Booking ?

BOOK TICKET

SEAT ALLOCATION

PASSENGER INFORMATION

Y

PASSENGER

ADMIN

SELECT AVALABLE ROUTE

Attempts > 3

N

Y

Cancellation?

Y

N

N

CANCELLATION

Confirmation

18 of 78

SYSTEM DESIGN

​

​

​

DATA FLOW DIAGRAMS

19 of 78

CONTEXT LEVEL DFD�

ONLINE TRAVEL

TICKET

BOOKING

PASSENGER

ADMIN

Ticket/Service Details

Inquiry/Booking/Payment

Report

Maintain Master Tables

20 of 78

  • FIRST LEVEL DFD�

21 of 78

1.0

LOGIN

​

ADMIN

Uid/Pwd

Verify & Rights

LOGIN_MASTER

PASSENGER

2.0

​

MAINTAIN MASTER

TABELS

​

ROUTE_MASTER

FARE_MASTER

Login Details

Updated Uid/Pwd

BUS_MASTER

Request for Add/update/Delete Master Tables

Details/Acknowledgment

Add/update/Delete Route Details

Route Details/Acknowledgement

Add/update/Delete Bus Details

Bus Details/Acknowledgement

Add/update/Delete Bus Details

Fare Details/Acknowledgement

Access Rights

3.0

VISITING

Go For Visiting

Details of Route/Fare/Bus/Time

Request for Fare Details

Fare Details

Request for Bus Details

Bus Details

Request for route Details

Route Details

Master Tables Info.

Master Tables Info.

22 of 78

4.0

TICKET

BOOKING

PASSENGER

Personal/ journey information

Ticket

PASSENGER_MASTER

BANK_MASTER

BILL_MASTER

Passenger Details

Acknowledgement

Payment Info

Booked Ticket info.

Acknowle-dgement

5.0

TICKET

CANCLETION

Delete Booked Ticket info.

Delete payment info.

Delete Passenger info.

Request for Cancellation

Booked Ticket info.

Acknowledgement

23 of 78

  • SECOND LEVEL DFD�

24 of 78

4.1

SELECT DESIRED

ROUTE/BUS/FARE

PASSENGER

DETAILS

Request for Route/Bus/Fare Details

Request for Fare Details

FARE_MASTER

Fare Details

Request for Bus Details

BUS_MASTER

Bus Details

ROUTE_MASTER

Request for Route Details

Route Details

25 of 78

THIRD LEVEL DFD�

26 of 78

PASSENGER

4.1.3

TICKET

BOOKING

4.1.2

DETAILS

FILLING

4.1.1

SEAT

SELECTION

​

BUS_MASTER

PASSENGER_MASTER

Booked Ticket info.

Passenger Details

Bill_MASTER

Seat Details

Updated Info

Personal information

Response

Request for Seat Allocation

Request for Ticket

Ticket Details

Ticket confirmation

Acknowledgement

Acknowledgement

Personal information

Selected Seat info.

27 of 78

SYSTEM DESIGN

​

DATA DICTIONARY

28 of 78

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

29 of 78

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.

30 of 78

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: - bus_master�Description: - Contains all the information regarding Bus And vacant seats

31 of 78

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

32 of 78

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

33 of 78

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

Table name :- Bill_master

Description :- Contains information regarding passenger bill

34 of 78

​

​

​

ENTITY RELATIONSHIP DIAGRAMS

35 of 78

ADMIN

Issues

Manages

BUS

Have

BUS

Book

TICKET

ADMIN

Manages

BUS

ADMIN

Manages

Have

BUS

ADMIN

Manages

BUS

Have

BUS

ADMIN

Manages

Book

BUS

Have

BUS

ADMIN

Manages

TICKET

Book

BUS

Have

BUS

ADMIN

Manages

Issues

TICKET

Book

BUS

Have

BUS

ADMIN

Manages

BUS

Manages

Have

BUS

Have

Book

BUS

Have

TICKET

Book

BUS

Have

Make Booking

TICKET

has Info to Book

PASSENGER

Have

1

1

M

M

M

M

M

M

36 of 78

Input Design

37 of 78

38 of 78

39 of 78

40 of 78

41 of 78

42 of 78

43 of 78

44 of 78

45 of 78

46 of 78

47 of 78

48 of 78

49 of 78

50 of 78

51 of 78

52 of 78

53 of 78

54 of 78

55 of 78

56 of 78

Output design

57 of 78

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 two

04/02/09

11:00am

300.50

Ahmedabad

jamnagr

Ac two by two

08/02/09

10:00am

415.50

Bus Fare Report

  • Report Date:28/02/09

58 of 78

Date Wise Report�

  • Report Date:10/02/09

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 two

09/02/09

11:00am

300.50

Ahmedabad

Jamnagr

Ac two by two

09/02/09

10:00am

415.50

Jamnagr

Ajmer

Ac three by two

09/02/09

04:00pm

520.00

Mumbai

Pune

NonAc two by two

09/02/09

04:00am

300.50

  • Enter Date:09/02/09

Parameterized Report

59 of 78

Source And Destination wise Report�

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 two

12/02/09

11:00am

400.50

Ahmedabad

Jaipur

Ac two by two

20/02/09

10:00am

415.50

Ahmedabad

Jaipur

Ac three by two

25/02/09

04:00pm

415.50

  • Report Date:28/02/09

Enter Source : Ahmedabad

Enter Destination : Jaipur

Parameterized Report

60 of 78

Passenger Bill Report

  • Report Date:28/02/09

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 two

4,5

850.00

2

Jaipur

Ajmer

11/02/09

11:15am

NonAc three by two

9

1000.00

3

Ahmedabad

Jaipur

20/02/09

10:00am

Ac two by two

​

4,15

800.00

61 of 78

Passenger name

Age

Address

Phone number

​

Email-ID

Patel Yogesh

20

5,sardarnagar,gatlodiya,Ahmedabad,pin-567435

9987654346

Patel Minaxi

25

7,saurabh app. maninagar,ahmedabad,pin-678543

9256786546

Passenger Details Report

  • Report Date:28/02/09

62 of 78

Payment Details Report

  • Report Date:28/02/09

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 India

43000

63 of 78

Process Phase

64 of 78

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

65 of 78

  • 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

66 of 78

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”.

Algorithm

67 of 78

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.

​

68 of 78

Scope for System

69 of 78

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.

​

70 of 78

Limitations

  • The website can not provide Registration to the passenger

71 of 78

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.

​

​

​

72 of 78

          • 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

TESTING METHODOLOGY

73 of 78

          • 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

​

74 of 78

  • 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.

75 of 78

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.

​

  • System Testing:

76 of 78

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

​

77 of 78

REFERENCES

Book:

  • Analysis & Design of Information System
  • Asp.Net Unleashed

​

Web Side:

​

​

78 of 78