Flight Reservation System The “flight reservation system” project is an attempt to stimulatethe basic concepts of flight reservation system. The system enables the Passenger to do the things such as find for flight 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 provide a facility to the flight passenger to find 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 shows all the flight’s details such as flight number, flight name, flight price and flight duration of journey .System display list of available flights and permit Passenger to choose a particular flight. Then the system checks for the availability of seats on the flight. If the seats are available then the system provides the functionality the passenger to reserve a seat. If seats are not available then it asks the user to choose another flight. To reserve a flight the system asks the Passenger to enter his details such as name, address, city, state, card number (like credit /debit) and contact number. Then it checks the validity of card and reserved the flight and alters the flight database and user database. The system also permits the Passenger to cancel his/her reservation. INPUT /Out Put APPLICATION Proto type for login system: Proto type for registration: Prototype for finding flight: Prototype for flight details: Prototype for reservation: Prototype for cancel ticket: ANALYSIS 2. REQUIREMENT ELICITATION: Requirement number Detail Type Priority Requirement-1 The user will be able to find for flights through a Normal screen. Functional Require Requirement-2 Administrator maintains the user details and the flights details in the database. Non functional Require Requirement-3 Through a Normal flight find function the passenger will be able to find one-way, round trip or multi destination flights. Functional Require Requirement-4 The passenger should able to specify the departure, arrival places and date of their flight. Functional Require Requirement-5 By advanced flight find function the passenger will allow the passenger to specify a proffered flight by its number or its name Functional Could have Requirement-6 The user will have the choice to select the either non-stop, single stop or multi-stop flights. Functional Require Requirement-7 The passenger can only find for a flight in the future and with in only one year of current date. Functional Require Requirement-8 Any error in entry of the system will stop the system from processing the find. error message will be Functional Require Requirement-9 The passenger will be able to see the price, duration of travelling, departure time and arrival time. Functional Require Requirement-10 Passenger will able to specify the flight class which will ...

1. Flight Reservation System
The “flight reservation system” project is an attempt to
stimulatethe basic concepts of flight reservation system. The
system enables the Passenger to do the things such as find for
flight 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 provide a facility to the flight passenger to find 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 shows all the flight’s
details such as flight number, flight name, flight price and flight
duration of journey .System display list of available flights and
permit Passenger to choose a particular flight. Then the system
checks for the availability of seats on the flight. If the seats are
available then the system provides the functionality the
passenger to reserve a seat. If seats are not available then it
asks the user to choose another flight.
To reserve a flight the system asks the Passenger to enter his
details such as name, address, city, state, card number (like
credit /debit) and contact number. Then it checks the validity of
card and reserved the flight and alters the flight database and
user database. The system also permits the Passenger to cancel
his/her reservation.
INPUT /Out Put APPLICATION
Proto type for login system:

2. Proto type for registration:
Prototype for finding flight:
Prototype for flight details:
Prototype for reservation:
Prototype for cancel ticket:

3. ANALYSIS
2. REQUIREMENT ELICITATION:
Requirement number
Detail
Type
Priority
Requirement-1
The user will be able to find for flights through a Normal
screen.
Functional
Require

4. Requirement-2
Administrator maintains the user details and the flights details
in the database.
Non functional
Require
Requirement-3
Through a Normal flight find function the passenger will be
able to find one-way, round trip or multi destination flights.
Functional
Require
Requirement-4
The passenger should able to specify the departure, arrival
places and date of their flight.
Functional
Require
Requirement-5
By advanced flight find function the passenger will allow the
passenger to specify a proffered flight by its number or its name
Functional
Could have
Requirement-6
The user will have the choice to select the either non-stop,
single stop or multi-stop flights.
Functional
Require
Requirement-7
The passenger can only find for a flight in the future and with
in only one year of current date.
Functional
Require
Requirement-8
Any error in entry of the system will stop the system from
processing the find. error message will be

