Airline Reservation System

www.bscitmumbai.blogspot.
com
Airline
Reservation
System
Submitted By:
10-ASHISH CHAURASIA
24-PRASHANT JAGTAP
56-KAMLESH SINGH
-1- www.bscitmumbai.blogspot.com
www.bscitmumbai.blogspot.com
INDEX
Sr. No. Topic Page
1. Project Scope 3
2. System Requirements 4
3. Entity Relationship Diagram 7
4. Database Design
a. Table Structure 8
b. Constraints 10
c. Relationships 13
5. List of Processes 14
6. Data Flow Diagram 16
7. Limitations 21
PROJECT SCOPE
This Project aims to model the working of an airway reservation system.

 The Project is built to model the reservation system as
closely as possible
 Finding flight schedule information according to various constraints and

condition.
 Appropriate error checking.
SYSTEM REQUIREMENTS
In this age, Computers are becoming the part of the human life
which results into the growth of the reservation system. Many reservation
system deals with computer Software whereas some interested in a
automated reservation system.
We have introduced this software for managing the entire database

of the reservation system for the automation of all aspects related to
Airline Reservation System.
Before this software some the corresponding reservation system

used to keep record in the form of handwritten documents but when a
search for long time back record is needed then it becomes a headache of
time consuming and power wastage for the company so the best way to
handle this situation is to use this management software to improve the
company’s performance.
This software is capable to keep track of entire company’s working

and performance due to the following modules:
1. Employee:
These are the persons hired for working for the company.
They are assigned to handle customers and manage the
department also.
Employee usually updates the database as soon as

reservation to the customer is done. The also make data entry
of the employee for the passenger, ticket which includes flight
details. This updates help Company to checkout the list of
tickets booked for a particular flight.
2. Customer:
These are the person who doesn’t actually interact with the
system but the indirect relation because they reserve ticket
for a flight. Customer’s and employee’s details are been made
to the system.
These all modules help to manage the system in its best way.
Moreover, this system is introduced to meet the following user
requirements:
1. Security:
It asks for login name (user id) and password for each user
(employee) and manager also to enter into the system.
2. Compatibility with windows OS:
The software is actually designed to work under Windows

platform. So the software is compatible with the Windows
versions such as Windows 98, Windows XP, and Windows
Vista.
3. Web Support:
The software can also jump directly to the web-markets

through HTML links induced on the master-page of the
software.
4. The master-page:
The master-page or welcome-page of this software contains

the following modules in the form of links so one can easily
jump to the required portion of the system:
a. Employee detail:
It includes the detail of all employees working in the

company like name, ID, age, address, and many details.
Access to this link is denied for all employees, only
manager can access theses all records.
b. Customer detail:
It includes all details of the customers and the reservation

done, different payment mode amount, date and time. All
employees along with the manager have access to read
these records.
c. Flights detail:
This link allows the employee to jump directly to the

reservation system in the database. This will help them to
understand at which different flights are available and their
departure time.
5. For the implementation of my project the mirror H/W &
S/W requirements as under
HARDWARE SOFTWARE
Pentium II to IV Window-9x,2000,2000server
Attempt 200 MHz MS-Access
Ram –32MB MS-Excel
H.D .space-4xGB MS-Word
FDD-
CD ROM DRIVE-52x
ENTITY RELATIONSHIP MODEL
Has
Books
Department Employee Payment
Receive
For
Booked includes
Passenger Ticket Flight Details
DATABASE DESIGN
Table Structure
Table: - Department
Column Name Data Type Length Constraint

Department_id Varchar2 8 PrimaryKey
Department_name Varchar2 25 Not null
Table: - Employee
Employee_id Varchar2 8 Primary Key
Employee name Varchar2 30 Not null
Employee add Varchar2 100 Not null
Contact no Number 10
Age Number 3 Not null
Salary Number 8 Not null
Joining date Date/Time Not null
Leave date Date/Time
Leave type Varchar2 10 Not null
Department_id Varchar2 8 Foreign Key
Designation Varchar2 15 Not null
Table: - Passenger
Passenger_id Number 8 Primary Key
Passenger name Varchar2 30 Not null
Passenger add Varchar2 100 Not null
Table: - Ticket
Ticket_id Number 8 Primary Key
Passenger_id Number 8 Foreign Key
Employee_id Number 8 Foreign Key
Flight_Number Number 8 Foreign Key
Payment _id Number 10 Foreign Key
Airline Company Varchar2 15 Not null
Seat number Number 8 Not null
Date Date 15
Table: - Flight Details

