AIRLINE RSERVATION SYSTEM

A MAJOR PROJECT REPORT

Submitted by
MUSHFIQ AHMED
(2014-301-047)

in partial fulfillment for the award of the degree of

BACHELOR OF COMPUTER APPLICATIONS

Under the supervision of

Dr. SHERIN ZAFAR

Department of Computer Science & Engineering

JAMIA HAMDARD
(Hamdard University)
New Delhi-110062

(2017)

DECLARATION
I, Mr. MUSHFIQ AHMED a student of BACHELOR OF COMPUTER
APPLICATIONS(BCA),(Enrolment No: 2014-301-047)hereby declare that
the dissertation entitled AIRLINE RESERVATION SYSTEM which is
being submitted by me to the Department of Computer Science and
Engineering, Jamia Hamdard, New Delhi in partial fulfillment of the requirement
for the award of the degree of BACHELOR OF COMPUTER(BCA), is my
original work and has not been submitted anywhere else for the award of any
Degree, Diploma, Associate ship, Fellowship or other similar title or recognition.

MUSHFIQ AHMED

Date: 15.05.2017
Place: NEW DELHI
 ACKNOWLEDGMENT

I have a great pleasure in presenting this project report on AIRLINE RESERVATION

SYSTEM and to express our deep regard to towards those who have offered their valuable
time & guidance in my hour of need.

Firstly, I would like to express my sincere gratitude to Mentor, the guide of the project who
carefully and patiently leant his valuable time and effort to give directions as well as to
correct various documents with attention and care. It is a great honor to do this project in this
esteemed institution, and i would extend my thanks to Dr. SHERIN ZAFAR, who helped me
in the best way possible.

I would also like to appreciate the consideration of the Project Coordinator, our Faculties and
colleagues, which enabled us to balance our work along with this project. It was their attitude
that inspired us to do such an efficient and apposite work.

I wish to avail this opportunity to express a sense of gratitude and love to all our friends and
our family for their unwavering support, strength, help and in short for everything they have
done during the crucial times of the progress of our project.
 CONTENTS

Page no

1. INTRODUCTION

1.1 Introduction of (ARS) 1

1.2 Objective 1

1.3 Problem Statement 2

1.3.1 Limitation of the manual system 3

1.3.2 Proposed system 3

1.4 Methodology/planning of work 3

2. SYSTEM REQUIREMENT

2.1 Hardware and Software Requirement

2.1.1 Hardware Requirement 6

2.1.2 Software Requirement 6

2.2 Front End (Java)

2.2.1 Overview of Java 6

2.2.2 Object Oriented 7

2.2.3 Java Feature 7

2.2.4 JDBC 7

2.2.5 Requirement to use JDBC 8

2.2.6 JDBC Driver 8

2.3 Back End (My SQL)

 2.3.1 Introduction to MYSQL 9

2.3.1 Access of data (MY SQL) 9

2.3.2 Features of MY SQL 10

3. SYSTEM DESIGN 11

3.1 Data Flow Diagram 12

3.2 ER-Diagram 14

3.2.1 ER-Diagram (Admin) 15

3.2.2 ER-Diagram (User) 18

4. SYSTEM IMPLEMENTATION

4.1 Screen Shots of Tables 20

4.2 Screen Short of Output 24

5. CONCLUSION & SCOPE 37

6. BIBLIOGRAPHY 38
1.1 INTRODUCTION

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.

1.2 Objective

The objective of this project is to implement the airline reservation system to the best
satisfaction of the customer. The normal process which was followed until recently was too
manually to fill the data and then process the data which used to cause a lot of inconvenience
to both the administrator and the customer as well. Now, we would like to use databases to
facilitate this process of smooth reservation of airline tickets with minimal work on the part
of both the customer and the administrators involved.
The various aspects of the Airline Reservation System can be presented in views of the
different people involved with it. The main people involved in the airline reservation are
1. Administrator
2. Customer

1. Administrators view:-

The administrator needs to know and control the following information at all times

1) Total Number of seats per flight and seats available (1st and 2nd classes if applicable)

2) Number of reservations per flight (1st and 2nd classes if applicable)

