AIRLINE RESERVATION SYSTEM

Fly in Cooooolllll………………..
Prepared By,
 Khitish Kumar Das
Regd. No-0805266064.
 Raghunath Rana
Regd. No-0805266098.

This project is done under the guidance of

 P.K. Dixit.
 Parthasarathi Das.
(Interface Software)

2
INTRODUCTION
 It is an internet based application dedicated to provide flexibility to
the user to book and/or cancel flight tickets through internet on
24x7 basis.

 This application also enables the organization a better reach to a

wider range of customers.

3
OBJECTIVES OF THE PROJECT
 This site provides booking facility to the users by the click of a
mouse from any place via internet.

 It will also give the company a better selling opportunity without a

congestion at the booking counter or booking office.

 We would provide a very easy, attractive and user friendly interface

so that users are motivated to use our website .

 It will also provide a quick service.

4
OVERVIEW OF THE PROJECT
This website has two modules:

1. Admin Module: Admin plays the key role throughout the whole
project.Admin having own username and password keeps track of
the flight details and also about the customer .He can approve and
can also reject the booking application of the customer.

2. User/Customer Module: - User also having his/her own username

and password for log on. After log on he/she can view all the flights
and their details and can book tickets as per the requirement. User
can also view and edit his own profile.

5
Software Specification:
 Operating System : Windows’2k
 Front end : java, servlet, jsp, html
 Back end : Oracle 10g XE
 Server : Apache Tomcat5.5.17

Hardware Specification :
 CPU type : Pentium IV.
 Memory : 256 MB RAM.
 Hard disk : 20 GB hdd.

6
Table Structures

7
TABLE NAME : LOGIN
PURPOSE : STORES USERS NAME, PASSWORD AND TYPE
PRIMARY KEY : SLNO

Column Name Data Type Size

Slno Number 22

Username Varchar 4000

Password Varchar 4000

Type Varchar 4000

8
TABLE NAME : BOOKING_DETAILS
PURPOSE : STORES BOOKING DETAIL.
PRIMARY KEY : BID
Column Name Data type Size
Bid Number 22
Date_of_booking Varchar2 4000
Date_of_journey Varchar2 4000
Class Varchar2 4000
No_of_seat Number 22
Cid Number 22
Fid Number 22
Full Name Varchar2 4000
Address Varchar2 4000
Mob_no Number 22
Dd/Cheque/Scrool no Varchar2 4000
Flight_from Varchar2 4000
Flight_to Varchar2 4000
9
Flight_name Varchar2 4000
Mode_of_payment Varchar2 4000
TABLE NAME : NOTICE
PURPOSE : STORES NOTICES
PRIMARY KEY : NOTICE_NO

Column Name Data type Size

Notice_no Number 22

Subject Varchar2 4000

Content Varchar2 4000

Date_of_notice Varchar2 4000

Receive_username Varchar2 4000

10
TABLE NAME : FEEDBACK_DETAILS
PURPOSE : STORES FEEDBACKS
PRIMARY KEY: FEEDBACK_NO

Column Name Data type Size

Feedback_no Number 22

Comments Varchar2 4000

Suggestion Varchar2 4000

Date_of_feedback Varchar2 4000

Name Varcahr2 4000

11
TABLE NAME : PAYMENTSDETAILS
PURPOSE : STORES PAYMENTS DETAILS
PRIMARY KEY :PID

Column Name Data type Size

Pid Number 22

Bid number 22

Date_of_payments date 7

Paymentmode varchar 4000

Accountno number 22

12
TABLE NAME : CUSTOMER_DETAILS
PURPOSE : STORES CUSTOMER DETAILS
PRIMARY KEY : CUSTOMERID
Column Name Data type Size

Customer_id number 22

Name Varchar2 4000

Address Datetime2 4000

Email Varchar2 4000

Gender Varchar2 4000

Phono Varchar2 4000

Cid number 22

