AIRLINE RESERVATION MANAGEMENT SYSTEM

A Project Report
Submitted in partial fulfillments of the
Requirements for the award of the degree of
BACHELOR OF SCIENCE (Information Technology)
By RITESH UTTEKAR / SUJIT BELHAVARE
Under the esteemed guidance of
Prof. Sumit Tripathi
(Head Of Department)

DEPARTMENT OF Information Technology

(Affiliated to University of Mumbai)

ANDHERI (EAST), MUMBAI - 400069.

DEPARTMENT OF Information Technology

 CERTIFICATE

This is to certify that the project entitled “AIRLINE RESERVATION

MANAGEMENT SYSTEM” is bonafide work of RITESH UTTEKAR
bearing seat number (T038). Submitted in partial fulfillments of the
requirements for the award of the degree of BACHELOR OF SCIENCE
(Information Technology) from University of Mumbai.

Internal Guide Coordinator

External Examiner

Date College
Seal

1
 ABSTRACT
Airline Reservation Management System is an application which is developed
for the Team and Admin of the Airline System. The system can perform various
tasks like retrieving the information of passengers, checking records of the
flights available from source to destination, check payments, add passenger
details, cancellation of the tickets,etc.

We can store information on a huge scale on the system. Various tables are
created on the database for easy and correct retrieval of data. For storing data
MySql has been used and data has been stored in tabular format in the database.

For the front end design we have used Core Java using the concept of swing
concept. To create an user-friendly and simple interface for the fetching and
retrieval of data of the users.

2
 ACKNOWLEDGEMENT
It gives me immense pleasure to present the Project on “Airline Reservation
Management System”. It would not have been possible without the kind
support of my teacher in charge Prof. Sumit Thriparthi (Head Of
Department) , under whose guidance and constant supervision the project was
brought to the present state.

I would also like to express my gratitude towards my parents for their kind
co-operation and encouragement which helped me in the completion of this
project. I am also thankful to the for giving me such an amazing opportunity
for making this project, and giving a suitable instructions and guidelines for the
project.

Last but not the least I thank my friends who shared necessary information and
useful web links for preparing my project.

Thanks again to all

3
 DECLARATION
I hereby declare that the project entitled “AIRLINE RESERVATION
MANAGEMENT SYSTEM” is done at college, has not in any case duplicated
to submit to any other university for the award of any degree.

To the best of any knowledge other than me, no one has submitted to any other
university.

The project is done in partial fulfillment of the requirement for the award of the
degree of BACHELOR OF SCIENCE (Information Technology) to be
submitted as a final semester project as part of our curriculum.

4
 Table of Contents
Chapter 1 INTRODUCTION

1.1. Introduction
6
1.2. Objectives of the project
6
1.3. Scope of the Project
7
1.4. Existing System
7
1.5. Proposed System
7
1.6. Limitations
8

Chapter 2 REQUIREMENT SPECIFICATION

2.1. HARDWARE Requirement
9
2.2. SOFTWARE Requirement
9

Chapter 3 SYSTEM DESIGN

3.1. Types of Libraries used with Description

10
3.2. Algorithm/Flow chart
10
3.3. UML Diagram
11

5
Chapter 4 TESTING METHODOLOGIES

4.1. Types of testing used

13
4.2. Test Case table (Datasets)
17
4.3. Screenshots
26
4.4. Gantt Chart
30

Chapter 5 FUTURE ENHANCEMENT

5.1. Conclusion
31
5.2. Future
31
5.3. References
31

Chapter 1 : INTRODUCTION

1.1 Introduction

Airline reservation systems (ARS) are part of the so-called passenger service
systems (PSS), which are applications supporting the direct contact with the
passenger.
An airline's direct distribution works within their own reservation system, as
well as pushing out information to the GDS. . Travel agencies and other indirect
distribution channels access the same GDS as those accessed by the airline
reservation systems, and all messaging is transmitted by a standardized
messaging system that functions on two types of messaging that transmit on
SITA's high level network (HLN). Prior to deregulation, airlines owned their
6
own reservation systems with travel agents subscribing to them. Today, the
GDS are run by independent companies with airlines and travel agencies being
major subscribers.Reservation systems may host "ticket-less" airlines and
"hybrid" airlines that use e-ticketing in addition to ticket-less to accommodate
code-shares and interlines.

1.2 Objectives of the project