Flight_Number Number 8 Primary Key
Date/Time Number Not null
Destination Varchar2 15 Not null
Type_id Number 8 Foreign Key
Ticket_id Number 8 Foreign Key
Table: - Payments
Payment _id Number 10 Primary Key
Ticket_id Number 8 Foreign Key
Payment mode Varchar2 15 Not null
Amount Number 10 Not null.
Date Date Not null.
Constraints
Table: - Department
Column Name Constraint Description
Department_id Primary key It uniquely identify each record
from the department table.
Department_name Not null This Column cannot be null each

department should have name.
Table: - Employee
Employee_id Primary Key It uniquely identify each
employee’s information from
their id.
Employee_name Not null This column cannot contain null

value the employee should
have their name.
Employee_add Not null It cannot contain null value as

employee must have an address.
Contact_no It can contain null value because

contact number can exist or not.
Age Not null It cannot contain null value each

Employee will have their age.
Salary Not null It cannot contain null value
Joining_date Not null It cannot contain null value
Leave_date It can contain null value.
Leave_type It can contain null value.
Department_id Foreign Key It is related to Department table.
Designation It can contain null value.
Table: - Passenger
Passenger_id Primary Key It uniquely identify each
passenger information from
their id.
Passenger name Not null This column cannot contain
- 10 -
Null value passenger

Should have their name
Passenger add Not null It column cannot contain

null value passenger should
have their address.
Table: - Ticket
Ticket_id Primary Key It uniquely identify each
ticket information from
their id.
Passenger_id Foreign Key It is related to Passenger table.
Employee_id Foreign Key It is related to Employee table.
Airline Company Not null This column cannot contain null

value as passenger decide the
company.
Seat number Not null This column cannot contain null

value as every passenger have
their identical seat number.
Date
Table: - Flight Details

Flight_Number Primary Key It uniquely identify each
Flight information from
their id.
Date/Time Not null This column cannot contain null

value as every flight have their
specific date and time.
Destination Not null It cannot contain null value.
Type_id Foreign Key It is related to Ticket Type

table.
Ticket_id Foreign Key It is related to Ticket table.
Passenger_id Foreign Key It is related to Passenger

table.
Table: - Payments
Payment _id Primary Key It uniquely identify Payment
type information from their id
- 11 -
Passenger_id Primary It uniquely identify each

Foreign Key passenger information from
their id.
Ticket_id Foreign Key It is related to Ticket table.

Amount Not null This column cannot contain
Null value as every flight
have their amount paid.
Date Not null It cannot contain null value

as every payment done on a
date
- 12 -
Relationships
[ADD CONTENT FROM HERE]
LEFT ENTITY RIGHT ENTITY RELATIONSHIP CONSTRAINT
DEPARTMENT EMPLOYEE ONE-TO-MANY One department

can have
many
employees.
EMPLOYEE TICKET ONE-TO-MANY One Employee can

book one or
many ticket
PASSENGER TICKET ONE-TO-MANY One Passenger can

booked one or
many ticket.
TICKET FLIGHT DETAILS ONE-TO-ONE One Ticket can

have one or
specific flight
details
PAYMENT TICKET ONE-TO-MANY One Payment can

be for one or
many ticket
- 13 -
LIST OF PROCESSES
- 14 -
GENERAL ENQUIRY In this Process, if the customer
request for information on
flight or fare and getting the
information
PASSENGER ENQUIRY If the passenger request for
checking booking enquiry or
checking New PNR
information.
BOOKING If the passenger request for
reservation and check the
status of the confirm ticket.
FLIGHT ENQUIRY If the passenger request for flight