3) Schedule of all flights in a day and flights which have arrived

1
 4) Schedule of a particular flight in a week.

5) List of passengers who are in the waiting list for a given flight

6) Information of each traveler with flight number.

2. Customers view:-

A customer needs to know the following information:

1) Availability of flights to the destination from the departure.

2) Reservation status for a particular flight.

3) Ticket price and the Concessions.

5) Status i.e., if the ticket has been confirmed or still in waiting list

1.3 PROBLEM STATEMENT

Online ticket reservation application is to maintain flight details, flight status, reservation,
cancellation process. The flight status which maintain flight ID, flight name, arrival time,
departure time and also it contain details about the seats such business class seats, economic
class seats. The flight detail contains the details about needed flight name as well as the
details about the seats. Flight reservation which contains the flight ID, ticket number,
passenger name, destination, flight name, business and economic class seats, travel charge,
passport number, date of travel are reserved. Then the cancellation process is also carried out.
Finally a report is generated about flight details, flight status, and reservation and cancellation
tickets.

2
1.3.1 Limitation of the manual system
The limitations of the manual system are:
1. Only few bookings could be made due to manual operation.
2. It takes enormous amount of time for recording transactions.
3. Requires a large amount of manual labourers.
4. Customers should go to ticket offices to reserve a ticket and cancel it.

1.3.2 Proposed system

In order to overcome the drawbacks in the manual system, it was decided to create a system,
which is integrated, reliable, consistent, flexible and secure. This system helps in speedy
information retrieval. Responds to various queries made at the different levels of
management. The system is Menu driven and user friendly with attractive html interface. It
assists the user with respective messages to overcome the errors at runtime. The system is
designed in such a way that the reservation list is available on time before the scheduled
departure time. The reservation list reflects the latest status with respect to the cancellation of
tickets that helps the wait-listed passenger in knowing their present status. In the new system
customers could reserve and cancel tickets from anywhere which have an internet access.

1.3 METHODOLOGY/PLANNING OF WORK

The development process adopted is a waterfall model. The waterfall model proceeds from
one phase to the next in a sequential manner. First we complete requirements specification
based on our analysis. We then plan on exactly what has to be achieved at the end of the
project. We then proceed to the design phase where we determine how the goals set for there
going to be met and how the deliverables are going to be achieved. This will be done by
making a blueprint for the design phase to help the group members have a fair idea of what is
expected of the system and what should be included in it and what should not.

3
The sequential phases in Waterfall model are:

Requirement Gathering and analysis: All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification
doc.

System Design: The requirement specifications from first phase are studied in this
phase and system design is prepared. System Design helps in specifying hardware and
system requirements and also helps in defining overall system architecture.

Implementation: With inputs from system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit Testing.

Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

4
 Deployment of system: Once the functional and non-functional testing is done, the
product is deployed in the customer environment or released into the market.

Maintenance: There are some issues which come up in the client environment. To fix
those issues patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the
defined set of goals are achieved for previous phase and it is signed off, so the name
"Waterfall Model". In this model phases do not overlap.

1.3.1 Waterfall Model Advantage and Disadvantage

Advantage
The advantage of waterfall development is that it allows for departmentalization and control.
A schedule can be set with deadlines for each stage of development and a product can
proceed through the development process model phases one by one.

Development moves from concept, through design, implementation, testing, installation,

troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order.

Disadvantage
The disadvantage of waterfall development is that it does not allow for much reflection or
revision. Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-documented or thought upon in the concept stage.

5
2. SYSTEM REQUIREMENT

2.1 Hardware and Software requirements

For the implementation of the project the minimum Hardware & Software requirements are
as follows:

2.1.1 Hardware Requirements:

PROCESSOR : 32 BIT, Pentium IV

RAM : 256 MB
HARD DISK : 40 GB
CLOCK SPEED : 266 MHz
FLOPPYDRIVE : 1.44 MB

2.1.2 Software Requirements:

OPERATING SYSTEM : Windows 2000/XP.

Language/Technologies (Front End) : JAVA OR VB
MIDDLEWARE : J2EE
BACK END : My SQL

