First

INTRODUCTION
The current trend in Airlines is online reservation. In concurrent to our traditional airlines
booking system online is gradually gaining entry. Advancement of network and information
technology have further catalyzed the process.
In online the Airlines database resides at a central server. Individuals of various statuses
(such as customers, Administrator, etc) can access the server database from any location, for
which all they need is a network connection and a web browser. They can log in, using their
ID and password which allows them to transact with the server as per authorization granted
against the corresponding user name & password. Customers can now access booking facility
from any location. Administrator can maintain flight details, customer account details from
any location.
The aforesaid managements are used to be more time consuming, complex and error
prone when handled manually. This computerized system will resolve the problems
effectively to some extent.
PURPOSE:
PURPOSE
This specification document describes the capabilities that will be provided by the
software application Airlines management system. It also states the various required
constrains by which the system will abide. The intended audiences for this document are the
development team, testing team and end users of the product.
SCOPE
The Airlines management System is collection of interactive programme which will be used
for following tasks
Keeping track of flights information, flights time schedules, flights fare

chart etc.
Keeping track of customers personal as well as contact details and log in

information.
Printable reports will be generated.
Allow the user to search a flight, book a flight and make payment for the
ticket via online.
Allow the Administrator to add, update, & cancel a flight and add a airport.
On Line ticket booking Management System
USER INTERFACE
The following screens will be provided:
Home page screen: User can login or search the flight.
Page 2
Login Screen:
This screen will allow the user to enter the username and password (Administrator, Register
user, Booking officer, Travel Agent). It will also allow the user to access different screens
based upon the users role.
Page 3
General user registration Screen:

This screen will allow the new general user, who book at least one flight, to register into the
system.
Page 4
Flight search & Book screen:

This screen will be accessible to the general and registered user. It will allow the user to enter
the origin, destination, departure date, return date, class of service etc. On the basis of these
criteria software will search the flight from the database and allow the user to book the flight.
Page 5
Payment Screen:
This screen will be generating dynamically. The ordinary user can booked their flight through
online via credit card, debit card, and internet banking. The booking officer has additional
option i.e. by cash.
Page 6
Ticket cancel screen:

This screen will be accessible only to the registered user. It will allow the user to enter their
reservation Id and ticket Number to cancel their ticket.
Page 7
Report generation screen:

This screen will be accessible only to the Administrator. It will allow the user to generate the
various types of reports. The following report will be generated:
Flight Details Report: Printable report will be generated to show the list of flight
details daily, weekly, monthly, few months, yearly.
Ticket Sales Report: Printable report will be generated to show the list of ticket sales
details daily, weekly, monthly, few months, and yearly.
Passenger Report: Printable report will be generated to show the list of passenger
according to different parameters.
Users Report:
This report will show about user account and personal details and
his/her journey details.
Frequent Traveler Report: This report will show about journey details of frequent
traveler.
Traveler Feedback Report: This report will show the feedback of different customer.
Booking Rate Report: This report will show the tariff of a particular flight or
particular route.
Route Details Report: This report will show the route details of different flight.
Cancel Flight Report: This report will show the list of details of canceled flight.
Ticket Cancel Report: This report will show the list of details of canceled ticket.
Page 8
Page 9
Aircraft maintain screen:

This screen will allow the administrator to add and delete the aircraft.
Add airport screen:

This screen will allow the administrator to add and delete the airport.
Page 10
SOFTWARE & HARDWARE INTERFACE
Hardware Interface
Pentium IV, 1.6 GHz
512 MB RAM
40 GB HDD
15 Monitor
104 keys Keyboard
1.44 Floppy Disk Drive
52X CD ROM Drive
Inkjet printer
Software Interface
Operating System
Windows 2000,XP
Environment
JDK 1.5
Web Server
Apache Tomcat 5.5
Editor/IDE Used
Notepad, Dream Weaver MX 2004
Technology Used
HTML, Java, JSP
RDBMS
Oracle 10g
Documentation
MS Office 2003
Others
Natty wares Pixie
Memory Constrains
At least 64MB RAM and 2 GB space on hard disk will be required for running the
application.
Operations
This product release will not cover any automated housekeeping aspects of the database.
The DBA at the client site will be responsible for manually deleting old/non-required
data. Database backup and recovery will also have to be handled by the DBA.
Site Adaptation Requirements

