Software engineering

 IEEE Standard Software

Requirement Specification
(SRS) for

Airline Flight Reservation

System

A Software Requirements Specification (SRS) is a document

that describes the nature of a project, software or application.
In simple words, SRS document is a manual of a project
provided it is prepared before we kick start a
project/application. There are set of guidelines to be followed
while preparing the software requirement specification of a
project. In addition to this, it also contains the information
about environmental conditions required, safety and security
requirements, software quality attributes of the project etc.

Table of Contents for a SRS Document

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, acronyms and abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Product Perspective
2.2 Product Features
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation constraints
2.6 Assumptions and Dependencies
3. Specific Requirements
3.1 Functional Requirements
3.2 External Interface Requirements
 User Interfaces
 Hardware Interfaces
 Software Interfaces
 Communications Interfaces
3.3 Nonfunctional Requirements
 Performance Requirements
 Safety Requirements
 Security Requirement
 Software Quality Attributes

4. Appendix
 PROBLEM DEFINITION
Ticket reservation system for airline has to be
developed.
The system developed should contain the following
features

1. The system should contain the following features

2. Search for information about the flight by means of
flight number and destination
3. While displaying information about the flight it had to
provide availability of seats.
4. While reserving tickets the system obtain following
information from the user
Passenger Name, Sex, Age, Address,
Credit Card Number, Bank Name,
Flight number, Flight name, Date of Journey and
number of tickets to be booked.
5. Based on availability of tickets, the ticket has to be
issued. The ticket issued should contain the following
information like ticket number, flight no, flight name,
date if journey, number of passengers, sex age and
departure time.
6. Cancellation of booked tickets should be available.

1. INTRODUCTION
1.1 Purpose
 The purpose of the SRS is to describe the
requirements involved in developing an Airline
Reservation system (ARS).
 The intended audience is any person who wants to
reserve or cancel tickets or to check the availability
of Airline tickets

1.2 Scope
 The product is titled Airline Reservation System
(ARS).
 The product will perform the following tasks –
 The software that is being developed can be
used to check the availability of the fight tickets
for the specified flight, destination and date of
journey
 If the tickets are available to the user’s needs
specification, then the software provide a
facility to book the tickets.
 If the passengers want to cancel the tickets, he
can use the cancellation module of the Airline
Reservation System.
1.3 Definitions, Acronyms and Abbreviations
 ARS: Airline Reservation System

1.4 References
  IEEE standard 830-1998 recommended practice for
Software Requirements Specifications-Description.
1.5 Overview
 The SRS contains an analysis of the requirement
necessary to help easy design.
 The overall description provides interface
requirements for the Airline Reservation system,
product perspective, hardware interfaces software
interface, communication interface, user
characteristics and other.

2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
A distributed airline database system stores the
following information.
 Flight details:
It includes the originating flight terminal and destination
terminal, along with the stops in between, the number
of seats booked/available seats between two
destinations etc.
 Customer description:
It includes customer code, name, address and phone
number. This information may be used for keeping the
records of the customer for any emergency or for any
other kind of information.
 Reservation description:
 It includes customer details, code number, flight
number, date of booking, date of travel.

2.2 PRODUCT FEATURES

The major features of airline database system as shown
in below
Entity-relationship model(ER model)

2.3 USER CLASS and CHARACTERISTICS

 User of the system should be able to retrieve flight
information between two given cities with the given
date/time of travel from the database. A route from city
A to city B is a sequence of connecting flights from A to
B such that:
a) There are at most two connecting stops, excluding
the starting city and destination city of trip
b) The connecting time is between one to two hours.
The system will support two types of user
privileges, Customer, and employee. Customer will
have access to customer functions, and the
employees will have access to both customer and
flight management functions. The customer should
be able to do the following functions:
 Make a new reservation
o One-way
o Round-Trip
o Multi-city
o Flexible Date/time
o Confirmation
 Cancel an existing reservation
 View his itinerary
Each flight has a limited number of available seats. There are a
number of flights which depart from or arrive at different cities
on different dates and time.

2.4 OPERATING ENVIRONMENT

 Operating environment for the airline management
System is as listed below.

 Distributed database
 Client/server system
 Operating system: Windows.
 Database: sql+ database
 Platform: vb.net/Java/PHP

2.5 DESIGN and IMPLEMENTATION CONSTRAINTS

1. The global schema, fragmentation schema, and