⚫ Create a new employee
⚫ Delete an existing employee
⚫ Create a new Customer
⚫ Delete an existing Customer
⚫ Create a new reservation
⚫ Cancel an existing reservation
⚫ Issue a flight ticket
⚫ Payment options
⚫ List all customers known by the system
⚫ List all employees known by the system
⚫ List all reservation known by the system
⚫ List all flights known by the system
⚫ Change a employee/ customer information (name, address, etc) ability to
change ALL attributes
⚫ Change a flights information (time, source, destination etc) change ALL
attributes
⚫ Search for a employee based on attributes.
⚫ Search for a flight based on attributes
⚫ Display information about a employee
⚫ Display information about a traveler
7
⚫ Display information about a flight

1.3 Scope of the Project

The Scope of the project is to enable easy and smooth functions for the Admin
and Employees of the Airline Reservation Management System. The easiness
and the accuracy of the system will be checked. Various functions like viewing
customer details, flight details, payment details,etc will be performed by the
admin and the team as it is an admin based application for the Airline
Reservation Management System.

1.4 Existing System

The Airline Reservation Management System is an web based solution for
consolidating data from the system regarding flights, bookings, payments,etc.
The existing system is automated and the users can do all the tasks online. As a
result the time and efforts of the users are saved by the system.

1.5. Proposed System

The application we have created is whole for the staff and admin of the Airline
System. The changes in the system can only be done by Admin and the
employees of the system. The database access can also be given to the
employees by the Admin to make necessary changes in the database system. If
the entries in the database are unnecessary so the admin or employees can delete
the records to keep the system space free and have enough space for the other
entries to be inserted into the system.

8
1.6. Limitations
⚫ The system mainly focuses from the Admin point of view

⚫ Admin and selected staff will be working on the system so if there are
change in entries of data at times errors can come into picture

9
 Chapter 2 : REQUIREMENT SPECIFICATION
2.1. Hardware Requirement
Microsoft® Windows® 7/8/10 (64-bit).

4 GB RAM minimum, 8 GB RAM recommended.

2 GB of available disk space minimum, 4 GB Recommended

1280 x 800 minimum screen resolutions.

2.2. Software Requirement /Programming Language

Software used: Netbeans IDE 8.2

Front end : Java

Concept used: Java Swing

Back end : MySQL

10
 Chapter 3 : SYSTEM DESIGN

3.1 Algorithm/Flow chart/UML Diagram

Fig 3.1.1 Flow diagram for Searching Airline Website

11
 Fig 3.1.2 Flow diagram for Distribution Management

SEQUENCE DIAGRAM

A Sequence Diagram illustrates the activities using actors, objects, and messages. This
diagram gives us ideas and guides us on how should the System be built. These ideas
were applied in the UML sequence diagram to give efficiency to Student Management
System development.

12
 Fig 3.1.3 SEQUENCE DIAGRAM

Fig 3.2.4 UML diagram for Admin Functioning

13
 Chapter 4 : TESTING METHODOLOGIES

4.1 Types of testing used

Unit testing

Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at the component level and test a specific business process, application, and/or
system configuration. Unit tests ensure that each unique path of a business process performs
accurately to the documented specifications and contains clearly defined inputs and expected
results.

Integration testing

Integration tests are designed to test integrated software components to determine if

they actually run as one program. Testing is event-driven and is more concerned with
the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the

14
combination of components is correct and consistent. Integration testing is specifically
aimed at exposing the problems that arise from the combination of components.

Functional test

Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and
user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted
Invalid Input : identified classes of invalid input must be rejected
Functions : identified functions must be exercised
Output : identified classes of application outputs must be exercised
Systems/Procedures : interfacing systems or procedures must be invoked

Organization and preparation of functional tests are focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes
must be considered for testing. Before functional testing is complete, additional tests
are identified and the effective value of current tests is determined.

System Testing

System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system
testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration
points.

White Box Testing

15
White Box Testing is a testing in which the software tester has knowledge of the inner
workings, structure, and language of the software, or at least its purpose. It is a purpose.
It is used to test areas that cannot be reached from a black box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, like most other kinds
of tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing
in which the software under test is treated, as a black box .you cannot “see” into it. The
test provides inputs and responds to outputs without considering how the software
works.

Unit Testing

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be
conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives
· All field entries must work properly.
· Pages must be activated from the identified link.
· The entry screen, messages, and responses must not be delayed.

Features to be tested
· Verify that the entries are of the correct format
· No duplicate entries should be allowed
· All links should take the user to the correct page.

16
Integration Testing

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects.
The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the
company level – interact without error.
Test Results:All the test cases mentioned above passed successfully. No defects
encountered.

Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results:

All the test cases mentioned above passed successfully. No defects encountered.