5. Functional
Require
Requirement-9
The passenger will be able to see the price, duration of
travelling, departure time and arrival time.
Functional
Require
Requirement-10
Passenger will able to specify the flight class which will be
with respect to the flight select.
Functional
Could have
Requirement-11
The passenger will be able to choose the seats from the list of
available seats of define flights.
Functional
Require
Requirement-12
The passenger must complete all the necessary steps to reserve
flight
Functional
Require
Requirement-13
After reserving the flight the user may cancel or altering their
flight.
Functional
Require
Requirement-14
Response time of the flight reservation system must be less than
5 sec most of time.
Non functional
Shall have
Requirement-15
System shall be able to handle atleast 9999 transactions per
second.
Non functional

6. Shall have
Requirement-16
System should be available 24x7.
Non functional
Require
Requirement-17
System shall always provide real time information about flight
availability information.
Non functional
Require
Requirement-18
The web interface should be interactive and easily navigable
passenger should be able to understand the menu and choices
provided by system
Nonfunctional
Require
Requirement-19
Users need to authenticated before having access to any
personal data
Non functional
Require
Requirement-20
System shall authenticate the passenger cards (credit/debit) and
their personal information.
Functional
Require
Requirement-21
Support for waiting list functionality.
Functional
Shall have
Requirement-22
The ars shall be able to handle the situation where flight
services are available to multiple cities or a single city.
Functional
Could have
Requirement-23

7. Only the system administrator that the right to change the
system parameters.
Non-functional
Shall have
Requirement-24
Reservation should be robust enough to have a high degree fault
tolerance.
Non-functional
Shall have
3. System Requirement Description
HARDWARE:
PROCESSOR : PENTUIUM IV 2.6 GHz
RAM :512MB DD RAM
MONITOR : 15” COLOR
HARD DISK :250 GB
CDDRIVE : LG52X
KEYBOARD : NORMAL 102 KEYS
MOUSE :OPTICAL MOUSE
SOFTWARE:
FORNT END : J2EE, HTML, JSP
BACKEND : ORACLE 11g
OPERATING SYSTEM : Independent
Entity Relationship Diagram

8. Booker
Need
Airways(Flight)))
Pays
Payment
Client
Need
Have
Booking
Issue
Ticket

9. Login
DATA FLOW DIAGRAM
Zero Level DFD
DETAILED DFD
Flight
Reservation
Process
Customer
Flight_Master
Ticket Cancellati-on Process

10. Client
Daily Flight Report Process
Report Generation Process
Flight Report
Client Report
Daily
Report Process
Daily Client Report Process
Client
Report
MODULARIZATION

11. Below are the different modules used in the project. It contains
different features a particular module support. All these
modules are independently developed and are integrated later.
Administrator roles are developed after all the forms are
developed so that back end word can be seen easily various
modules used are:
There are five modules in the systems
1. Admin_login
2. Ticket
3. Tools
4. Report
1. Admin_login
This module contains two sub modules.
Admin_login
Description: This submodule is used to logging in the project.
Without Admin_login we can’t use the use the facilities of the
software. The existing can using this system by entering
username and password. Each user has unique Admin_login id
and password provided. They can only identify with these
values on Admin_login module.
Inputs: Administrator id and password and other inputs are
according to the task performed.
Outputs: The form is validated and options for performing
various tasks are displayed.
Validations: No required field should be left empty.
Attribute: Administrator id , Password
Exit
This option is used for exit from the system.
2. TICKET