13
TABLE NAME : FLIGHTDETAILS
PURPOSE : STORES FLIGHT DETAILS
PRIMARY KEY : FID
column Name Data type Size

Fid number 22

Fname Varchar2 4000

Flt_from Varchar2 4000

Flt_to Varchar2 4000

Deparature_time number 22

Arrival_time number 22

Available number 22

Price number 22

Class Varchar2 4000

14
TABLE NAME : REGISTRATION
PURPOSE : STORES NEW USER DETAILS
PRIMARY KEY :RID

Column Name Data type Size

Rid number 22

Fname Varchar2 4000

Lname Varchar2 4000

Gender Varchar2 4000

Email Varchar2 4000

Address Varchar2 4000

Mob_no number 22

Slno number 22

15
Data Flow Diagram(DFD)

16
DATA FLOW DIAGRAM(DFD)
 The DFD is a graphical model of a system that shows the different
processing activities or functions that the system performs and the
data interchange among these functions.

 Each function is considered as a process that consumes some input

data and produces some output data.

 DFD is also known as Data Flow Graph or Bubble Chart.

17
EXAMPLE

data store

data flow

process

data flow

External Entity

18
Components
This modeling technique uses five kinds of system components –
 1. Process:-
Process
 Performs processing on incoming data.

 Represented with a circle.

2. Data Stores:-
 Holding areas for collection of data, processes add or retrieve data
from these stores. data store

 Reperesnted using two parallel lines.

3. External Entity:-
 The system and external entities exchange data
External Entity

in the form of data flows. 19

 Represented using a rectangle.

 Cont’d
4. Data Flow:-
 Connects the processes, external entities and data stores.
data flow
 Represented using a directed arc or an arrow.

5. Output:-
 Produces the output of the system.
 Output
Represented as-

20
LEVEL 0DFD:

(0.0)
Airline
User Reservation OUTPUT
System

DATASTORE

21
LEVEL 1DFD: (FOR LOGIN)

Username
Password (1.0)
Login
Type LOGIN
Successfully

Login
22
LEVEL 2DFD: (FOR VALID ADMIN)

Flight Management(2.0.1)
Valid Admin View Customer(2.0.2)
(2.0) View Booking(2.0.3)
PROCESS
View Booking(2.0.4)
Give Announcement(2.0.5)

23
LEVEL 2DFD: (FOR FLIGHT
MANAGEMENT)

Flight Management Add Flight(2.0.1.0)

(2.0.1) Edit Flight(2.0.1.1)
PROCESS
Delete Flight(2.0.1.2)

24
LEVEL 2DFD: (FOR ADD FLIGHT)

Flight Name
Flight No
From
To
(2.0.1.0) SUCCESSFULLY
Arrival Time
ADD FLIGHT ADDED
Departure Time
Class
Seat Available
Price

25
FLIGHTDETAILS
ENTITY RELATIONSHIP
DIAGRAM

26
An Entity-relationship diagram is a specialized graphic that illustrate inter
relationship between entities in a Database.

Notations used:

Rectangles represents entity sets

Ellipses represents attributes

Diamonds represents relationship sets

 NAME EMAIL ADDRESS
CUSTOMERID GENDER
PHONENO
CID

CUSTOMERDETAILS
MOB_NO
FLIGHTNAME HAS A
DATE_OF_BOOKING
TYPE

BID
HAS A
SLNO
CID
LOGIN
USERNAME
FID

HAS A PASSWORD
CLASS

DD
BOOKIN_DETAILS ARRIVALTIME
DATE_OF_JOURNEY PAYMENTDETAILS
DEPATURETIME
NO_OF_SEATS PID
FLT_FROM

MODE_OF_PAYMENT BID
PAYMENTMODE
FLT_TO
ACCOUNTNO
FULL_NAME FLIGHTTO
DATEOFPAYMENT
FLIGHTDETAILS

FID
ADDRESS FLIGHTFROM 28
CLASS
PRICE
AVAILABLE FNAME
THANK YOU

29