2 . 2 F R O N T E N D ( J AVA)

2.2.1 Overview of Java:

Java is a powerful but lean object oriented programming language. It has generated a lot of
excitement because it makes it possible to program for Internet by creating applets, programs
that can be embedded in wed page. The context of an applet is limited only by ones
imagination. Applets can be just little decorations to liven up web page, or they can be serious
applications like word processors or spreadsheet. But Java is more than programming
language for writing applets. It is becoming so popular that many people believe it will
become standard language for both general purposes and Internet programming.
6
2.2.2 Java is Object Oriented:
The Java programming language is object oriented, which makes program design focus on
what you are dealing with rather than on how you are going to do something. This makes it
more useful for programming in sophisticated projects because one can break the things
down into understandable components. Reusability of these components is another big
benefit Object oriented languages use the paradigm of classes. In simple terms, a class
includes both the data and the functions to operate on that data. Object is an instance of the
class forms the actual run time entity of the class. Encapsulation of code and date makes it
possible it make the changes in code without breaking other programs that use that code.
Java includes inheritance, or the ability to derive new classes form existing class referred to
as the parent class. A subclass can add new data members to those inherited form the parent
class. As far as methods are concerned, the subclass can reuse the inherited methods as it is,
change them, and its own new methods.

2.2.3 Javas exciting features are:

Ease in code correction.

Garbage collection.
Absence of pointers.
Java is extensible.
Java is secure.
Java is robust.
Java is multithreading.
Simplicity.

2.2.4 JDBC

JDBC is a java TM API for executing SQL statements.

It consists of a set of classes and interfaces written in the java programming language
that makes it easy to send SQL statements to virtually any relational databases.
JDBC (Java Database Connectivity) is a front end tool for connecting server to ODBC

7
 in that respect.
JDBC is essentially a low-level application programming interface. It is called as low-
level API since any data manipulation, storage and retrieval has to be done by the
program itself. Some tools which provide a higher-level abstraction of, expected
shortly.
The combination of java and JDBC lets a programmer write it once and run it anywhere.

2.2.5 Requirem ents to use JDBC:

To use JDBC we need a basic knowledge of database and SQL.

We need the jdk1.1 (Java Development Kit 1.1 available Java Softs website) or a
version of java since jdk1.1 and above come bundled with JDBC software.
A back-end database engine for which a JDBC driver is available. When JDBC
drivers area not available JDBC-ODBC bridge drivers are used to access the database
through ODBC.
Back-end is not needed when JDBC driver is capable of storing and retrieving the
data itself, or if JDBC-ODBC Bridge and the ODBC driver can be used to store and
retrieve the information.

2.2.6 JDBC Drivers:

The JDBC API founds in java.sql package, consists only a few concrete classes. Much of the
API is distributed as database-neutral interface classes that specify behavior without
providing any implementation. The actual implementations are provided by third-party
vendors.
An individual database system is accessed via a specific JDBC driver that implements the
java.sql. Driver interface. Drivers exist for nearly all popular RDBMS systems, though few
are available for free. Sun bundles a free JDBC-ODBC bridge driver with the JDK to allow
access to standard ODBC data sources, such as a Microsoft Access Database.
However, Sun advises against using the bridge driver for anything other than development
and very limited deployment. Servlet developers in particular should need this warning
because any problem in the JDBC-ODBC bridge drivers native code section can crash the
entire server, not just your servlets.

8
2.3 BACK END (MY SQL)

2.3.1 Introduction to MYSQL

Modern relational database management systems can perform a wide range of tasks. It has
got the following advantages-

Define a database
Query the database
Add, edit and delete data.
Modify the structure of the database
Secure data from public access.
Communicate within networks
Export and import data

MySQL is one such RDBMS. It provides a set of functional programs that we use a tool
to build structure and performs tasks, in MySQL data is stored and displayed in tables. A
table is a data structure that holds data in a relational database. A table comprises of rows
and columns. Table can also show relationship between entities. The formal name of
table is relation, hence the name Relational Database Management System.

2.3.2 Access of data in MySQL