information by checking
database, we inform
accordingly
FARE ENQUIRY If the passenger request for Fare
enquiry for a particular flight
by checking database we can
inform accordingly.
NEW PASSENGER If the New Passenger comes he
request to check for a
particular flight seats are an
available or not.
PASSENGER ENQUIRY If the Existing Passenger request
to check whether existing
PNR information.
ON THE SPOT If any Passenger come for on the

spot reservation of the ticket.
STABD BY BOOKING If any Passenger comes for Stand

By Booking or in advance
booking for a particular flight.
PAYMENT MODE The Payment for a specific ticket,

there can be a number of
ways such as Cash, Credit,
- 15 -
Cheque, and Debit
DATA FLOW DIAGRAM
Context Diagram: (Level 0)
- 16 -
Level 1: DFD of Airline Reservation System
- 17 -
LEVEL 2: DFD ON GENERAL ENQUIRY
- 18 -
- 19 -
- 20 -
LEVEL 2: DFD OF BOOKING
- 21 -
LIMITATIONS
• Since this management system is semi-automated causes a staff for

data entry purpose which can switch to the human errors.
• This reservation system cannot be used for Cancellation of ticket.
- 22 -

Airline Reservation System

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Airline Reservation System

Uploaded by

Copyright:

Available Formats

www.bscitmumbai.blogspot.

3. Entity Relationship Diagram 7

6. Data Flow Diagram 16

This Project aims to model the working of an airway reservation system.

 Finding flight schedule information according to various constraints and

We have introduced this software for managing the entire database

Before this software some the corresponding reservation system

This software is capable to keep track of entire company’s working

Employee usually updates the database as soon as

2. Compatibility with windows OS:

The software is actually designed to work under Windows

The software can also jump directly to the web-markets

The master-page or welcome-page of this software contains

It includes the detail of all employees working in the

It includes all details of the customers and the reservation

This link allows the employee to jump directly to the

5. For the implementation of my project the mirror H/W &

S/W requirements as under

ENTITY RELATIONSHIP MODEL

Passenger Ticket Flight Details

Column Name Data Type Length Constraint

Table: - Flight Details

Department_name Not null This Column cannot be null each

Employee_name Not null This column cannot contain null

Employee_add Not null It cannot contain null value as

Contact_no It can contain null value because

Age Not null It cannot contain null value each

Salary Not null It cannot contain null value

Joining_date Not null It cannot contain null value

Leave_date It can contain null value.

Leave_type It can contain null value.

Department_id Foreign Key It is related to Department table.

Designation It can contain null value.

Passenger name Not null This column cannot contain

Null value passenger

Passenger add Not null It column cannot contain

Passenger_id Foreign Key It is related to Passenger table.

Employee_id Foreign Key It is related to Employee table.

Airline Company Not null This column cannot contain null

Seat number Not null This column cannot contain null

Table: - Flight Details

Date/Time Not null This column cannot contain null

Destination Not null It cannot contain null value.

Type_id Foreign Key It is related to Ticket Type

Ticket_id Foreign Key It is related to Ticket table.

Passenger_id Foreign Key It is related to Passenger

Passenger_id Primary It uniquely identify each

Ticket_id Foreign Key It is related to Ticket table.

Date Not null It cannot contain null value

LEFT ENTITY RIGHT ENTITY RELATIONSHIP CONSTRAINT

DEPARTMENT EMPLOYEE ONE-TO-MANY One department

EMPLOYEE TICKET ONE-TO-MANY One Employee can

PASSENGER TICKET ONE-TO-MANY One Passenger can

TICKET FLIGHT DETAILS ONE-TO-ONE One Ticket can

PAYMENT TICKET ONE-TO-MANY One Payment can

FLIGHT ENQUIRY If the passenger request for flight

ON THE SPOT If any Passenger come for on the

STABD BY BOOKING If any Passenger comes for Stand

PAYMENT MODE The Payment for a specific ticket,

DATA FLOW DIAGRAM

Context Diagram: (Level 0)

Level 1: DFD of Airline Reservation System

LEVEL 2: DFD ON GENERAL ENQUIRY