12. This module contains three submodules.
2.1 Booking
Description: This submodule is used for the Booking of Flight.
It contains the Ticket no., Flight Name, Flight Number, fare and
all the personal detail of the client.
Input: Flight name, Required seats, Fare and Personal
information of the Flight Reserver e.g. Name, Age, Address
Output: Shows options for inserting the Flight Description,
Client Personal Information.
Validation: No Ticket Number, Flight Name, Required Seat,
Fare and Name, Address of Client Field should left empty.
Attributes: Ticket number, Flight Name, Flight Number, Fare,
Name of Client, Address.
3.2 Fligh_Cancellation
Description: This submodule is used for the Fligh_Cancellation
of the booked Flight tickets. It contains the Ticket no, Flight
name, journey date and the personal detail of the client.
Input: Ticket number, Journey Date, Flight Name, Clients
Personal Information and Options for performing various task
is displayed.
Output: Display options required for Fligh_Cancellation of a
booked Ticket e.g- Ticket Number, Flight Name, Name of
Clients, Address of Client.
Validations: No Ticket Number, Journey Date, Flight Name,
Name of Client fields should left empty.
Attributes: Ticket Number, Flight Name, Flight Number, Fare,
Name of Client, Address.
3. TOOLS
This module contains one submodule.
4.1 Add/Remove Flight

13. Description: This Submodule is used for Adding, New Flight,
Deleting the existing Flight, modify the Details about the
existing Flight etc.
Input: Flight Number, Flight Name, Destination and other
Inputs are according to the task performed.
Output: This form shows options for Adding, Modifying or
Delete the Flight from the list.
Validation: No Field Flight Number and Flight Name should left
empty.
4. REPORT
This module contains four submodules.
4.1 Flight Status
Description: If any client wants to book a Flight, he can view
the details of Flight that the Flight is available at that particular
date or not. After viewing the status of Flight clients can make
easy decisions about the Flight Booking.
4.2 Client Report
Description: This submodule is used for showing the Clients list
that has booked their seats in the Flight.
Output: Shows the list of the clients who has booked the Flight.
Validations: Shows only the list of booked clients list.
4.3 Report
Description: This submodule is used for showing the clients list
whose tickets are cancelled.
Output: Shows the list of the clients who has cancelled the
Flight Booking.
Validations: Shows the list of client who cancelled the Booking.
DATA DICTIONARY
In this project we handle databases through using the concept of

14. Relational database
First One is ADMIN_LOGIN Table: -
Field Name Storage Type Length
Constraint
Username varchar 25
primary key
Password varchar 20
-
Second is BookingTable: -
Field Name Storage Type Length
Constraint
Ticket_no integer 10 primary key
Journey_date date - -
From_of varchar - -
To_of varchar - -
Flight_name varchar - -
Required_seats integer 8 -
Flight_no varchar - not null
Flight_fair integer 5 -
Total_amount integer 8 -
Name varchar - -
Age integer - -
Martial_status varchar - -
Sex varchar - -
Seat_no varchar - -
Address varchar 100 -
Street_no varchar - -
City_of varchar - -

15. State_of varchar - -
Country_of varchar - -
Pin_of integer 10 -
Phone_no integer 10 -
Email_of varchar - -
Third is Fligh_Cancellation Table: -
Field Name Storage Type Length Constraint
Ticket_no integer 10 primary key
Journey_date date - -
From_of varchar - -
To_of varchar - -
Flight_name varchar - -
Flight_no varchar - not null
Name varchar - -
Age integer - -
Martial_status varchar - -
Sex varchar - -
Seat_no varchar - -
Address varchar 100 -
Street_no varchar - -
City_of varchar - -
State_of varchar - -
Country_of varchar - -
Pin_of integer 10 -
Phone_no integer 10 -
Email varchar - -
Fifth is Flight Entry Table: -
Field Name Storage Type Length
Constraint