SQL is a structured query language that we use to communicate with mysql. It consists of a
set of English words like Select, Create etc. The standard set of SQL command fall into the
following category-

Queries using select clause

9
 Data definition language (DLL) commands which are for creating and altering the

structure of database.

2.3.3 Salient Features of MySQL

Open Source
Efficient multi-user support and consistency
Powerful security feature
Fault tolerance
Ease of administration
Application development tools
Networking
SQL compatibility

10
3. SYSTEM DESIGN

Software design is a process through which requirements are translated in to a representation

of software. Initially the representation depicts a holistic view of software. Subsequent
refinement leads to a design representation that is very close to source code.

Since, we are following an Object oriented Design technique, the next step towards the
development is to identify the classes and their relationships. A class is a description of an
object type. Instances of classes are known as Objects. UML also provides tools for designing
the system. Class diagrams enable us to establish relationship among various classes of the
system. Before proceeding on to develop class diagrams, the next step is to identify the
potential classes in the system. Some of the basic tips in identifying the classes are:

Analyzing the requirement statement.

Use Cases.
Application experts.
Studying the system.

By following these simple rules during the initial process of analyzing, several classes get
formulated. These classes are referred to as candidate classes and they represent the possible
classes in a given system. It is not essential to incorporate all the identified candidate classes;
some of them may also be dropped and are called unfit candidate classes.

A class icon is a rectangle with three sections in it. Horizontal lines across the rectangle
divide the sections. The first section is where the class name is mentioned. In the second
section the attributes or data members of the class and in the third section the methods or
functions of the class are mentioned. A class diagram thus takes the form

In DFD the cardinality or multiplicity can be expressed at the ends of the association at the
class where it is applicable. Whenever there is no mention of the cardinality then one is
considered.

11
With the help of DFD, we designed the class diagram of our system, which looks like the
following. The cardinality among the relationship is also mentioned.
3.1 DATAFLOW DIAGRAMS

The Data flow diagram can be explained as the separate levels indicating the individual
complexity in the each level of the system and gives a detailed explanation in the further
levels that are following them.

LEVEL 0

Initially in the first level of the Data flow the level 0 explains the basic outline of the system.
The end-user sends the packets to the system to determine the source and destination address.
The diagram marked as the 0 represents the complete Packet watching system which simply
represents the basic operation that is being performed by it in the initial level.

LEVEL 1

The level 1 of the Data flow diagram given explains in detail about the Packet watching
system which was marked as 0 in the previous level. In this level the end-user who passes the
request for the system enters into the first process, the capturing process and then to the
processing module. After processing the packets it was send for storing.

LEVEL 2

The level 2 provides the clear explanation about the whole system. In this level first we have
to select the packet and perform test over that selected packets. Then identify the end address
of the packet and send that packet for processing. After processing the packet it was send to
the identity content. Then send the processed packet for storing and display the source and
destination addresses.

12
DATA FLOW DIAGARAMS

O-LEVEL DFD

Login
User
Admin

1-LEVEL DFD

13
3.2 ENTITY RELATIONSHIP DIAGRAM
An entity-relationship diagram (ERD) is a graphical representation of an information system
that shows the relationship between people, objects, places, concepts or events within that
system. An ERD is a data modeling technique that can help define business processes and can
be used as the foundation for a relational database.

1. One-to-One
One instance of an entity (A) is associated with one other instance of another entity (B). For
example, in a database of employees, each employee name (A) is associated with only one
social security number (B).

2. One-to-Many
One instance of an entity (A) is associated with zero, one or many instances of another entity
(B), but for one instance of entity B there is only one instance of entity A. For example, for a
company with all employees working in one building, the building name (A) is associated
with many different employees (B), but those employees all share the same singular
association with entity A.

14
3. Many-to-Many

One instance of an entity (A) is associated with one, zero or many instances of another entity
(B), and one instance of entity B is associated with one, zero or many instances of entity A.
For example, for a company in which all of its employees work on multiple projects, each
instance of an employee (A) is associated with many instances of a project (B), and at the
same time, each instance of a project (B) has multiple employees (A) associated with it.

3.2 E-R DIAGRAM

