Flight Reservation Management Software Requirement Specification (SRS)
Flight Reservation Management Software Requirement Specification (SRS)
By:
Akshaya K Salim
Aisha A Majeed
Ancy Rajan
Nithya Nepolean
1
TABLE OF CONTENTS
1.Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
2.Overall Description
3.Specific Requirements
3.1 Functionality
3.1.1 Customer -Book Flight
2
1.INTRODUCTION
The introduction of the Software Requirement Specification (SRS) provides an
overview of the entire SRS with purpose, document convention, scope, and
reference. The aim of this document is to gather and analyse and give in-depth
insight of the complete project by defining the problem statement in detail. It
concentrates on fulfilling the daily requirements or services that each house
needs. The detailed features and requirements of the project named Flight
Reservation is given in this document.
1.1 Purpose
The purpose of the document is to collect and analyse all assorted ideas that
have come up to define the project, its requirements with respect to consumers.
Also, we shall predict and sort out how we hope this online reservation service
will be used in order to gain a better understanding of the project, outline
concepts that may be developed later, and document ideas that are being
considered, but may be discarded as the product develops.
In short, the purpose of this SRS document is to provide a detailed overview of
our online flight reservation management, its parameters and goals. This
document describes the project's target audience and its user interface, and
software requirements. It defines how our customers, team and audience see the
product and its functionality. Nonetheless, it helps any designer and developer
to assist in software delivery lifecycle (SDLC) processes.
1.2 Scope
Flight Reservation Management is based on a concept to provide an online
platform for booking flights for our customers. The services that we include are
to view the flights that are available to us, to book a flight with the availability
and to cancel the flight if needed. There are four modules in the project they are
admin, customer, flight and ticket.
3
1.3 Definitions Acronym and Abbrevations
SDLC – Software development lifecycle
2 OVERALL DESCRIPTION
This document contains the problem statement that the current system is facing
which is hampering the growth opportunities of the company. It also illustrates
the needs and wants of the each and every one to reduce the difficulty in
booking a flight. It further lists and briefly describes the major features and a
brief description of each of the proposed system. The following SRS contains
the detailed application perspective. It provides the detail functions of the
applications with user characteristics permitted constraints, assumptions and
dependencies and requirements subsets.
3 SPECIFIC REQUIREMENTS
The specific requirements are:
3.1 Functionality
This subsection contains the requirements for the application. These
requirements are organized by the features as discussed. Features are then
refined into use case diagrams and to sequence diagram to best capture the
functional requirements of the application.
4
3.1.1 Customer – Book Flight
The system shall display all the flights that are available.
The system shall allow customer to select the flight and book for it.
3.1.2 Customer – View Flight.
The system shall allow the customer to view the flights that are available.
3.1.3 Customer – Cancel Flight
The system shall allow customer to cancel the flight that was booked.
3.1.4 Flight – Add Flight
The system shall allow admin to add the flight details to a file.
3.1.5 Flight – Edit Flight
The system shall allow the admin to edit the flight details that are stored in the
file.
3.1.6 Flight – Delete Flight
The system shall allow the admin to delete the flight details that are stored in the
file.
3.1.7 Flight- Display Flight
The system shall display all the flights that are available.
3.1.8 Ticket- View Ticket
The system shall allow to view the ticket that was booked by the customer.
3.2 USABILITY
3.2.1 Graphical User Interface
The system shall provide a uniform look and feel between all the web pages.
The system shall provide use of icons and toolbars.
3.2.2 Accessibility
The Application shall be accessible through any web browser.
5
3.3 PERFORMANCE
The product shall be based on web and has to be run from a web server. The
product shall take initial load time depending on internet connection strength
which also depends on the media from which the product is run.
3.6 INTERFACES
3.6.1 User Interfaces
The user interface for the software shall be compatible to any browser such as
Mozilla or Netscape Navigator by which user can access to the system.
6
3.6.2 Application Interface
1. There are two in this application, the user (admin and customer) interface
Django. The second interface will be between the Django and the database.
2. The application system shall communicate with the Configurator to
identify all the available flights for booking.