The terminal at client site will have to support the hardware and software interfaces
specified in above section.
Page 11
Product
Functions
The system will allow access to registered user, administrator, booking officer. Depending
upon the users role, he/she will be able to access specific module of the system.
A summary of the major functions that the software will perform:
A Login facility for enabling only authorized access to the system.
Normal user will be able to search flights depending upon date, destination, origin etc.
and register them to the system.
Registered user will be able to search, book, cancel a flight and also make payment.
Travel agent will be able to search, book, cancel a flight and also make payment and
have a special agreement with the company.
Booking officer will be able to search, book, cancel a flight and also make payment.
He also view the daily sales report and issue original ticket against general user ticket.
Administrator will be able to add/modify/delete a flight.
Administrator will also be able to add airport, show report, issue promotional offer.
Administrator will also be able to maintain login and user account.
User
User
Educational level:Characteristics
At least graduate should be comfortable with English
Characteristics
language.
Experience: Should be well versed/informed about the airlines system. Entry

of Flight details or modification can be done only by Administrator.
Technical
expertise:
Should
be
comfortable
using
general-purpose
applications on a computer.
Constraints
i) It is dependent on the internet. So downloading the page from the server to client
takes more time if the speed of the internet is slow and if many people request at a time it
would be also slow due to server capacity problem.
Page 12
ii) Bank transaction may hamper due to hacker and internet speed.
iii) Users at Airlines will have to implement a security policy to safeguard the personal
details and bank information from being modified by unauthorized users.
Assumptions and Dependencies
The system could not book more than eight people at a time
We could book two flights at a time in this system.
This software is suitable for Internet Explorer.
Apportioning of requirements:
Not required.
CASE STUDY
Case Study of Online Air booking & Management

System:
The problem statement for online air booking & management system is given below:
Problem statement:
A software has to" be developed for automating the manual air booking & management
system of an aviation company. The system should be web application in nature. It should be
designed to provide functionality's as explained below:
An aviation company has decided to engage a software company for the automation of
Online Air Booking Management System. The following documents are required to be
prepared.
1. Problem statement
2. Context Diagram
3. Data flow diagram
4. ER diagram
5. Use case diagram
6. Use case
7. SRS as per IEEE stander 830-1993
These seven documents may provide holistic view of the system to be developed. The
SRS will act as contract document between developers (Software Company) and client
(Aviation Company).
1 .The initial problem statement:
Page 13
The problem statement is the first document which is normally prepared by the client.
It only the superficial view of the system as per clients perspective and exception. It
is the input to the requirement engineering process where final product is SRS.
The problem statement of Online Air Booking Management System of an aviation

company is given below:
The purpose of the airline reservation system is to help the travel agent must be able
to find all of the flights meeting a passengers needs and make reservation based on
the passengers preferences.
2. Goal of the system:
2.1
The purpose of the system is to help the travel agent sell tickets
2.1.1 The system must help the travel agent find all of the flights meeting a
passengers needs.
2.1.1.1
The System must be able to find all flights with a given

origin and destination.
2.1.1.2
The system must display the arrival and departure time, the
price and the flight number for each flight it finds.
2.1.1.3
The passenger will choose a flight based on the displayed

information.
2.1.2 The system must let the travel agent makes reservations
2.1.3 The system must allow the travel agent to cancel reservations.
2.1.4 The system must be able to friend all reservation on a given flight after
a given datederived from 2.2.2
2.1.5 The customers who book their flight online they will make payment by
credit card, Internet Banking, Debit card.
2.2
The system must provide a means for the airline administrator to manage
flights.
2.2.1 The system must allow the airline administrator to schedule new
flights.
Page 14
2.2.2 The system must allow the airline administrator to drop flight from the
schedule.
2.2.3 The system must allow the airline administrator to change the fare for a
flight.
2.2.4 The system must allow the airline administrator to show different
reports depending on different criteria.
CONTEXT FLOW
DIAGRAM
Page 15
Entity Relationship
Diagram
Page 16
USE CASE DIAGRAM
Page 17
USE CASE
SPECIFICATION
Page 18
1. USE CASE: SIGN IN OR LOGIN

