AKS Project Airline Reservation System
AKS Project Airline Reservation System
AKS Project Airline Reservation System
1 . I NT R O D U C T I O N :
Airline reservation systems were first introduced in the late 1950s as
relatively simple standalone systems to control flight inventory, maintain
flight schedules, seat assignments and aircraft loading. The modern airline
reservation system is comprehensive suite of products to provide a system
that assists with a variety of airline management tasks and service customer
needs from the time of initial reservation through completion of the flight.
One of the most common modes of travel is traveling by air. Customers
who wish to travel by air nowadays have a wide variety of airlines and a
range of timings to choose from. Nowadays competition is so fierce between
airlines that there are lot of discounts and a lot of luxuries given to customers
that will give an edge to that particular airline.
The World Wide Web has become tremendously popular over the last
four years, and currently most of the airlines have made provision for online
reservation of their flights.
people looking for making reservations online without the hassle of meeting
travel agents. My Project intends to serve these purposes. It intends to check
all the available airline databases and return a string of results, which can
help them in their travel plans.
The objective of this project is to create an airline reservation system
where a traveler can request all flight information as per their journey dates.
They can get information regarding time, cost, etc all at the same time and
place. When the customer calls the Counter Assistant for his/her travel
needs, the counter assistant will enter the customer's details (flight
requirements) in the system. The system displays all the available airlines,
schedules and prices. This system would help the airline to better serve its
customers by catering to their needs. The site would use a Database to hold
this information as well as the latest pricing and availability information for
the airlines.
Page |2
TECHNICAL SYSTEM
Page |3
1) Faster System
2) Accuracy
3) Reliability
4) Informative
5) Reservations and cancellations from anywhere to any place
AIRLINES SYSTEM
CANCELLATIO
N
RESERVATION
UPDATION
2. FEASIBILITY STUDY
Feasibility study is to check the viability of the project under consideration.
Theoretically various types of feasibilities are conducted, but we have
conducted three type of feasibilities explained as under.
ECONOMIC FEASIBILITY
With the manual system the operating cost of the system is about 60 Lakhs
P.A.. This cost comprises salary of 25 people, stationary, building rent,
electricity, water, telephone etc. But with the new system this reoccurring cost
comes out to be about 20 Lakhs PA. Hence the new system is economically
feasible.
TECHNICAL FEASIBILITY
The new system requires approximately 6 trained employees to work with
the system and in overall 10 people per office are sufficient. So we will
identify 6 best people from existing system and train them.
As our existing system is purely manual, so we need a one time investment
of Rs. 4 Lakhs for the purchase of 7 computers, 5 Ticket printers, a laser
printer, AC and networking etc. It requires 20 Lakhs PA as an operating cost.
With the above details our system is technically feasible as after investing
24 Lakhs in a year, the company is still saving Rs 25 Lakhs PA.
OPERATIONAL FEASIBILITY
The new solution is feasible in all sense but operationally it is not. The new
system demands the expulsion of at least 15 people from the company. It
creates an environment of joblessness and fear among the employees. It can
lead to an indefinite strike in the company also. So the management must
3 . OV E R V I E W O F T H E P R O J E C T:
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 reservation, modify reservations or cancel a particular
reservation.
The name of the software is AIRLINE RESERVATION SYSTEM. This
software provides options for viewing different flights available with different
timings for a particular date and provides customers with the facility to book
a ticket, modify or cancel a particular reservation but it does not provide the
customers with details of cost of the ticket and it does not allow the
customer to modify a particular part of his reservation and he/she can
modify all details.
3.1 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:
Error prone
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:
4. SYSTEM ANALYSIS
This is the most important phase of project life cycle. It requires the maximum
time in order to accomplish a well defined project in later stages of projects
life cycle. The block diagrams given below depict various facts which were
understood by one during the analysis phase.
BLOCK DIAGRAM
BOOKING
DEPARTMENT
RECEIVE
CUSTOME
R
REQUEST
Flight MAINTENANCE,
Booking, cancellation
PASSENGER
LIST
CONFIRMED
LIST
AIRLINE
RESERVATION
SYSTEM
PASSENGER
DATA STORAGE
Ticket reservation
Cancellation,
Request for
enquiry
REPORTS
WAITING LIST
CANCELLATION
DATA ACCESS
database
Passenger list,
Fleet info
concession
Flight
information,
Fare details,
SYSTEM COMPONENTS:
4 . 1 F R O N T E N D ( J AVA )
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.
Java from C++:
Java builds on the strength of C++. It has taken the best features of C+
+ and discarded the more problematic and error prone parts. To this, it has
added garbage collection (automatic memory management), multi threading
(the capacity for one program to do more than one thing at a time) and
security capabilities. The result is that Java is simple, elegant, powerful and
easy to use.
Java is actually a platform consisting of three components:
Components of Java:
Java is actually a platform consisting of three components:
projects
because one
can break
the things
down
into
Garbage collection.
Absence of pointers.
Java is extensible.
Java is secure.
Java is robust.
Java is multithreading.
Simplicity.
Library Classes:
The
Java
platform
includes
an
extensive
class
library
so
that
The way classes are loaded. The java byte code loader, another Part of the
virtual machine, checks whether classes loaded during program execution are
local or from across a network. Imported classes cannot be substituted for
built in classes cannot accidentally reference classes brought in over a
network.
The way access is restricted for entrusted code. The java security manager
allows user to restrict entrusted java applets so that they cannot access the
local network, local files and other resources.
4.2 MODULES:
There are 5 modules in this project.
Administrator Module.
Passenger Module.
Payment.
Cancellation.
M O D U L E S E X P L A N AT I O N :
Administrator Module.
Enables the administrator to perform all administrative functions and
manage inventory over LAN or the Internet. The administrator can define or
modify routes, fares schedules and assign or deny access for qualified
travel agents and other authorized users.
Passenger Module.
Payment.
Provides the airline with the ability to set up various travel agents and give
them reservations capabilities over the Internet. The travel agents are able to
display and offer discounted fares to passengers.
Cancellation.
The system should allow the user to cancel the existing booking. In this
cancellation very helpful in all the travelers.
5. SYSTEM DESIGN:
Use
Case
diagram
for
modeling
the
business
processes
Sequence
diagram
between objects
Collaboration
diagram
for
modeling
object
interactions
the system
Class
diagram
system.
UML is a consolidation of many of the most used object-oriented
L I S T OF F I G U R E S :
Class Diagram
Activity Diagram
Sequence Diagram
Use Case Diagram
Collaboration Diagram
5 . 1 . 1 C L A SS D I A G R A M S :
The class diagram is the main static analysis and design diagram for a
system. In it, the class structure of the system is specified, with relationships
between classes and inheritance structures. During analysis of the system, the
diagram is developed with an eye for an ideal solution. During design, the
same diagram is used, and modified to conform to implementation details.
5.1.2. ACTIVITY DIAGRAMS:
The Activity Diagram is a multi-purpose process flow diagram that is
used to model behavior of the system. Activity Diagram can be used to model
a Use Case, or a class, or a complicated method. An Activity Diagram can
show parallel processing. This is important when using Activity Diagram to
model business processes, some of which can be performed in parallel, and for
modeling multiple threads in concurrent programs.
5.1.3 SEQUENCE DIAGRAM:
The Sequence diagram is one of the most effective diagrams to model
object interactions in a system. A Sequence diagram is modeled for every Use
Case. Whereas the Use Case diagram enables modeling of a business view of
the scenario, the Sequence diagram contains implementation details of the
scenario, including the objects and classes that are used to implement the
5 . 1 . 5 C O L L A B O R AT I O N D I A G R A M :
The Collaboration Diagram presents an alternate to the Sequence
Diagram for modeling interactions between objects in the system. Whereas in
the Sequence Diagram the focus is on the chronological sequence of the
scenario being modeled, in the Collaboration Diagram the focus is on
understanding all of the effects on a given object during a scenario.
Objects are connected by links, each link representing an instance of an
association between the respective classes involved. The link shows messages
sent between the objects, the type of message passed, and the visibility of
objects to each other.
5 . 1 . 6 D ATA F LO W D I A G R A M S :
In order to design a better solution. I had designed the DFD for system including all technical
processing details is given bellow
PASSENGER
INFORMATION
1.0
GENERAL
ENQUIRY
BOOKING
ENQUIRY
NEW PNR INFORMATION
RESERVATION REQUEST
2.0
PASSENGER
ENQUIRY
3.0
BOOKING
COUNTER
CANCELLATION REQUEST
4.0
CANCELLATION
ACKNOWLEGMENT
PASSENGER
REQUEST FOR
INFOR MATION
REQUIRED
INFOR MATION
1.0
GENERAL
ENQUIRY
R
E
Q
U
E
S
T
I
N
F
O
R
M
A
T
I
O
N
R
E
Q
U
E
S
T
FLIGHT
T
I
O
M
1.2
FARE
ENQUIRY
E
Q
U
E
S
T
I
N
F
O
R
M
I
N
F
O
R
M
A
T
I
O
1.1
FLIGHT
ENQUIRY
1.3
DISCOUNT
FARE
DISCOUNT
15
PASSENGER
ENTRY OF NEW RECORD OR EXISTING
PASSENGER ENQUIRY
PASSENGER
ENQUIRY
U
N
I
Q
U
E
P
N
R
R
E
Q
U
E
S
T
R
E
Q
U
E
S
T
I
N
F
O
NEW
2.2
PASSENGER
PASSENGER
ENQUIRY
UNIQUE
PNR
PASSENGER
INFORMATION
PASSENGER
<<include>>
login
validate user
maintain user details
select dates
select cities
<<include>>
<<in clude>>
<<include>>
user
select the flight type
<<include>>
bookticket
<<extends>>
cancel ticket
<<include>>
return money
payament
adminstrator
login
user
search flight
database
system
select ticket
user database
book flight
cancel ticket
airline database
5 . 2 D ATA D I C T I O N A RY:
5.2.1 INTRODUCTION:
D I C T I O N A RY The logical characteristics of current system
data stores including Name, Address, Flight code, Source, Destination,
Airline code, Flight code, Credit card number, Payment amount etc
identifies process where the data are used and where immediate
access to information required, Serves as the basis for identifying
database requirements during system design.
Uses of Data Dictionary:
5 . 2 . 2 D ATA D I C T I O N A RY:
1. Cancellation.
This table is used to store the cancel details.
Field name
cancelid
reservationid
Description
Cancellation id
Reservation id
cancelationdate Date of
refundmoney
Cancellation
Money to be
Data type
int
int
Size
10
10
date
decimal
Constraints
PRIMARY KEY
FOREIGN KEY
NOT NULL
10,0
NOT NULL
refundable
2. Classes
This table is used to store the class details.
Field name
Classid
flightcode
classcode
classname
Description
Id of the class
Name of the
Data type
int
int
varchar
varchar
Size
10
10
50
50
constraints
PRIMARY KEY
FOREIGN KEY
NOT NULL
NOT NULL
decimal
int
10,0
10
NOT NULL
NOT NULL
class
Fare
totalclassseat
Total seats in a
class
3 . F l i g h t d ay s
This table is used to store the flight days details
Field name
datecode
Description
Code of the date
Data type
int
Size
10
constraints
PRIMARY KEY
flightcode
Date
departure
flight departure
Code of the flight
date
Departure time
int
date
time
10
FOREIGN KE
NOT NULL
NOT NULL
4. Flight details
This table is used to store the flight details.
Field name
flightcode
airlinecode
flightname
source
Description
Code of the flight
Code of the airlines
Name of the flight
Starting place of the
Data type
int
varchar
varchar
varchar
Size
10
100
100
100
constraints
PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
destination
flight
Destination of the
varchar
100
NOT NULL
totalcapacity
flight
Total capacity of the
int
10
NOT NULL
Size
50
50
constraints
PRIMARY KEY
NOT NULL
flight
5. Login
This table is used to store the login details
Field name
username
password
Description
Name of the user
Password for the
user login
Data type
varchar
varchar
6. New User
This table is used to store the new user details.
Field name
Userid
Firstname
Description
Users id
First name of the
Data type
int
varchar
Size
10
250
constraints
PRIMARY KEY
NOT NULL
lastname
user
Last name of the
varchar
250
NOT NULL
middlename
user
Middle name of the
varchar
250
NOT NULL
mobileno
Dob
address
City
State
country
emailid
password
usertype
username
user
Mobile number
Date of birth
Mail id
Type of the user
Name of the user
int
date
varchar
varchar
varchar
varchar
varchar
varchar
varchar
varchar
10
250
250
250
250
250
250
250
250
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
UNIQUE KEY
7 . Pa s s e n g e r
This table is used to store passenger details.
Field name
passengerno
Description
Number of the
Data type
Int
Size
10
constraints
PRIMARY KEY
flightcode
Dob
address
passengers
Code of the flight
Date of birth
-
Int
Date
varchar
10
FOREIGN KEY
NOT NULL
NOT NULL
250
nationality
Name
Gender
phoneno
emailid
passportno
reservationid
varchar
varchar
varchar
varchar
varchar
Int
Int
250
250
250
250
250
10
10
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
FOREIGN KEY
8. Payment
This table is used to store payment details
Field name
paymentid
checkno
creditcardno
paidamount
paymentdate
passengerno
Description
Checking number
-
Data type
Int
Int
Int
decimal
date
Int
Size
10
10
10
10,0
10
constraints
PRIMARY KEY
NOT NULL
NOT NULL
NOT NULL
NOT NULL
NOT NULL
9. Reservation
This table is used to store reservation details.
Field name
reservationid
flightcode
journeydate
Source
Description
Starting place of the
Data type
Int
Int
Date
varchar
Size
10
10
50
constraints
PRIMARY KEY
FOREIGN KEY
NOT NULL
NOT NULL
destination
flight
Ending position of
varchar
50
NOT NULL
Status
journeytime
the flight
Time the flight
Int
time
10
NOT NULL
NOT NULL
starts
10. Reserve check
This table is used to store reserve check details
Field name
reservationid
Description
Reservation id
Data type
Int
Size
10
username
Password
number
Name of the user
Password to login
Varchar
Varchar
250
250
constraints
PRIMARY KEY
6 . I M P L E M E NTAT I O N :
Modules of this project consist of :
1) Main Form
2) Login Form
3) Domestic Flight booking
4) International Flight booking
5) Economic Class Traveling
6) Business Class Traveling
7) Print Ticket Form
1. Main form:
7. Console Output:
7. TESTING:
7.1 Introduction:
System Development is a process of conceiving the specification
specified in the designing stage into source code. Careful study and
observation about system designing were made and accordingly the
system was coded to convert from designing to source code, where
Java as the frontend. The System was developed such that it should be
used for the future enhancement.
All the module of the system is combined and is put to the
operational use. This means that the new and old system are run in the
parallel for sometimes, errors are identified and the corresponding
errors are to be concerned to get the required output.
The set of working programs and initialized tables are also provided for
the easy start of the user, in addition, system documentation is also
provided, and all users have been trained to use the system.
This creates two problems,
7.2
Types
of
testing:
7.2.1Unit
Testing:
Unit test is designed to ensure that the purpose for
which it was designed for which it was designed for is
fulfi lled. Each and every module was tested individually with
the
test
data
and
error
messages
were
displayed
for
incorrect and suffi cient for entry works. All validation was
tested to correctness. Test data were fed in and results were
checked for the maintenance module, to ensure that all
tables created contained nothing but valid data. Reverential
integrity constraints specifi ed as part of the table defi nition
was also tested.
7.2.2 Integration Testing:
In integration testing a system consisting of diff erent
modules
is
tested
for
problems
arising
from
component
integrated
and
tested.
In
my
project
have
done
7.2.3
Recovery Testing:
7.2.4
Security Testing:
7.2.5
Performance Testing:
7.2.6
test
can
be
conducted
to
ensure
that
internal
components
and
loops.
Using
white-box
testing
software
8. CONCLUSION:
The entire project has been developed and deployed as
per the requirements stated by the user, it is found to be bug
free as per the testing standards that are implemented. And
by specifi cation-untraced errors concentrated in the coming
versions, which are planned to be developed in near future.
Finally, we like to conclude that we put all our eff orts
throughout the development of our project and tired to fulfi ll
most of the requirements of the user.
9. REFERENCE:
Websites
http://www.google.com
http://www.microsoft.com
http://www.programmer2programmer.net
http://www.codeproject.com
http://www.slideshare.net
http://www.1000projects.com
http://www.firstload.com
Books
Database Development