17
4.3 Screenshots
Login

Mainframe

18
List Of Functions(Admin/Employees)

Flight Information

19
Adding Customer Details

Journey Details

20
Payment Details

21
 Cancellation Details

4.4 Gantt Chart

September

November

December

February
October

January
August

March
Months
July

Weeks 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Req. gathering

Planning

Analysis

Design

Code

22
 Testing

Implementation

Chapter 5 Future Enhancement

5.1 Conclusion
Through this project, the functions and tasks on Airline Reservation Management
System data can be performed successfully.

The Admin will be able to perform all the functions like adding customer details,
adding flights, viewing payment details,etc.

Here, we have tried to provide maximum information about Airline Reservation

Management System to the Admin and the employees working over the system.

23
5.2 Future Scope
The project Airline Reservation Management System as in now is only admin panel
and only admin and the employees can work on the system.

In future we can add the customer to book tickets, do payments, view flight details
from the system by logging into the system. New users can signup into the system and
can do functions related to Airline Booking System.

Then the system can be used by both admin and the customers who wants to use the
services of the application.

5.3 References
1. “Aviation and Space”. Retrieved on May 20, 2012 from Microsoft Encarta
Premium

2009 Encyclopedia.

2. “Computerized Reservation System”. Retrieved on May 14, 2012

fromhttp://en.wikipedia.org/wiki/Computer_reservations_system.htm.

3. Airline , 2012 http://www.enotes.com/topic/Airline_Reservations_System retrieved

on

23.May 2012

4. Alter, S. L. (1980). Decision support systems: current practice and continuing

challenges.

Reading, Mass., Addison-Wesley Pub.

5. C. Winston, S. Morrison (1995): "The Evolution of the Airline Industry",

Brookings

Institution Press, South Dakota, Cf. p. 61-62, Computer Reservation Systems.

6. Diane (1993) Computer Reservation Systems: “Action Needed to Better Monitor

the

CRS Industry and Eliminate CRS Biases”, DIANE Publishing Company,

24
ISBN1568069774

7. European Parliament: “More Competition in Airline Reservation System – With

Protection for Consumers,” Sept. 4, 2008 retrieved on June 6, 2012 from

http://www.ehow.com/about_5122697_airline-reservation-systems.html.

8. Finley, P. N. (1994). Introducing decision support systems. Oxford, UK Cambridge,

Mass., NCC Blackwell; Blackwell Publishers.

9. Global (2012 ) http://www.businessdictionary.com/definition/Global-Distribution-

System-GDS.html accessed on May 26, 2012

10. Henry R. Luce (2001) “The Rise of the American News Media” The Johns
Hopkins

University Press (July 12, 2001)

11. James a. O‟Brien (2001). Management information system

12. Kantar, (1997). Managing with information. 4th edition

13. M. J. Smith (2002): “The Airline Encyclopedia, 1909 – 2000”. Scarecrow Press,
New York.

14. Merril Wells (2002) “Introductory Microsoft Access 2002”

15. Nasim Zaidi (2010), Civil aviation requirements section 3 air transport series‟‟
part one issue one, April, 2010.

16. P. N. Seth, S. S. Bhat (2002): “An Introduction to Travel and Tourism”,

Prentice Hall,
London.
17. R. Doganis, C. Routledge (2001): “The Airline Business in the 21st Century.”
McGraw-
Hill, New York.
18. R. Doganis, C. Routledge (2002): “Flying Off Course: The Economics of
International
Airlines,” 3rd Edition. McGraw-Hill, New York.
19. R. E. G. Davies (1964): “A History of the World‟s Airlines”. Oxford
University Press,
London.

25
20.
ReservationInterface(2012),http://www.asppms.com/autoclerk/Products/Interfaces/
Reser
vationInterfaces/InterfacetoGDS.aspx(retrived on 23.May.2012)
21. Rochester, Jack B. (1996). "Tools for Knowledge Workers” Using Computers
in
Information. Indianapolis, IN: Que Education and Training.
22. Stair, Ralph M. (1996). Principles of Information Systems and Managerial
Approach, 2nd
ed. Cincinnati, OH: Boyd & Fraser. . [Accessed May, 19, 2012].
23. Wardell, David J, "Airline Reservation Systems", 1991. Research paper.
24. Wikipedia (2012) ,
http://en.wikipedia.org/wiki/Computer_reservations_system accessed
on May 26, 2012
25. Winston, Clifford, 1995 "The Evolution of the Airline Industry", Brookings
Institution
Press, ISBN 081575843X. Cf. p.61-62, Computer Reservation Systems

26