1.1 Brief Description: This use case describes how users login/sign in into the Online
Airlines Booking System.
1.2 Actors: Customer, Administrator
1.3 Flow of events:
1.3.1 Basic Flow:
1. The system requests that the actors enter his / her username, password.
2. The actor enters / her username, password.
3. The system validates the entered username, password & logs the actor into the
system with his or her own page.
1.3.2 Alternative Flow:
2. a. Invalid username or password:
If in the basic flow the actor enters an invalid username, password, system
displays an error message. The actor can choose to either return to the beginning
of the basic flow or cancel the login, at which point the use case ends. Actors will
be requested to system to get his/her password and also register them with new
username & password.
1.4 Special requirements: None
1.5 Pre-conditions: All actors have a username and password. In case of new customer,
he/she will be requested to register them with new username, password
& personal details.
1.6 Post Conditions: If the use case was successful, the actor is logged the system with their
own page.
If the actor is an administrator then she / he will have access to only
screen corresponding to the Add flight, modify flight, cancel flight,
view report, customer account maintain, add airport module of the
system.
If the actor is a customer then he / she will have access to only the
screen corresponding to the search flight, book flight, and payment
modules of the system.
Administrator and customer will be differentiated by index id which is
a field of the table. In case of administrator index id will be 2 and in
case of customer index id will be 1.
2. Use Case: Registration for User

2.1 Brief Description: The use case documents the procedure for registration of the user for
further requirement.
2.2 Actor: Administrator, customer.
2.3 Pre-condition: User has to book a flight before registration.
2.4 Post-condition: User successfully registered.
2.5 Flow of events:
2.5.1 Basic flow: This use case starts after the user books a flight.
System displays a form with required fields.
User fills up the form with necessary information.
2.5.2 Alternative Flow: User cancels his/her action.
Page 19
2.6 Special Requirements: None

2.7 Related Use Case: None
3. USE CASE: SEARCH A FLIGHT

3.1 Brief Description: This use case allows the actor to search flight on the basis of
origin, destination, arrival time, departure time and preferable
class.
3.2 Actors: Customer
3.3 Flow of events:
3.3.1 Basic flow: This use case starts when the customer wishes to book a flight or to
enquiry flights. Customer provides a destination and dates to the system. The system
enquires the airline database about the available flights & presents them to the
customer.
1. Customer select search available flight first.
2. Selects origination city
3. Selects destination city
4. Selects departure date
5. Selects return date
6. Selects one way or two way
7. Selects connections or nonstop
8. Submit criteria
9. System validates the customer data. Data is valid if customer enters a start and end
cities that the system provides service to and valid dates such that the starts date is not
prior to the end date & vice versa. Invalid data are empty cities & dates that do not
exist.
10. System shows list of flights that met customers criteria and each item in the list
has an associated price and a Book this Flight option.
1. Flight not found: If there is no such flight matching the search criteria then a
message will be displayed.
2.(10.a) After displaying the list of flight a customer can select cancel option
then system display the main option screen.
3. (8.a) If customer does not complete the main option screen with the input
data and a note starting that certain required data is missing.
3.4 Special Requirement: None
3.5 Pre condition: Actor has successfully navigated to the main options screen.
3.6 Post condition: A list of flight matching the search criteria is presented.
3.7 Extension points: None
4. USE CASE: BOOKING A FLIGHT

4.1 Brief description: This use case allows the customer to book a flight.
4.2 Actor: Customer
4.3 Flow of events:
4.3.1 Basic flow:
1. Customer selects the Book this flight option from the list of the
flights presented.
Page 20
2. The system displays a screen with three types of options viz. by

