AIRLINE RESERVATION

SYSTEM

Group Members:

Rima Roy Chowdhury ()
Deepanwita Maji ()
Sumana Chakraborty ()
Moulika Sain ()

Guide: Ms. Aditi Acharya

 Acknowledgement

We have successfully done our project “Airline Reservation

System” taking a lot of valuable tips and suggestions from a no.
of individuals. We would like to pay our sincerest gratitude to
every particular person.
We are highly obliged to Ms. Aditi Acharya (our project
guide) , for her guidance as well as her special care to ourselves.
She was along with us through the whole project to solve critical
problems whichever we faced. We are highly grateful to her.
We also express our guidance to our college and the faculty
members of Computer Science Department who have provide us
with the foundation on which we could dare to explore the
future.

-----------------------------------------------------------------------
Certificate
 Contents

Serial no. Topics to be covered Page no.

1. Introduction
1.1 Overview
1.2 Definitions
2. Feasibility Study
3. E-R Diagram
4. Data Dictionary
4.1 Table Airport
4.2 Table Fare
4.3 Table Airlines
4.4 Table Passenger
4.5 Reserve_passenger
4.6 Seat_status
4.7 Seat_reservation
5. Data Flow in the Project
6. Data Flow Diagram
7. Structure chart
8. Software design specification
8.1 Introduction
8.1.1 Purpose of this Document
8.1.2 Scope of the Development Project
8.1.3 Overview of Document
8.2 Design Goals
9. Form design
9.1 Form for loading project
9.2 Form for security
9.3 From for flight details
9.4 Form for passenger details
10. Visual Basic Code
11. Project Management
8.1 Session Management
8.2 Error Handling
12. Testing & test run
12.1 Unit testing
12.2 Integration testing
12.3 System testing
13. External Interface Requirements
13.1 Hardware Requirement
 13.2 Software Requirement
14. Provision for Future Work
15. References
16. Conclusion
1. Introduction

Overview

This Project aims to model the working of an online airway res

ervation system. The project has been built and
tested on the Oracle database, using ORACLE 9i as the
programming language. OLEDB was used as the interface
between the database and VB 6.
This Project is built to model the reservation system as
closely as possible. Some features are:

•Separate profiles for users, containing all their personal data.

•Possibility of multiple bookings per profile.

•Finding flight schedule information according to various

constraints and conditions.

•Handling of different kinds of schemes for frequent fliers, and for fl

ights.

•Separate profile type for officials.

•Appropriate error checking.

All these and other transactions and features have been

described in detail in the following section.  
 Definitions

1.Plane type: This defines the physical type of the

plane. It dictates the capacity of executive, business and
economy seats that a flight can have.

2.Airport: It consists of the airport name, its airport id and the

country and the city where it is located.

3.Flight : A flight is identified by its flight number. A flight

denotes an unique “plane”, i.e. one which is scheduled torun at a ce
rtain time, from one place to another. A flight runs over a set of
routes.

4.Route: A route is simply a tuple of airports, and every route

has a unique route id. A flight runs over a route only
if it runs from the start airport to the end airport, possibly
halting in between at other airports. A route is elementary
for a flight if the flight runs nonstop from the start airport
to the end airport.

5.Passenger: A person who can book tickets for oneself others.

Every passenger has a distinct passenger id that is denoted as
his/her ticket number. A ticket is unique. The ticket may be a
passenger ticket or a cargo ticket, and can be booked under a
passenger profile. A ticket is booked on a flight for a route that the
flight is associated with. A passenger ticket contains details about
the passenger.

6.Fare : Fare for flight depends upon the airline company

providing the flight. The fare ranges between a maximum and a
minimum depending upon the passenger’s class (i.e. Executive,
Business or Economy).

The above descriptions more or less define all the entities that
are in the ER diagram of the database project. Some
of the important and not so obvious relationships are explained :
 I. Flight-Route Ticket: This ternary relation says that a
ticket is booked on a certain flight over one route that the
flight allows. It has only the primary keys of each entity.

II. Passenger-Ticket relation: This consists of two relations:

user profile related to ticket and the official profile related
to ticket. This is done to keep the user and official profiles separate
and independent from each other.

The Entity Relationship diagram for the database is

shown in the following page.

2. Feasibility study
The main aim of feasibility study is to determine weather
developing the software product is financially and technical feasible.