allocation schema.
2. SQL commands for above queries/applications
3. How the response for application 1 and 2 will be
generated. Assuming these are global queries.
4. Implement the database at least using a centralized
database management system.

3. SPECIFIC REQUIREMENT

 DESCRIPTION and PRIORITY

The airline reservation system maintains information on
flights, classes of seats, personal preferences, prices,
and bookings. Of course, this project has a high priority
because it is very difficult to travel across countries
without prior reservations.
 STIMULUS/RESPONSE SEQUENCES
o Search for Airline flights for two travel cities
o Displays a detailed list of available flights and make
a “Reservation” or book a ticket on a particular
flight.
o Cancel an existing reservation.

3.1 FUNCTIONAL REQUIREMENTS

Other system features include:

o DISTRIBUTED DATABASE:
It implies that a single application should be able to
operate transparently
On data that is spread across a variety of data that
is spread across a variety of different databases and
connected by communication network as shown in
figure below

o CLIENT/SERVER SYSTEM
 The term client/server refers primarily to an
architecture or logical division of responsibilities,
the client is the application, and the server is the
DBMS.

A client/server system is a distributed system

in which,
 Some sites are client sites and others are server
sites.
 All the data resides at the server sites.
 All applications execute at the client sites.

3.2 EXTERNAL INTERFACE REQUIREMENTS

 USER INTERFACES
 Front-end software: Vb.net versant
 Back-end software: SQL+
 HARDWARE INTERFACES
 Windows.
 A browser which supports CGI, HTML & JavaScript.
 SOFTWARE INTERFACES
Following are the software used for the flight management
online application.
o Operating system: windows
o Database: to save the flight records, passenger’s
records we have chosen SQL+ database.
o VB.Net: to implement the project we have chosen
Vb.net language for its more interactive support.
  COMMUNICATION INTERFACES
This project supports all types of web browsers. We are
using simple electronic forms for the reservation forms,
ticket booking etc.

3.3 NONFUNCTIONAL REQUIREMENTS

 PERFORMANCE REQUIREMENTS
The steps involved to perform the implementation of
airline database are as listed below.
a)E-R diagram
The E-R diagram constitutes a technique for representing
the logical structure of a database in a pictorial manner.
This analysis is then used to organize data as a relation,
normalizing relation and finally obtaining a relation
database.

E-R diagram of airline database

 b) The basic objective of normalization is to reduce
redundancy which means that information is to be stored
only once. Storing information several times leads to
wastage of storage space and increase in the total size of
the data stored.

 SAFETY REQUIREMENTS

If there is extensive damage to a wide portion of the

database due to catastrophic failure, such as a disk
crash, the recovery method restores a past copy of the
database that was backed up to archival storage and
reconstructs a more current state by reapplying or
redoing the operations of committed transactions from
the backed up log, up to the time of failure.

 SECURITY REQUIREMENTS

Security systems need database storage just like many

other applications. However, the special requirements
of the security market mean that vendors mush choose
their database partner carefully.

 SOFTWARE QUALITY ATTRIBUTES

 AVAILABILITY: The flight should be available on the specified
date and specified time as many customers are doing advance
reservations.
  CORRECTNESS: The flight should reach start from correct
start terminal and should reach the correct destination.

 MAINTAINABILITY: The administrators and flight in chargers

should maintain correct schedules of flights.

 USABILITY: The flight schedules should satisfy a maximum

number of customers needs.

4. Appendix: Glossary

 Authentication
The process of identifying an individual, usually based onusername and password

Cached
A form of storing information/data, usually this data is repeatedly accessed.

 CSS
Cascading Style Sheets is a feature to give users and developers more control on
how web site pages are displayed.

 Database
Is a structured collection of records or data that is stored in computer system. In
our
system, this may pertain to flight records or user information.

 Dynamic Links
A pointer to a particular scope called during runtime.
 Encryption Algorithm
A mathematical procedure for performing encryption on data, which is translating
Data into secret code.

 HTTP
Hyper Text Transfer Protocol is the underlying protocol used by the World Wide
Web. It defines how messages are formatted and transmitted and what actions
should be taken in response to various commands.

 Hyper Links
Also called link, is a directly followable reference within ahypertext document.

 Input Criteria
A defined particular group of criteria, which defines inputs.

 Query or Queries
A form of questioning. In this document, query pertains to asearch entered by a
user into a search engine to return results.
Thank you