cash, by credit card, by internet banking.
2.1 If the user choose the by cash option then the system
displays a text box for entering the cash amount.
2.2 If the user choose the by credit card option then the system
displays a screen with input fields for entering a credit card
number, cardholder name, and credit card expiration date.
2.3 If the user choose the by internet banking option then the
system displays a screen with input fields for entering account
number and bank name.
3. After entering required data customer clicks the submit button.
4. System displays the details of the reservation.
5. Customer then selects the "Complete Reservation" option.
6. The system displays the main options screen. The message
"Reservation Successfully Made" is also displayed.
1. (3.a) If the customer does not complete all the necessary fields. Then system
redisplays the input fields from step 2 with the input data and a note stating that
certain required data is missing or invalid.
2. (3.b) If the customer selects cancel option then system displays the screen with
three options.
3. (5.a) If the customer selects cancel option before selecting the Complete
Reservation option then system displays the screen with three options.
4.4 Special requirement: None
4.5 Pre-condition: Actor has successfully generated a list of flights as documented in the
"Search for Flights" use case.
4.6 Post-condition: A reservation has been made.
4.7 Extension Points: None.
5. USE CASE: PAYMENT FOR TICKET

5.1 Brief Description: This use case allows a customer to purchase the ticket for a reserved
flight.
5.2 Actor: Customer
5.3 Flow of Events:
5.3.1 Basic Flow:
1. This use case starts when the customer selects the "Purchase Ticket" link from the
list of options.
2. The system displays a screen with an input field for a reservation number.
3. Customer enters a reservation number and clicks the "Submit" button.
4. The system displays the details of the reservation.
5. Customer selects the "Purchase Ticket" option.
6. The system displays a screen with three types of options viz. by cash, by credit
card, by internet banking.
6.1 If the user choose the by cash option then the system displays a text box for
entering the cash amount.
6.2 If the user choose the by credit card option then the system displays a screen
with input fields for entering a credit card number, cardholder name, and credit card
expiration date.
Page 21
6.3 If the user choose the by internet banking option then the system displays a
screen with input fields for entering account number and bank name.
7. After entering required data customer clicks the submit button.
8. System displays the main options screen. The message "Ticket Successfully
Purchased" is also displayed
1. (3.a) If customer selects the "Cancel" option Then system displays the main
options screen.
options screen.
options screen
4. (7.b) If the customer does not complete all the necessary fields. Then system
redisplays the input fields from step 6 with the input data and a note stating that
certain required data is missing or invalid.
5.4 Special Requirements: None.
5.5 Pre-Conditions: Actor has successfully made a reservation as documented in the "Make
a Reservation" use case.
5.6 Post-conditions: A ticket has been purchased.
5.7 Extension Points: None.
6. Use Case: User Account Information Change

6.1 Brief Description: The use case documents the procedure for changing the user account
information if users want.
6.3 Pre-condition: User must be logged into the system.
6.4 Post-condition: User account information changed.
6.5 Flow of events:
6.5.1 Basic flow: This use case starts when the user wishes to change his/her account
information.
1. User selects the My Account link.
2. The system will display the screen with basic profile, change password, change
Personal details, change contact details, journey details options.
3. Once the user provides the requested information, one of the sub-flows is
executed.
If the user selects the basic profile link then system show his/her profile
details.
If the user selects the change password link then system will show the screen
that will allow the user to change his/her password.
If the user selects the change personal details link then the system will show
the screen that will allow the user to change his/her personal details.
If the user selects the change contact details link then the system will show the
screen that will allow the user to change his/her contact details.
If the user selects the journey details link then the system will display the
details of his/her journey.
6.5.2 Alternative Flow: user doesnt change his/her account information.
Page 22
7. USE CASE: MAINTAIN FLIGHT