The feasibility study involves analysis of the problem and

collection of data which would be input to the system, the
processing required to be carried out on these data, the output data
required to be produced by the system which we are developing.
The collection data are analyzed to arrive at the following.

• An abstract definition of the problem.

• Formulation of different solution strategies.

• Examination of alternative solution strategies and their benefits,

indicating resource required, development, cost and time in
respect of each of the alternative solutions.

• A cost benefit analysis is performed to determine which solution is

the best. At this stage, it may also be determined whether any of
 the solutions is not feasible due to high cost, resource
constraints or extraordinary technical reasons.

The output from this phase principally defines the user

requirements of the new system. It defines the propose solution and
any new or change processes, usually with some sample scenarios.
It consists of the project goal, it bounds, and the terms of reference
for the project. Furthermore, it may include any restriction on the
project, such as the part of the existing system, which can not be
changed, as well as those, which can. This will include a rough idea
of the resource requirements of each of the subsequent project
phase. It will contain tentative start and completion dates for each
phase and number of persons expected to be involved in each
phase.

The statement of what the new system will do becomes a

statement of requirements for further works and sets the guidelines
for the next phase, which elaborates these requirements in detail.

Before started work we mean the entire member of our project

team at first decides some important feature of our project. Then
emphasize about those important features and discussed. Those are
mention one by one.

At first we thought that whether we will able to complete our

project.

• We follow a standard existing Airlines Reservation System.

• Then we made a project work chart as per our requirement.

We find that all the technical (i.e., Hardware and Software needs)
are easily available and all the requirements of the software can
also be met.
 3. E-R Diagram
Total_seat

airlines
Airport_nam Airport_cod weekdays
e e Scheld_d_tim
e
flight
airport Flight_no
Leavi
ng
from
city rout Sched_a_time
countr
e
y

Avail_seat havin
g
Flight_no be
ars

Passport_no
Seat_status Passenger_nam
mov e
airlines airline
e addre
s cit
J_dat y ss

Total_sea e se
t J_date carri rout x
es e Reserve_passenger ag
Seat_n
e
o
nationalit Fare_cod
y e
Flight_no amoun class
amoun
Ticket_no t
airline t Amo_deduct_cance
R_date
s l
phon
Fare e
clas
s
Flight_n
o R_date
deposit Book
Fare_cod ed
ed route
e Seat_n
by
airlines o
Ticket_no

Seat_reservation Passenger_name
Passport_no
clas
s
J_date

amount route Flight_no

4. Data dictionary
 List of Tables in the Database with Constraints

4.1. Table Airport :

Fields Domains Constraints Description

airport_name varchar2(10) Not null Name of airport.

airport_code varchar2(5) Code of airport

City varchar2(15) City of airport.

country varchar2(15) Country in which

airport is situated.

4.2. Table Fare :

Fields Domains Constraints Description

Flight_no varchar2(8) Not null Flight whose fare is
determined

airlines varchar2(25) Name of plane.

Class varchar2(15) Not null Fare of different

class.

amount number(10) Fare amount.

amo_deduct_cance number(10) Amount to be

deducted on
l
cancellation of ticket

fare_code varchar2(9) The code of the fare

4.3. Table Flight :

Fields Domains Constraints Description

flignt_no varchar2(8) Not null Flight no to be
boarded.

airlines varchar2(25) Name of airlines.

Route varchar2(30) Route of journey.

weekdays varchar2(15) On which days a

particular flight is
departed.

total_seat number(5) Total no. seats.

Sched_a_time number(8) Arrival time.

Sched_d_time number(8) Departure time.

4.4. Table Passenger :

Fields Domains Constraints Description

passport_no varchar2(12) Not null Passport no. of the
passenger.

City varchar2(15) City of passenger.

nationality varchar2(15) Nationality of

passenger

flight_no varchar2(15) Not null Flight no of the pass.

airlines varchar2(15) Name of airlines.

Class varchar2(15) Not null On which class

(executive, economy
or business) a
passenger wants to
travel.
Route varchar2(15) Route of travel.

r_date date Return date.

j_date date Journey date.

amount number(15) Amount of flight.

passenger_nam varchar2(20) Passenger name.

e
Age number(2) Age of passenger.

Sex varchar2(2) Sex of passenger.

address varchar2(25) Address of

passenger.