3.2.1 Admin

(Figure 1 E-R Diagram of Admin)

Continue

15
 (Figure 2 E-R Diagram of Admin)

Continue

16
 (Figure 3 E-R Diagram of Admin)

3.2 E-R DIAGRAM

17
3.2.2 User

(Figure 4 E-R Diagram of User)

Continue

18
 (Figure 5 User)

(Figure 6 E-R Diagram of User)

4. SYSTEM IMPLEMENTATION

19
4.1 Screen Shots of Tables

1.

(Figure 7 Screen Shot of Customer Details)

2.

(Figure 8 Screen Shot of Destination)

3.

20
 (Figure 9 Screen Shot of Employee Table)

4.

(Figure 10 Screen Shot of Flight Details)

5.

(Figure 11 Screen Shot of Pay Credit)

6.

21
 (Figure 12 Screen Shot of Payment)

7.

(Figure 13 Screen Shot of Source Table)

8. Treser

22
 (Figure 14 Screen Shot of Treser)

(Figure 15 Screen Shot of Treser)

Scree Shots of Output

23
1. Login

(Figure 16 Screen Shot of Login)

2. Display

24
 (Figure 17 Screen Shot of Display)

3. Customer Details

(Figure 18 Screen Shot of Customer Detail)

25
4. View Customer

(Figure 19 Screen Shot of View Customer)

5. Flight Information.

(Figure 20 Screen Shot of Flight Info)

6. Ticket Reservation

26
 (Figure 21 Screen Shot of Ticket Reservation)

7. Payment Details

(Figure 22 Screen Shot of Payment Details)

8. Ticket Enquiry

27
(Figure 23 Screen Shot of Ticket Enquiry)

28
9. Ticket Cancellation

(Figure 24 Screen Shot of Ticket Cancellation)

10. Update Customer

29
 (Figure 25 Screen Shot of Update Customer)

11. Add Flights

30
 (Figure 26 Screen Shot of Add Flight)

12. Update Flights

31
 (Figure 27 Screen Shot of Update Flight)

13. Flight List

32
 (Figure 28 Screen Shot of Flight List)

14. Registration List

(Figure 29 Screen Shot of Registration List)

15. Booking list

33
 (Figure 30 Screen Shot of Booking List)

16. Add Source

(Figure 31 Screen Shot of Add Source)

17. Add Destination

34
 (Figure 32 Screen Shot of Add Destination)

18. Add Employee

(Figure 33 Screen Shot of Add Employee)

19. Change Password

35
 (Figure 34 Screen Shot of Change Password)

20. Delete Employee

(Figure 35 Screen Shot of Delete Employee)

SCOPE AND CONCLUSION

36
This Project is not only restricted to Computer Reservation Systems (ARSes), but also other
systems dedicated to the optimal performance in the airline industry; airline agencies and
their customers inclusive. The outcome of this study will provide a basis for developing the
appropriate approach to the problems associated with air travelling operations in relation to
Airline Reservation Systems. This presentation will be beneficial to all those who make use
of Airline Reservation Systems (ATRSs), flight operators, air travelling operators, travel
agents and airline agencies. The project is aimed at exposing the relevance and importance of
Airline Reservation Systems (ARS). It is projected towards enhancing the relationship
between customers and airline agencies through the use of ARSs, thereby easing the flight
ticketing and selling process and all air traveling operations the airline reservation system
project is just another attempt to stimulate the basic concepts of airline reservation system.
The system follows a simple process which allows the passenger to check availability of
flights by entering the two travel cities, namely the Departure city and Arrival city. Once
this is done if the seats are available the system asks the customer to enter his details such as
name, address, city, state, credit card number and contact number. Then it checks the validity
of card and book the flight and update the airline database and user database.

37
BIBLIOGRAPHY

Various sites referred to during making of the project are as follows:

www.wikipedia.org

www.google.com

www.w3cschools.com

Various books are referred are as follows:

Professional Java Programming by Brett Spell.
Programming with Java by E. Balaguruswamy.
HTML 5 Black Book by Cogent Learning
Structured Query Language (SQL) by Ivan Barros
.

38