7.1 Brief description: This use case allows the administrator to maintain flight information.
This includes adding, modifying, canceling flight information from
the system.
7.2 Actors: Administrator
7.3 Flow of events:
7.3.1 Basic Flow: This use case starts when the administrator wishes to add, modify and
cancel flight information from the system.
1. Administrators page allows selecting an option either Add flight, Modify
flight, or canceling flight.
2. Once the administrator select one of the sub-flows is executed
If the administrator selects Add flight, the Add flight sub flow is
executed.
If the administrator selects Modify flight, the Modify flight sub
flow is executed.
If the administrator selects Cancel flight, the Cancel flight sub flow
is executed
7.3.1.1 Add Flight:
1. The system requests that the administrator enter the flight information. This
includes:
a) Flight No. - Should be unique for every flight.
b) Origin
c) Destination
d) Aircraft Type
e) Weight
f) Capacity of economic class, Business class & General class.
g) Fare of economic class, Business class & General class.
h) Departure Time
i) Arrival Time
j) No. of stop over
k) Available day
7.3.1.2 Modify Flight:
1. System requests that the Administrator to select the Flight No.
2. Administrator selects the Flight No. The system retrieves and displays the
flight information.
3. Administrator makes the desired changes to the flight information. This
includes any of the information specified in the Add Flight sub flow.
4. Once the Administrator update the information, the system updates the
flight details with the updated information.
7.3.1.3 Cancel Flight:
1. System requests that the administrator to select the Flight No.
2. Administrator selects the Flight no. The system prompts the administrator
to confirm the deletion of the flight.
3. The administrator confirms deletion.
4. The system deletes the flight information.
Page 23

7.3.2.1 Flight not found: If in the modify flight or cancel flight sub-flow, a flight with
the specified Flight No. does not exist, then the system displays
an error message. The Administrator can then enter a different
flight no. or cancel the operation, at which point the use case
ends.
7.3.2.2 Modify Cancelled: If in the Modify Flight sub-flow, the Administrator
decides not to modify the flight information. The update is cancelled and the basic flow is
restarted at the beginning.
7.3.2.3 Delete Cancelled: If in the cancel Flight sub-flow, the administrator decides
not to delete the flight information, the delete is cancelled
and the basic flow is re-started at the beginning.
7.4 Special requirements: None.
7.5 Pre conditions: The administrator must be logged onto the system before this use case
begins.
7.6 Post conditions: If the use case was successful, the flight information is added, modified
or deleted from the system. Otherwise, the system state is unchanged.
a. Extension points: None.
8. Use Case: Login Maintain

8.1 Brief Description: The use case documents the procedure for maintaining Login Details.
8.2 Actor: Administrator.
8.3 Pre-condition: Administrator must be logged into the system.
8.4 Post-condition: If use case is successful, the login details should be updated, otherwise
the system state is unchanged.
8.5 Flow of events:
8.5.1 Basic flow: The use case starts when the administrator wishes to add, delete, and
modify some details of login.
The corresponding changes will be done.
The use case end.
8.5.2 Alternative Flow: None
9. USE CASE: GENERATE REPORTS

9.1 Brief Description: The use case documents the procedure for generating the reports as
desired by the Administrator.
9.4 Post-condition: If use case is successful, the various reports, regarding the details of the
flight, sales, user, etc. are generated.
9.5 Flow of events:
9.5.1 Basic flow: This use case starts when an Administrator wants to generate reports of the
Airline Booking System.
Page 24
The system display the various report generating criteria to the

user, which can be about flight, passengers, users, booking rate, route
details and sales report etc.
The Administrator selects the criteria and enters the
various parameters based on the criteria selected.
The system generates the report and sends that to printer.
The use case ends.
9.5.2.1 Printer out of paper or low on ink: If the printer goes out of paper or low on
ink, then the printing operation is aborted and the necessary action needs to be taken,
which can be feeding paper to the printer or replacing the ink cartridge. The use case
ends.
10. Use Case: User Account Maintain

10.1 Brief Description: The use case documents the procedure for maintaining User Account
Details.
10.4 Post-condition: If use case is successful, the user details should be updated, otherwise
10.5 Flow of events:
modify some details of user.
The corresponding change will be done.
The use case end.
11. Use Case: Login Maintain

11.1 Brief Description: The use case documents the procedure for maintaining Login
Details.
11.4 Post-condition: If use case is successful, the login details should be updated, otherwise
modify some details of login.
The corresponding changes will be done.
The use case end.
Page 25