Phone number(12) Phone no. of

passenger.

Ticket_no number(10) Ticket no. of the

passengers.

seat_no number(7) Seat no. of

passenger.

4.5. Table Reserve_passenger :

Fields Domains Constraints Description

passport_no number(15) Not null Passport no. of the
passenger.

passenger_nam varchar2(20) Passenger name.

e
Age number(3) Age of passenger.

Sex varchar2(2) Sex of passenger.

address varchar2(20) Address of

 passenger.

City varchar2(15) City of passenger.

nationality varchar2(15) Nationality of

passenger.

Phone number(12) Phone no. of

passenger.

Ticket_no number(10) Ticket no. of the

passengers.

seat_no number(5) Seat no of

passenger.

Flight_no varchar2(10) Not null Flight no of the

passenger.

airlines varchar2(20) Name of airlines.

Class varchar2(15) Not null On which class

(executive, economy
or business) a
passenger wants to
travel.

Route varchar2(30) Route of travel.

r_date date Return date.

j_date date Journey date.

amount number(10) Amount of flight.

fare_code varchar2(10) For a particular

amount of fare a
code is created.

4.6. Table Seat_status :

Fields Domains Constraints Description

Flight_no varchar2(10) Not null Flight no of the pass.

airlines varchar2(16) Name of airlines.

j_date date Journey date.

total_seat number(8) Total no. of seats.

avail_seat number(8) Seats leftover.

4.7. Table Seat_reservation :

Fields Domains Constraints Description

Ticket_no number(10) Not null Ticket no. of the
passengers.

passport_no number(15) Not null Passport no. of the

passenger.

passenger_nam varchar2(20) Passenger name.

e
seat_no number(10) Seat no of
passenger.

Flight_no varchar2(10) Not null Flight no. of the

passenger.

airlines varchar2(15) Name of airlines.

Class varchar2(15) Not null On which class

(executive, economy
or business) a
passenger wants to
travel.

Route varchar2(15) Route of travel.

r_date date Return date.

j_date date Journey date.

amount number(10) Amount needed to
board a flight.

5. Data Flow in the project

The data flow within the database components is explained

below through some examples.

1. An example of data flow between these entities is as soon as

a user makes a query for flights running between
two cities on a certain date.

•The table is scanned in conjunction with the airport

tables to get a listing of all the airports in the start and end cites.

•The flight table is checked for schedule arrival and departure

time of a particular flight.

•Data about flight seat availability is retrieved by a

loop in the SQL program.This is done to take into account
multiple stops.

•Finally the results found are filtered/sorted according to the a

dvanced query and displayed in proper format.

2. The other major part of the model is the inter

relation between passenger and ticket bookings. Data flow
occurs between the passenger, tickets and the flight
and route entities through the flight route ticket relation.

An example of the data flow is as follows:

A person logged in wants to retrieve info about all tickets booked

by him:

•The ticket_ids are used to find the flight_ids.

 •The flight table is then used to scan the route and get
the start and end airports.

•The times of arrival/departure are found from the flight

table.

3. Another important part of the project was to ensure consist

ent booking across multiple stops. Suppose we need to query for se
at availability in a flight which runs from A>B>C>D>E,
for the route A>E. Then the number of seats
available is the min. number of seats among all the
elementary routes that the flight takes in its path from A to E. All c
hanges to the ‘seats remaining’ are done only for the
elementary routes. Here, seats(A,E)=min(seats(A,B), seats(B,C),
seats(C,D), seats(D,E)).
This means that on booking a ticket from A>E,each of these
routes’ booked seats must be increased by 1.
The main objects used are: User and Query Result. The class
user stores information about the currently logged in
user. The class query result has information about a
successful query to the flight schedule. This is later used
in booking tickets.

6. Data Flow diagram

DFD is well known and widely used notation for specifying the
functions of an information system. They describe system as
collection of data that are manipulated by function. A DFD serves
the purpose of clarifying system requirements and identifying major
transformations. There are different types of processes and only one
type of entity, which represents the different kinds of functions
which are served by the project and the users i.e.; the customers.
And the arrows indicate the way of the procedure. And the DATA
STORES represent the updating process of the project. The DFDs of
the project is shown below;
 Level 0 DFD:

 Analysis of the level-0 DFD:

This Data Flow Diagram has only one process and entity too.
There are several queries in this DFD which are answered by the
process to the entity. This DFD only represents the entire process of
the software and the only one entity i.e., Customer.

 Level 1 DFD:
  Analysis of the level-1 DFD:
Level 1 DFD is more accurate than the previous DFD. Here,
the entire process has been broken into two processes labeling as 1
& 2. The first process i.e., process 1 maintains the database of flight
numbers, aircrafts for the specific destinations & the second
process i.e., process 2 maintains the different kinds of fares & time
schedules of different flights for different destinations & also with
these, the processes have their data stores which maintain the
tables that are made to maintain the database carefully.
 Level 2 DFD:

 Analysis of the level-2 DFD:

Level 2 DFD is more specific than the level 1 DFD. Here, both
of the processes are subdivided in several parts as process 1 in 1.1,
1.2 & so on. The process 1.1 describes the flights numbers for the
specific destinations & the processes 1.2 describe the aircraft
numbers of the corresponding flights. The process 2.1 describes the
fares for the specific destination. The process 2.2 describes the time
schedules i.e., arrival & departure time for the specific destination
of the specific flights & the process 2.3 describes the frequency of
flights in a week & also all the process have their own data stores
named as D1 & D2, Which maintains the tables of the
management.
7. Structure Chart
A structure chart represents the software architecture that is the
various modules making up the system, the module dependency
(which modules call other modules) and the partner that are passed
among the different module. A structure includes the following:

 Rectangular Boxes- Presents a module.

 Module Invocation Arrows- Connecting two modules imply

that during program execution control is passed from one
module to the other in the direction of connecting arrows.

 Data Flow Arrow- The small arrow represents the fact that
the named data passes from one module to another in the
direction of arrow.

 Library Modules- Represented by double edged rectangle used

for frequently called modules.

 Selection- The diamond represents the fact that one module

out of the several modules connected with the diamond signal
is invoked depending on the outcome of the condition attached
to the diamond signal.

 Repetition- A loop around the control flow arrows denote that

the respective modules are invoked repeatedly.

 Analysis of structure Chart-

Here,”DBM” i.e.; database manager is the main module. First

it passes the control to the module named “Requirement of the
customers” which collects the enquiries from the customers by
another module named “Get the required information fro the
customers” and also check the queries that whether they are valid
or not by another module named “Valid query from the customers”,
which also returns the acknowledgement i.e.; the queries are valid
to the module named “Requirement of the customers”, which also
returns the information to the “DBM”.

Next the “DBM” passes the control to the other module named
“Specification i.e.; required from the customers” which collects the
information of the passengers i.e.; the no. of the passengers and the
detailed information of each passengers. After getting all the
required information from each of the passengers the main module
i.e.; “DBM” shows the tickets to the customers by the module
named “Show the result i.e.; TICKET”.

8. Software design specification

Introduction
Purpose of this Document
This Software Design Specification (SDS) document contains a
brief statement of the design of Airlines reservation. In SDS, the
designers are supposed to provide an unambiguous design of the
project. The design then serves as a guide to the developers who
write the code and actually create the product. The SDS discusses
how the program is separated into modules, how the modules
interact with each other, and how users see the program. The SDS
also looks into several design considerations, including design
tradeoffs and code reusability.

Scope of the Development Project

Airlines Reservation is a software project which enables the
customer to book tickets for travelling from one city to another city.
The target people are the common people of the world who are
interested in vacations, business trips, visiting their families and
official trips.
Overview of Document
Firstly the SDS describes the overall design of the Airlines
Reservation and shows how the various modules interact with each
other. Then looks at each of these modules in greater detail. After
this it discusses the design goal of the product and lastly contains
the page transition diagram for the product.

Design Goals

The software is to be designed in such a way that the user can

be easily handle the whole system and not only that we also have
make the design by supervising the whole facility of employee and
related customer for booking tickets.

 
9. Form Design
We have designed some forms of our project by VB 6.0.
These forms are shown below.

The first form is the Security portion of our project. A

suitable user name & a specific password have been set for the
security of software. If the user name & the specific password is
match to the system, then the user can use the data base system &
software.

Following form is for loading the project.

Following form is for the security.
 The Flight Details form displays all the particulars of a flight
i.e., the route of the flight, its arrival & departure time, flight no.
etc. actually it shows the result of the query of the customers.
 The next form is for passenger. Here the details of the
