BAHADURGARH
PROJECT
SYNOPSIS
SUBMITTED TO:
BY:
SUBMITTED
Mrs .....................
.
......................
(lect. In M.C.A dept.)
Sem.
M.C.A 6th
PROJECT TITLE
AIRLINE
RESERVATION
SYSTEM
CONTENTS
Introduction
Problem definition
Need for airline system
Scope of the project
System requirement specification
System planning
DFDS ( DATA FLOW DIAGRAMS)
Conclusion
Introduction
Overview
This Project aims to model the working of an online airway reservation
system. The project has been built and tested on the Oracle database, and
uses JAVA as the programming language. JDBC was used as the interface
between the database and JAVA. 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 flight schedules across multiple stops, and multiple airports in
one city.
Handling of different kinds of schemes for frequent fliers, and for flights.
Separate profile type for officials.
Appropriate error checking.
Definitions
1. Plane type: This defines the physical type of the plane. It dictates the
capacity of first, executive, business and economy seats that a flight can
have.
2. Airport: An airport consists of a name, the city it is in, and its airport id.
3. Flight : A flight is identified by its flightid. A flight denotes an unique
plane, i.e. one which is scheduled to run at a certain time, from one place
to another. A flight runs over a set of routes.
4. Route: A route is simply a tuple of airports: (StartAirport, EndAirport),and
every route has a unique route id. A flight runs over a route only if it runs
from the startairport to the endairport, 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. Ticket : A ticket is uniquely identified by a ticketid. The ticket may be a
passenger ticket or a cargo ticket, and can be booked under a passenger
profile or a user 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, and a cargo ticket about a cargo.
6. Scheme : A scheme consists of discount percentages on various
classes awarded on certain flights, and for certain people or round trips.
Scheme ids have a type code defining what they are valid for, and a period
code showing whether they are valid as of now or no. A scheme is defined
for a flight and for a particular route.
7. Official: An official is a person who can book tickets for others, and can
find retrieve the complete list of passengers boarding a flight. An official
works at an airport.
8. Profile: A profile denotes that a person has been verified to be genuine
and can book tickets/ execute certain queries.
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 notsoobvious relationships are explained :
1. FlightRouteScheme: This is a ternary relation that says that a flight
runs over a route using a particular scheme. The scheme can be null, but
not the flight id and route id. The attributes in this include:
1. Fare for the flight between the two stops given by the route specified.
2. Any scheme valid on this flight, for this route
3. Number of booked seats on this flight, route.
4. A flag value indicating whether this is an elementary or complex route for
this flight.
2. FlightRouteTicket: 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.
3. ProfileTicket 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.
Problem Definition
The definition of our problem lies in manual system and a fully automated
system.
Manual system : The system is very time consuming and lazy . This
system is more prone to errors and sometimes the approach to various
problems is unstructured.
Technical system: With the advent of latest technology if we do not
update our system then our business result in losses gradually with time.
The technical systems contains the tools of latest computers printers, fax,
Internet etc. The systems with this technology are very fast, accurate, userfriendly and reliable.
Need of Airlines system
A few factors that directs us to develop a new system are given below -:
1) Faster System
2) Accuracy
3) Reliability
4) Informative
5) Reservations and cancellations from anywhere to anyplace
Scope of the project
This is the project to automate the work of Airline Reservation System.
Traditionally Airline Reservation System was done manually. There were a
lot of drawbacks in traditional approach. If the volume of reservations is
less then we can go with manual system but when the volume of
reservations crosses a certain level then it becomes very tough to manage
reservation system manually. If the Airline Reservation Systems operator
want to do a new reservation, he need not to find the last ticket number it
will be done and incremented automatically.
This Airline Reservation System will reduce the manpower requirement
drastically. Only one operator is required to operate the system.
System Requirement Specification
SRS is a document that completely describes what the proposed software
should do. The basic goal of requirement phase is to produce the SRS,
which describe the complete behavior of proposed software.
INRODUCTION
Purpose
The purpose of this document is to describe the external requirement for an
Airline Reservation System. It also describes the interface for the system.
Scope
This document is only one that describes the requirement of system. It is
meant for use by developer and will be the basis for validating the final
delivered system. Any changes mode to the requirement in the future
changes approval process. The developer is responsible for asking any
classification, where permission of client.
Over view of developers Responsibility
The Developer responsibilities are,
Developing the system
Installing the S/W on the client H/W
Constructing the user training that might be necessary for using the
system.
Maintaining the system for a period of one year after installation it
includes only the preventive and corrective and maintenance
Enhancement and adaptive maintenance is not including it.
This SRS provides many benefits, some of the goals it accomplishes are:-
Establishing the basis for agreement between client and supplier
on what the software product will do.
Reducing the development cost. The preparation of the SRS
forces rigorous specification before the design basis. Careful
development of on SRS can real. Inconsistencies and
misunderstanding early in development cycle, which can
considerably reduce cost.
Proving a reference for validation of the final product. The SRS
assist the client in determining if the software meets the
requirement.
Hardware and Software Requirements
Software Requirement
The minimum S/W requirements are as follows
Platform
: JAVA, Netbeans IDE
Backend
: MS Access 2007
Operating System
: Windows
Hardware Requirement
The minimum H/W requirements are as follows
Processor
: Pentium
Ram
: 256 MB
Hard disk
: 40 GB
System planning
PERT CPM
ACTIVITY
DEPENDENCY
DURATION
(A) Study
-------------------
15
(B) Analysis
Study
(C) Design
Analysis
15
(D) Coding
Design
20
(E) Testing
Design
14
(F) Implementation
Coding Testing
Total Days
Design Phase:
File Design.
Program Logic Design.
81
Development Phase:
Coding
Debugging
Testing
DATA FLOW DIAGRAM (DFD)
DFD for listing of flights
Flight
Flight file
Flight information
Display informantion
DFD for Reservation in flight
Flight file
Save record in
Passenger file
True
Taking date and flight
No from keyboard
False
False
Exit
Exit
DFD for Cancellation of Reservation
Passenger file
True
Input ticket no from keyboard
False
Exit
DFD for Cancellation of Flight
Flight file
Input flight no from keyboard
Exit
DFD for Enquiry of ticket
Passenger file
Input ticket no from keyboard
Exit
Conclusion
Though the system still containing lot of scope of improvement in it. But its
overall look and feel gives rough picture of on existing automation system.
I have take MS-Access at backhand but it has a limitation of 1 GB size .It
over data size approaches this 1gb some other database the SQL server,
oracle, can be used with ODBC to break this barrier .