12. Use case: Add Airport.

12.1 Brief Description: The use case allows the user to add airport.
12.4 Post-condition: If use case is successful, the airport details should be added; otherwise
12.5.1 Basic flow: The use case starts when the administrator wishes to add airport.
User selects the Add airport link.
System will display a form with required field.
User fill up the form with necessary information
12.5.2 Alternative Flow: User cancel the operation.
13. Use Case: Promotional Offer

13.1 Brief Description: The use case documents the procedure for issues or retrieves the
promotional offer.
13.4 Post-condition:
13.5.1 Basic flow:
14. Use Case: Sign out or Logout

14.1 Brief Description: This use case describes how a user logout/sign-out from the Online
Airlines Booking System.
14.3 Pre-condition: User must be log into the system.
14.4 Post-condition: User successfully logout from the system.
14.5.1 Basic flow: This use case starts when the user wishes to quit the system.
User click on Logout link.
System will display a log in screen for further use.
14.5.2 Alternative Flow: The user doesnt logout.
Page 26
SEQUENCE DIAGRAM
Sequence Diagram-Login
Page 27
Sequence Diagram-Registration
Page 28
Sequence Diagram-Search Flight
Page 29
Sequence Diagram-Reservation
Page 30
Sequence Diagram-Payment
Page 31
Sequence Diagram-User Account Maintain
Page 32
Sequence Diagram-Flight maintain
Page 33
Sequence Diagram-Login Maintain
Page 34
Sequence Diagram-Report Generation
Page 35
Sequence Diagram-User Account Maintain
Page 36
Sequence Diagram-Log out
Page 37
CLASS DIAGRAM
Page 38
Page 39
Page 40
Page 41
Page 42
DATABASE SCHEMA
Page 43
Page 44
Page 45
Page 46
Page 47

First

Uploaded by

Copyright:

Available Formats

First

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

First

Uploaded by

Copyright:

Available Formats

INTRODUCTION

Keeping track of flights information, flights time schedules, flights fare

Keeping track of customers personal as well as contact details and log in

Printable reports will be generated.

On Line ticket booking Management System

On Line ticket booking Management System

On Line ticket booking Management System

General user registration Screen:

On Line ticket booking Management System

Flight search & Book screen:

On Line ticket booking Management System

On Line ticket booking Management System

Ticket cancel screen:

On Line ticket booking Management System

Report generation screen:

his/her journey details.

On Line ticket booking Management System

On Line ticket booking Management System

Aircraft maintain screen:

Add airport screen:

On Line ticket booking Management System

SOFTWARE & HARDWARE INTERFACE

Pentium IV, 1.6 GHz

104 keys Keyboard

1.44 Floppy Disk Drive

52X CD ROM Drive

Apache Tomcat 5.5

Notepad, Dream Weaver MX 2004

HTML, Java, JSP

Natty wares Pixie

Site Adaptation Requirements

On Line ticket booking Management System

A Login facility for enabling only authorized access to the system.

Administrator will be able to add/modify/delete a flight.

Administrator will also be able to maintain login and user account.

Experience: Should be well versed/informed about the airlines system. Entry

On Line ticket booking Management System

Assumptions and Dependencies

We could book two flights at a time in this system.

This software is suitable for Internet Explorer.

Case Study of Online Air booking & Management

On Line ticket booking Management System

The problem statement of Online Air Booking Management System of an aviation

The System must be able to find all flights with a given

The passenger will choose a flight based on the displayed

On Line ticket booking Management System

On Line ticket booking Management System

On Line ticket booking Management System

USE CASE DIAGRAM

On Line ticket booking Management System

On Line ticket booking Management System

1. USE CASE: SIGN IN OR LOGIN

2. Use Case: Registration for User

On Line ticket booking Management System

2.6 Special Requirements: None

3. USE CASE: SEARCH A FLIGHT

4. USE CASE: BOOKING A FLIGHT

On Line ticket booking Management System

2. The system displays a screen with three types of options viz. by