passenger are inserted. The passenger name, passport no. etc are
recorded.

10. Visual Basic Code

11. project management

 Session Management:
We have used session management to keep track of user profile,
and when a user logs in/logs out. A new session
is created when the page is accessed
first.Within a session, information is stored about user (if any) logge
d in, and results of the query that he/she executes in order to book
or cancel tickets.A session is invalidated when a user logs
out,or when there are multiple login on the same account.

Storing the timetable for flights:

The date, time values are stored and compared using time
stamp and date types in SQL. Extensive use is made of
casting in order to obtain the appropriate values in the
correct format from the queries.

Error Handling:

Appropriate error handling has been done in project.

All errors are routed to the pages which process the error
according to some session attribute, and display appropriate
messages. The following errors are detected and
error messages are displayed:
•If a user tries to login using a wrong password, the
system asks him/her to try again.
•On querying for a flight schedule, we check that if the round t
rip option is selected then the date of the return journey
must be after the date of the first tri.

•If fields like the flight_id, class and route while

booking are left unspecified then the system indicates error and
asks the user to select it from the list.

12. Testing And Test run

 Testing
The aim of the testing process is to identify all defects existing
in software product. However, for most practical systems, even after
satisfactorily carrying out the testing phase, it can’t be guaranteed
that the software is error-free or whether it would work
satisfactorily. This is because of the fact that the input data domain
of most software products is very large, and it is not practical to test
the software exhaustively with respect to all the values that the
input data may assume. However, it is also true that testing does
expose many defects existing in a software product, and therefore
testing provides a practical way of reducing defects in a system and
increasing the users’ confidence in a developed system. A software
product goes three levels of testing:-

􀂾 Unit testing: - The purpose of unit testing is to determine the

correct working of the individual modules. Unit testing involves a
precise definition of the test cases, testing criteria and management
cases.

􀂾 Integration testing: - During integration testing, different

modules of a system are integrated using an integration plan. The
integration plan specifies the steps and the order in which modules
are combined to realize the full system. After each integration step
the partially integrated system is tested. The primary objective of
integration testing is to test the module interfaces.

􀂾 System testing: - System tests are designed to validate a fully

developed system with a view to assuring that it meets its
requirements. There are essentially three main kinds of system
testing –

1) Alpha testing

2) Beta testing

3) Accept testing
13. External Interface Requirements
   
Hardware Interfaces:

No special hardware is required for this product.

Software Interfaces:

1. VB
2. OLEDB
3. Oracle 9i SQL server

14. Provision for Future Work

Though our Project covers almost all the topics which are require
for Airlines Reservation for customers it can be extended further.
The provisions for extension of the project are given in the following
points.
There is no scope for online ticket booking for journey.
We believe that this ER model is quite versatile and
can handle situations much resembling real life ones. The
project can be extended to include many more features and
functionalities. Due to lack of time, we couldn’t do it within
the timeframe allotted for this project.
15. References

 Reference Books

A) Mastering Visual Basic 6 by Evangelos Petrotsous & Visual

Basic 6 Black Book by Steven Holzner.
B) SQL by Ivan Bayross.
C) Database System Concepts by Korth, Silberschatz &
Sudarshan.
D) Fundamentals of Software Engineering by Rajib Mall.

 Reference Websites

A) www.google.com

B) www.yahoo.com

C) http://www.masp.edu

D) http://www.w3school.com

E) http://www.tizag.com

 Design Tools

The design tools for the project are

 Oracle 9i for creating database

 Visual Basic 6.0 for form design & connect the database

 MS-PowerPoint for presentation

 MS-Word for documentation

 Corel Draw 12 for creating some images

  Adobe Photoshop for creating some image.

 MS Paint for creating some image.

16. CONCLUSION

Our project is a mere endeavor of designing the windows pages

for developing the concept of Airlines Reservation with VB codes
and SQL database. There exists a great scope towards the
improvement of this project. We whole heartedly wish and expect
that the great heights will be achieved in better implementation of
the window pages. We have tried our best to give a natural,
practical and developed effect to our project in this short period of
available time. The project can be properly developed and
implemented if properly worked with database and VB codes. We
have tried our best to endeavor the concept of Airline Reservation
system with our best knowledge, energy and dexterity. But they can
be made more modernized with the advancement of concept and
technologies