Experiment-I: Software Requirements Specification

(ONLINE FLIGHT RESERVATION SYSTEM)

1. Problem Statement: To collect software requirements and create software

requirement specification.

2. SOFTWARE REQUIREMENTS: Ms Word.

1. Introduction

1.1 Purpose Basic Description of Problem

The purpose of this project is to allow the users to books flight tickets online from
anywhere and at any time they want.

1.2 Scope

The purpose of this specification is to document requirements for a system to manage

the flight ticket booking. The specification identifies what such a system is required to
do. The specification is written in a format conforming to the IEEE Standard 830-
1984. Subject to approval, the specification will complete the Requirements phase and
will be followed by detailed design, implementation, and testing.

1.3 Definitions, Acronyms, and Abbreviations

GUI- Graphical User Interface

MI- Flight ID
SI- Seat ID

1.4 References
DOnline flight reservation system is a complete Online Flightbooking management software
and system with features like: Selecting aeroplane name, airport, time, Adding flights and a
lot more.

1.5 Overview

This specification includes a brief product perspective and a summary of the functions
the software will provide. User characteristics are discussed and any general
constraints or assumptions and dependencies are listed.

Requirement statements are categorized as functional requirements, performance

requirements, non-functional requirements, or design constraints. Functional
requirements are further categorized in terms of user registration, Selecting city,
plane, time, airport, number of seats etc. Non-functional requirements are further
categorized in terms of security, maintainability, and scalability.

2. General Description
2.1 Product Perspective

Online Flight Reservation System is designed to help the administrator to handle the process
of adding or cancellation of flights , saving information related to booking, payments. The
current design goal is to build an internal system to achieve the functionality outlined in this
specification.

2.2 Product Functions

Online Flight Reservation System will allow the user to manage information about selecting
city, airport , time, date, number of seats, cancel ticket. User registration provide the users
sign up procedure. Data updation here means adding or cancelation of tickets . The online
Flight Reservation System will also support the automatic backup and protection of data.

2.3 User Characteristics

There are three different types of users for the SMS system:

Type 1. Administrative Clerks, who handle data entry for the Online Flight
Reservation system. They have data entry training. Administrative Clerks are
familiar with basic computer operations. They add or cancel flights into /from
the System.

Type 2. Users, who use this whole system (booking tickets based on flight, airport ,
name, time, date) but cannot modify any information.

Based on the above categorizations, in order to meet user's needs the following precautions
should be taken:

 the interface should be designed with the computer novice in mind

 data entry masks should recognize and correct improperly entered data
 for cancelling the ticket, system should ask the users for confirmation
 Error messages should be provided.
 the interface should be easy to understand.

2.4 General Constraints

The following constraints will limit the developer's options for designing the system:

 the budget for this project is fifteen lakhs.

 implementation is required within 9 weeks.
3. Specific Requirements

3.1 Functional Requirements

R l. User Registration and Booking Subsystem

The Flight Ticket Reservation subsystem requirements are concerned with the management
of user ticket booking information.

R 1.1 The Flight Ticket Reservation subsystem shall allow the user type 1 to update
the flights list i.e ,adding or cancelling a flight.

R 1.2 The Flight Reservation System subsystem shall store all users booking history
information.

R 1.3 The Flight Reservation System subsystem shall allow the user type1 to add
new users (customers) into the system.

R 1.4 The user can register by creating user name and password and using the
same for login.

R l .5 The Flight Reservation System subsystem shall allow all user types to retrieve
booking history and personal information by logging into their respective
accounts.
R 1.6 The user can login and book tickets by selecting city, language, Flight , date,
airport, time, number of seats, type of seats, selecting seats, and view booking
receipt, can also cancel tickets.

R2 Data Updation by Administrator

R2.1 List of Flights information management

R3.1.1 Add new Flight.

R3.1.2 Delete an existing Flight.

R3.1.3 Displaying offers

3.2 Performance Requirements

R3 The SMS shall respond to user's booking by selecting Flight, airport, data, time, number
of seats and payment quickly. The waiting time for any operation must be under 2 seconds.

3.3 Non-functional Requirements

R4 Security.

The security requirements are concerned with security and privacy issues. All users
information is required by law to be kept private
 R 4.1 The Flight Reservation System system shall support different user access
privileges.

R 4.2 The Flight Reservation System system shall protect every user’s information.

R5. Maintainability

The maintainability requirements are concerned with the maintenance issues of the system.
R 5.1 The maintenance time of Flight Reservation System system shall be done regularly.
R 5.2 System down time for maintenance should be less than 6 hours per quarter of a year.

R6. Scalability

The scalability requirements are concerned with the scalable issues of the system.
R 6.1 The Flight Reservation System system shall be able to scale up to support more
workstations. System performance shall not degrade if up to twenty percent (20%) more
workstations are added.

3.4 Design Constraints

R 8. The Flight Reservation System system shall have a graphical user interface.

R 9. The Flight Reservation System system must be written in Java.