AIRLINE RESERVATION SYSTEM

ABSTRACT

The main purpose of this software is to reduce the manual errors involved in the airline
reservation process and make it convenient for the customers to book the flights as when they require
such that they can utilize this software to make reservations, modify reservations or cancel a
particular reservation.

The name of the application is “AIRLINE RESERVATION SYSTEM”. This application

provides alternatives for watching different routes available with different timings for a particular
time frame and provides clients with the service to publication an admission, change or terminate a
particular reservation but it does not offer the clients with information of price of the admission and it
does not allow the client to alter a particular aspect of his reservation and he/she can change all his
information.

The Airline Reservations System (ARS) was one of the earliest changes to improve efficiency.
ARS eventually evolved into the Computer Reservations System (CRS), and then into Global
Distribution System (GDS). The airline industry created the first GDS in the 1960s as a way to keep
track of flight schedules, availability, and prices. Although accused of being “dinosaurs” due to their
use of legacy system technology, GDSs were actually among the first e-commerce companies in the
world facilitating B-2-B electronic commerce as early as the mid 1970s, when SABRE (owned by
American Airline) and Apollo (United) began installing their propriety internal reservations systems
in travel agencies. Prior to this, travel agents spent an inordinate amount of time manually entering
reservations. The airlines realized that by automating the reservation process for travel agents, they
could make the travel agents more productive and essentially turn into an extension of the airline’s
sales force.

The web based “airline reservation system” project is an attempt to stimulate the basic concepts
of airline reservation system. The system enables the customer to do the things such as search for
airline flights for two travel cities on a specified date, choose a flight based on the details, reservation
of flight and cancellation of reservation.

The system allows the airline passenger to search for flights that are available between the two
travel cities, namely the “Departure city” and “Arrival city” for a particular departure and arrival
dates. The system displays all the flight’s details such as flight no, name, price and duration of
journey etc.
 EXISTING SYSTEM.

The effectiveness of the system depends on the way in which the data is organized in the
existing system, much of the data is entered manually and it can be very time consuming.
When records are accessed frequently, managing such records becomes difficult. Therefore
organizing data becomes difficult.

The major limitations are:

 Modification are complicated.

 Much time consuming.
 Error prone.
 Unauthorized access of data.

PROPOSED SYSTEM.

The proposed system is better and more efficient than existing System by keeping in
mind all the drawbacks of the present system to provide a permanent to them.

The primary aim of the new system is to speed up the transactions. User friendlines is
another peculiarity of the proposed system. Messages are displayed in message boxes to
make the system user friendly. The main Advantage of the proposed system is the reduction
in labor as it will be possible so search the details of various places. Every record is checked
for completeness and accuracy and then it is entered into the database. The comments and
valid messages are provided to get away redundant data. Another important feature of the
proposed system is the data security provided by the system.

The main Objectives of the proposed System are :

 Complex functions are done automatically.

 Processing time can be minimized.
 Simple and easy to manage.
 Chances of errors reduced .
 Faster and more accurate than the existing system.
 Easy for handling reports.
 3) SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS.

HARD DISK : 320 GB

PROCESSOR : DUAL CORE
RAM : 2 GB
INPUT DEVICE : KEYBOARD & MOUSE.
OUTPUT DEVICE : LED MONITOR.

3.2 SOFTWARE REQUIREMENTS.

OPERATING SYTEM : Windows.

FRONT END : SERVLET,HTML, CSS
BACK END : MYSQL
SERVER : TOMCAT SERVER

MODULE DESCRIPTION

 ADMIN LOGIN
 FLIGHT DETAILS
 ADD FLIGHT
 FLIGHT REPORT
 BOOKING TICKET REPORT
ADMIN LOGIN:

A user who has traveled by the airline earlier would have been given a user id and a password. He
would have his personal information stored in the database referred to earlier in section 2 as ‘DB-
user’. This ‘personal information’ would be henceforth referred to as ‘profile’. Such a user with a
profile in DB-user shall be called a ‘registered user’. A registered user will be able to check the
availability of tickets as well as block/buy a ticket by logging into the system.

FLIGHT DETAILS

After logging in a user (either a registered user or a guest), the system shall request him to enter
the following details – origin city and destination city. “City’ is a generic term and refers to a city or
town as the case may be. The origin and destination cities would be entered as text.

The system shall now refer to the flight schedule database, referred to as ‘DB-geography’ in
section 2, and check if there is any ambiguity with the names of the cities. In case there are more than
two cities with same name as entered by the user, the system shall list all of them (with more
qualifications) and ask the user to select one of them. In case, either the origin or destination cities are
not listed in DB-geography as being directly serviced by the airline, the system shall suggest the
nearest city to which service is available, including the distance of the destination city from this
nearest city.

ADD FLIGHT

If the difference between the departure date and system date is more than 2 weeks, the system
asks the user if he would like to block or buy the ticket. The system informs the user that he can block
the ticket at no cost now. It also informs him that if he chooses to block the ticket, he should make a
final decision before 2 weeks of the departure date. The system shall send an email to the user, 3
weeks before the departure date as a reminder, in case he decides to block the ticket now.

FLIGHT REPORT

The system shall allow any user (registered or non registered) to access the details about
the arrival and departure times of a flight by requesting the user to input the flight number and
date. The system accesses DB-schedule and presents the time of arrival and departure.

BOOKING TICKET REPORT

 A user who has earlier blocked a ticket after going through the steps 3.2 through 3.4, is required
to either confirm the ticket before two weeks of the departure date or the ticket stands cancelled.

To let the user confirm a ticket, the system shall first log him on and ask for his blocking number.
Then it accesses DB-reservation and removes the check mark, which so far represented a blocked
seat. The seat is now confirmed and reserved for the user.

The system accesses DB-user and charges the price of the ticket to the credit card number of the
user. It simultaneously generates a confirmation number and displays it for the user to note down. The
ticket has been reserved. It adds the mileage of the trip (accounting for the number of travelers) to the
skymiles in his profile.