16. Flight_no varchar - not null
Flight_name varchar - -
Flight_fair integer 5 -
Destination varchar 100 -
Remarks varchar 100 -
SQL STATEMENT TO CREATE DATABASE
Create Table Admin_login
Create Table Admin_login (username varchar primary key,
password varchar (20));
Create Table Booking
Create Table Booking (Ticket_no integer(10) primary key,
journey_date date, from_of varchar, to_of varchar, Flight_name
varchar, Required_seats integer,Flight_no varchar, Flight_fair
integer(5), Total_amount integer(8), Name varchar, Age integer,
Martial_status varchar, Sex varchar, Seats_no varchar, Address
varchar(100), Street_no varchar, City_of varchar, State_of
varchar, Country_of varchar, Pin_of integer(10), Phone_no
integer(10), Email_of varchar);
Create Table Flight_Cancellation
Create Table Fligh_Cancellation (Ticket_no integer (10)
primary key, journey_date date, From_of varchar, To_of
varchar, Flight_name varchar, Flight_no varchar not null, Name
varchar, Age integer, Martial_status varchar, Sex varchar,
Seat_no varchar, Address varchar (100), Street_no varchar,
City_of varchar, State_of varchar, Country_of varchar, Pin_of
integer (10), Phone_no integer (10), Email varchar);
Create Table Flight Entry
Create Table Flightentry (Flight_no varchar not null,
Flight_name varchar, Flight_fair integer (5), Destination

17. varchar (100), Remarks varchar (100));
Project Plan
This project on inventory control management system will be
completed within four months starting from Fri 7/15/16.The
estimated fund for this project is $2,500 The phases for this
project include five steps of the development life cycle which
are Analysis Phase, Planning Phase, Design Phase, and
Implementation Phase, testing / maintenance Phase.
Team Structure
Name
Duty
Mmmm
Project Manager / Technical Head
Xxxxx
Programmer / Design Architect
Kxxxx
System Analyst / Quality Analyst
Kaxxxx
Risk Manager / Database Administrator
Sampled Project Schedule or Break down Structure
Task

18. Due Date
Responsible Member
Software Project Management Plan
Fri 7/15/16
ALL
Software Requirements Specifications
Thu 8/25/16
ALL
Software Architecture Design Document
Fri 8/26/16
ALL
Work Breakdown Structure
Fri 9/16/16
ALL
Milestone Report
Fri 11/11/16
ALL
Software Design Document (SDD)
Tue 12/20/16
ALL
Risk Management Plan
Fri 1/27/17
ALL
Quality Assurance Plan
Tue 2/28/17
ALL
Source and Object Code

19. Thu 3/9/17
ALL
User Manual
Fri 4/21/17
ALL
Length of the Project
Work Package/ Action Performed
Responsible Member
Time Duration
Software Project Management Plan
ALL
70 Hours
Software Requirements Specifications (
ALL
70 Hours
Software Architecture Design Document
ALL
100 Hours
Work Breakdown Structure
ALL
60 Hours
Milestone Report
ALL
70 Hours
Risk Management Plan
ALL
90 Hours
Quality Plan

20. ALL
90 Hours
Source and Object Code
ALL
160 Hours
Total
700 Hours
Team Details and Project Manager
Role
Position
Stake Holder
Sponsor
Manager
Consultant
Project Manager
Technical Head /Project Manager
Team Member 1
Design Architect/ Programmer
Team Member 2
Quality Analyst /System Analyst
Team Member 3

21. Risk Manager/
Database Administrator
GANTT CHART

22. PERT CHART
Coding
Data Gathering
Analysis
Designing
Testing
Implementation
20 days
45 days
65 days
90 days
115 days
135 days
25 days
40 days
25 days
25 days
20 days

23. REFERENCES
1. Ali Bahrami – “Object oriented systems Development”
2. Grady Booch, James Rumbaugh, and Ivar Jacobson -”Unified
Modeling Language User Guide”

24. 3. Simon Bennett ,Steve Mcrobband Ray Farmer– “Object
Oriented Analysis and Design”
4. Terry quatrani –“Visual modeling with Rational Rose 2002”
28
Individual Project: Students will work individually on a system
design project to demonstrate their ability to apply the
knowledge acquired in this course. The project will require
students to perform requirements analysis, system and database
design, and a project plan. You can suggest a topic related with
your work/interest or use one from the list below:
My Choice: Internet shopping sites (clothing, shoes, books,
music, or others)
Kindly include: DFD, pert charts, a write up
I have attached a sample work for my friend, I want mine to be
better than his so kindly go through the attached one and make
mine far much better. I need an A