Software Requirements

Specification
for

Airline Flight Booking System

Software Engineering Management

Team:
Rajani Sharma (2022H1030115P)
Joshi Kashyap Jayantkumar(2022H1030116P)
Akash Popatrao Shejul (2022H1030117P)
Keya Arunakar (2022H1030120P)

December 3, 2022

1
 Table of Contents
1. Introduction --------------------------------------------------------------------------------------------------- 1
1.1 Purpose --------------------------------------------------------------------------------------------------------- 1
1.2 Document Conventions -------------------------------------------------------------------------------------- 1
1.3 Intended Audience and Reading Suggestions ------------------------------------------------------------- 1
1.4 Project Scope -------------------------------------------------------------------------------------------------- 1
1.5 References ------------------------------------------------------------------------------------------------------ 1
2. Overall Description ------------------------------------------------------------------------------------------ 2
2.1 Product Perspective ------------------------------------------------------------------------------------------- 2
2.2 Product Features ----------------------------------------------------------------------------------------------- 2
2.2.1 Login 2
2.2.2 Enrollment 2
2 2.3 Book Flights 3
2.2.4 Reserve Seats ---------------------------------------------------------------------------------------------------------- 3
2 2.5 Flight Status 3
2.2.6 Flight Schedules -------------------------------------------------------------------------------------------------------
4
2 2.7 My Account 4
2.2.8 Logout 4
2.3 User Classes and Characteristics ---------------------------------------------------------------------------- 5
3. System Features ---------------------------------------------------------------------------------------------- 6
3.1 General Requirements ---------------------------------------------------------------------------------------- 6
3.1.1 Login 6
3.1.2 Enrollment 7
3 1.3 Book Flights 9
3.1.4 Reserve Seats ---------------------------------------------------------------------------------------------------------10
3 1.5 Flight Status 12
3.1.7 My Account 13
3.1.8 Account Log out ----------------------------------------------------------------------------------------------------- 14
4. External Interface Requirements ----------------------------------------------------------------------- 15
4.1 User Interfaces ----------------------------------------------------------------------------------------------- 15
4.2 Communications Interfaces -------------------------------------------------------------------------------- 15
5. Other Nonfunctional Requirements -------------------------------------------------------------------- 15
5.1 Performance Requirements --------------------------------------------------------------------------------- 15
5.2 Security Requirements -------------------------------------------------------------------------------------- 15
5.3 Software Quality Attributes -------------------------------------------------------------------------------- 16
5.3.1 Usability: 16
5.3.2 Robustness: 16
6. Appendix A: Glossary ---------------------------------------------------------------------------------------- 20
7. Size Estimation ---------------------------------------------------------------------------------------------------21
7.1 LOC(Line Of Code) Estimation 21
7.2 FP(Function Point Calculation) 21
8. Schedule, Time , Man Power Estimation---------------------------------------------------------------------22

2
1. Introduction

1.1 Purpose
This SRS document provides a comprehensive summary of the Airline Flight Booking
system, version 1.0. It is the customer requirements analysis that outlines the functional and
non-functional needs of the airline's website and its various functions. It outlines the system's
capabilities, responses to inputs, guidelines, and constraints. This paper will be
comprehensive regarding the system's scope and required functions. The system provides a
means for the user to search for flights that meet their requirements, reserve seats, manage
their account, and book flights.

1.2 Document Conventions

The document is in the format required by IEEE (IEEE Std. 830 1998).

1.3 Intended Audience and Reading Suggestions

This document is for EasyFly. which is a flight booking website.

1.4 Project Scope

The website for flight booking is a user-server-hosted application.The goal of the website is to
enable users to complete tasks associated with flight booking.

1.5 References
-Software Engineering: A Practitioner's Approach, by Roger S. Pressman. McGraw-Hill, 2005, New
York
-Lecture s slides

3
2. Overall Description

2.1 Product Perspective

This undertaking represents the first iteration of the Airline Booking system. All of these
requirements define a system that is self-sufficient. A user will be able to book flights,
check flights, do account maintenance, and query flight information using this project. The
aim is to provide clients with better and simpler access to the airline's booking system
twenty-four hours a day, seven days a week.

2.2 Product Features

We may divide the project into seven major components. The following functions are
described in detail in Section 3.

2.2.1 Login
Description: This tool enables a registered user to log in to their account using their
username and airline's password. If a user is not registered, the
website must give them the option to register. When a user attempts to
log in, both the username and password will be verified.
Rationale: This ensures the security of the system by authenticating each
member and gives the consumer assurance that his or her personal
information is protected.

2.2.2 Registration

Description: This feature permits unregistered users to register and create an

account on the website. A user's name, email address, and
password are required when creating a new account. During the
registration procedure.The system verifies that all required data
have been entered before prompting the user, if necessary, to
provide additional information. After the user provides all
essential information, then user will be able to register.

4
 Rationale: A user must be logged in to purchase flights and access all features.
2.2.3 Book Flights
Description: The Book Flights function allows the user to purchase plane tickets.
The system should display information on all current flights to the
user. The user can then choose flight (departure andarrival) on which
to purchase seats. The user can specify the number of seat and their
location.
Rationale: The core of the business is the sale of airline seats. This section
serves as the primary origination point for system transactions.
2.2.4 Reserve Seats
Description: The Reserve Seat function allows the user to reserve seats for an
airline flight. The user selects seats from each flight, where the
number of seats picked for each flight corresponds to the number of
seats booked for that flight. After selecting the flight seats, the user
verifies the seat selection.
Rationale: Customers prefer to know the location of their seats. In addition,
they prefer to select specific seats, such as those closer to the front,
window seats, aisle seats, etc.
At that moment, the seats are withdrawn from available/unreserved
seats and linked to the user's reservation for those specific seats. If
the user fails to reserve a seat prior to the flight's departure, the user
is assigned a seat at random from available seats 30 minutes before
to the flight's departure. This capability is available immediately
after booking, and the customer can book seats at any moment up
until 30 minutes before their departure.

2.2.5 Flight Status

Description: This part shall provide the user, whether or not enrolled, to view flight
information that meets the entered criteria. The user will focus on
providing:
1. Date and a flight number
OR
2. Cities and dates of departure and arrival.

The system will show the following fields along with any matching
flight data:

5
 Departure City
Flight Information
Arrival City

Rationale: Even if they're not at an airport, users will want to use the system to
find out about flights (e.g., on their mobile phone). By putting this
information on our website, we can give the customer an extra
service and make our company more valuable.

2.2.6 My Account

Description: This section enables the user to view, save, change, or remove the
account information. The user can view the status of a booked flight,
cancel a booked flight (optional).This feature is restricted to registered
users only.
Rationale: A customer's information varies with time. Giving users the ability to
amend their account information enables the organization to maintain
current and precise info.

2.2.7 Logout

Description: The Logout feature allows the user to log out of the system in a
secure manner. This procedure will save all user actions after the user logs out of
the system. To access user features, a user must log in again if he or she wishes to
continue using the website.
Rationale: Customers typically utilize shared machines. Providing a means to clear
state and log out ensures that no one else will utilize a customer's flight
booking session.

6
2.3 User Classes and Characteristics
The system's primary actors are (1) the user, (2) the flight, and (3) the Flight Seat. The user
will select a flight and reserve seats onboard. Then, they will reserve particular seats on the
aircraft. Following are brief explanations of various classes:
User
o Has characteristics like Name,Email.
o Associated with obtained Flight Miles and Credit Card details.
o able to book and cancel the ticket.
Admin
o Associated with the Add flights task
o Able to book and cancel the ticket
Crew
o Associated with the checkIn task.
.

A user may be associated with many flights, and multiple users may be associated with a
single flight. Thus, a many-to-many association exists as a result of flight reservations.

There are many Flight Seats that go with flights. Each seat on a flight only goes with one
flight. So, this is a relationship between one and many.
The flight is merely an object to be acted upon, so considerable consideration should be
given to the user's booking experience. The user is our most important client.

7
3.System Features
This section contains specific criteria for the website's layout, including functional
specifications.

3.1 Tabular SRS for General Requirements

3.1.1 Login
Description and Priority: A registered user can access this service to log into his account
account using his username and a password. The website
must allow users to register if they are not already doing so.
When a user tries to login, the system will verify both the
username and the password.

The username is typically convenient for both system

performance and the user. The user can recall their flight
numbers with ease but not a repetitive string. The system will
simultaneously deliver flight details when given the flight
number. As a result, such an operation decreases the risk of a
second query.

Theoretically, several records can be retrieved using the

frequent flight number and password of the user. Multiple
people may have selected the identical password and flight
number. In the event of a tie, the system will request the
user's email confirmation in order to determine the winner.
Inputs: Password and UserName

Source: The user provides all input.

Outputs: A message informing that the user is logged in to the system.

Destination: The outputs are recorded in the system and shown on the screen.
Requires: The user gives authentication details like frequent flyer
number and password.
Pre-Conditions: User is not currently logged in. User has previously registered.

Post-Conditions: Either the user is logged in to the system or the user is not logged in due
. to a result of entering invalid data.

Side-Effects: None

8
3.1.2 Enrollment

Description and Priority: This feature permits unregistered users to register and create an
account on the website. A user's name, email address, and
password are required when creating a new account.

The system verifies that all required data have been entered
before prompting the user, if necessary, to provide additional
information.
Inputs: Required: First name, last name, email address .

Source: The user inputs all data except the frequent flyer number.
The frequent flyer number is obtained from the system
database..
Outputs: Frequent Flyer Number

Destination: Upon completion of the "enrollment" function to account

information, the modifications are committed. The screen
also provides all information to the user.

Pre-Conditions: The user must not already have an account on the site.
Post-Conditions: User account is created, and the user has access to all features
offered by the "My Account" function (refer to 3.1.7)

Side-Effects: None

9
Stimulus-Response:

User Action System Application

I. The system displays a list
of required information that
the user must submit to
create a new account.

II. By filling in fields, the user III. The system determines

submits information whether the user has
including first name, last provided all required
name, address, email information. If a required
address, credit card piece of information is
information, and password. missing, the system prompts
Some information is the user to submit it before
optional, while some are continuing with the account
mandatory (see section 2.2 creation.
of REQ-02).
IV. When all essential
information is submitted,
the system generates an
account and a unique flyer
number that must be used
for subsequent
authentication.
Additionally, the system
transmits the user account
information, including the
flyer number, to the email
address

10
 supplied by the user during
account creation.

3.1.3 Book Flights

Description and Priority: Utilizing the Book Flights feature, the user can purchase airline
seats. The system must provide the user with details on all
active flights. The user may next choose a flight pair
(departure and return) in order to purchase seats.The user can
specify the quantity and arrangement of seats. Finally, the
system should assist the user through the entire checkout
procedure.
Inputs: User information; the user must be currently logged in.

Source: Except for flight information, which is obtained from the

system, all inputs come from the user.
Output: The purchased tickets are associated with the user's
account, allowing the user to reserve seats in the future.

Destination: The booked flights will be stored in the user's account

information once payment has been completed.
Additionally, the flight information must be displayed
on the screen.

Pre-Conditions: The user must have an account on website and be logged in

to access the content.

Post-Conditions: This function guarantees that the user has a seat on a particular
flight. However, if the user desires specific seats, he or she
must also utilize the function to book seats. Any flight
booked successfully through this service is assumed to have
completed payment.

Side-Effects: Account of the user is charged. A flight is linked to the user's account.
Stimulus/Response:

User Action System Application

I. The system determines whether the
user is logged in; if not, the user is
required to log in. The system
displays a list of the user's
previously booked flights together
with the available seats on those
flights.
II. The user picks individual seats from a III. The system verifies whether the
list of flights that have been pre- selected seats remain available.
booked.

11
 The seats are selected in pairs, If available, the seats are made
allowing the user to select momentarily unavailable to other
individual seats for the outgoing users so that the user can confirm
and incoming flights. their choices. The seat selection and
confirmation screen is presented.

IV. On the screen, the user confirms their V. When a reservation is confirmed,
seat selections. the seats are reserved specifically for
that person and added to their
account. Users are presented with a
confirmation screen that shows their
chosen seats and their account
details.

Activity Diagram:

3.1.4 Reserve Seats

Description and Priority: The Reserve Seat option allows the user to select seats for a later
transport via airplane; flight. Reservations made by the user
in the past are used as a starting point in locating available
seats. The Book Flight feature was formerly used for making
these reservations (SEE 2.2.3).

12
 The system needs to show the user where they can sit on their
departing and incoming flights. The number of seats chosen
from each flight corresponds to the number of tickets
purchased for that flight. When a passenger has chosen their
seats for a flight, they must then confirm their choice.
Inputs: The user's information is utilized to track down previously booked
flights.Reservations for specific seats will be made by the user.

Source: Aside from flight details, which are received

automatically, all inputs come from the user.

Outputs: Selected Seats

Destination: After a user finishes using the Reserve Seats feature, the updated
the updated details are permanently saved to their account. On
the screen, you may also see which seats have been picked.

Pre-Conditions: The user must be logged into their website account. In addition,
the user must have previously booked flights where no seats
were secured for them in advance (either by the user or the
system).
Post-Conditions: Each seat option made by a user must be associated with their profile.

Side-Effects: These selected seats are now closed to further sales.

13
Stimulus/Response:

User Action System Application

I. First, the system verifies whether or
not the user is currently
authenticated; if not, the user is
prompted to do so. In response to
the user's input, the system displays
a list of available flights that meet
their criteria.
II. The user decides on a single flight III. The programme verifies that the
or a set of itineraries (round trip). necessary number of seats is still
To reserve a specific number of available on the selected flight(s). If
seats, customers simply select that they are, the system will let the user
number. know that the booking procedure for
their flight has begun and that they
must now finish making their
payment. If all available seats have
been taken, the system will inform
the user of which flights have been
oversold and take them back to the
start of the function.

14
 be modified to reflect the additional
available seats, and the user's profile
would be changed to reflect the
reserved flight. A final confirmation
screen is presented to the user,
detailing their upcoming flight in
addition to their account details.

3.1.5 Flight Status

Description & Priority: Whether or whether they have signed up for the service, users
of this part will be able to see flight data that meets their
specified criteria. The user must supply:
a. A flight number and
Date OR
b. Departing/Arriving Cities and Date.

The system will display matching flight information

including the following fields:
o Flight Number
o Departure City
o Arrival City
Inputs: Departing city, Destination city, Departure date/time

Source: All inputs are provided by the user.

Outputs: Flight information including Flight Number, Departure
City, Arrival City, and Flight Status.

Destination: All outputs should display on the screen.

Pre-Conditions: None.

Post-Conditions: user can check the status of any flights that match their search.

Side-Effects: None

3.1.6 Flight Schedule

Description & Priority: A user will be able to query flight schedules using minimal
minimal criteria with this component of the system. The user
is required to input a departure date, as well as an arrival and
departure location. The following data will be displayed if
any flights meet the criteria:

15
 o Flight Number
o Departing City & Date/Time
o Arriving City & Date/Time
A "matching" flight is one that uses the user-supplied
destination and arrival cities and has a flight time greater than
or equal to the user-supplied time. If no suitable flights are
found, the system will notify the user accordingly.
Inputs: Destination City, Departure Date/Time, Departing City
Source: All inputs provided by the user.
Outputs: Flight Information Including Flight Number, Departure City
and Date/Time, Arrival City and Date/Time, and the Number
of Available Seats.
Destination: All output should display to the screen.
Pre-Conditions: None

Post-Conditions: User has access to flight details for any matched flights.
Activity Diagram:

16
3.1.7 My Account
Description & Priority: This section allows the user to view, save, amend, or remove
the account information. The user can check his/her accrued
points, points, view the status of a booked flight, cancel a
booked flight (optional), and update his/her address,phone
number, email address, or password. This feature is restricted
to registered users only.
Inputs: Account modifications made by the user, if any. Account
modifications include modifications to the first name, last
name, email address, mailing address, password, and
telephone number.
Source: All data are inputs from the user.

Output: None.
Destination: When the My Account function is completed, the account
function to account information.

Pre-Conditions: Prior to accessing his or her account, the user must be logged in
and have a website account.

Post-Conditions: All user-submitted modifications are applied to the user's

account upon completion of the function.

3.1.8 Account Log out

Description & Priority: The Logout feature allows the user to log
out of the system in a secure manner. The procedure will save
all user actions after the user exits the system. If a user wishes
to continue using the website, he/she must re-login in order to
access user features.
Inputs: None.

Source: N/A
Outputs: Notification that the user is logged out.

Destination: Users are notified by display to screen.

Pre-Conditions: User is logged in to the system.

Post-Conditions: User is logged out of the system.

Side-Effects: Once the user logs out, the system clears their session state.

17
 4.External Interface Requirements

4.1 User Interfaces

Every screen will feature a Help link that describes each page's function to the user. The
implementation should be designed so blind users can interact with the system.

4.2 Communications Interfaces

The system must use the standard HyperText Transfer Protocol (HTTP) to ensure
optimum interoperability with browsers. The client gains access to the system via a
web browser.

5.Other Nonfunctional Requirements

5.1 Performance Requirements

The Airline Website must have the capacity to accept 500 connections simultaneously. For
each session, the system must ensure a connection time of five minutes from the last input,
beyond which it will be regarded to have expired. Upon expiration, a close operation will
be executed. This design is intended to meet the usability and connection requirements of
every user.
After receiving a user-submitted form, the system shall send out verification requests
instantly (within 100 milliseconds).
All flight status information will be updated every 5 minutes.

5.2 Security Requirements

Minimum password length is eight characters and one to seven digits are required.
Email addresses should be validated prior to granting access to the system. This
verification will be performed by sending a confirmation email to the prospective user
after enrollment. This email must contain information pertinent to the enrollment
procedure.

All client-to-server exchanges involving sensitive data must utilize the highest level of available security
(e.g., https).

18
 5.3 Software Quality Attributes

5.3.1 Usability:

The design of the airline's website must permit deployment on both Windows and
UNIX (Linux) servers.

5.3.2 Robustness:
The system design must incorporate recovery scenarios that enable the ability to
restore a state that is no more than one business day.

19
6. Appendix A: Glossary
Authentication Identification of an individual, typically based on
username and password

Cached A method of storing information or data that is

frequently accessed.
CSS CSS is a feature that gives users and developers greater
control over how web pages are displayed.
Database A database is a collection of organized records or data
stored in a computer system. This may pertain to flight logs
or user information in our system.
Dynamic Links A pointer to a specific scope invoked at runtime.

Encryption Algorithm A mathematical procedure for encrypting data,

which involves converting the data into secret code.

HTTP HyperText Transfer Protocol is the protocol upon which the

World Wide Web is built. It specifies how messages are
formatted and transmitted, as well as the actions required in
response to various commands.

Hyper Links A hyperlink is a reference that can be followed directly

within a hypertext document.
Input Criteria A specific group of defined criteria that defines inputs.

Query or Queries A form of interrogation. In this document, query is a

search that a user enters into a search engine to retrieve results.

20
 Size Estimation

Loc (Line of Code): 10,000

FP (Function Point):

Number of Inputs:10
Number of Outputs: 4
Number of External interfaces:3
Number of Files:7
Number of Inquiries:3

Step-1:
DI = 14 * scale,
Scale = 3(Average),
DI= 42

Scale varies from 0 to 5 according to the character of Complexity Adjustment Factor (CAF). Below table
shows scale:

Step-2: Calculate Technical Complexity Factor (TCF).

TCF = 0.65 + ( 0.01 * DI )
TCF = 0.65 + (0.01 * 42)
TCF = 0.65 + (0.42)
TCF = 1.07

21
Step-3: Calculate Unadjusted Function Point (UFP).

UFP = (Number of inputs)*4 + (Number of outputs)*5 + (Number of inquiries)*4 + (Number of files)*10 +

(Number of interfaces)*10
UFP = (4*10)+(4*5)+(3*4)+(7*10)+(3*10)
UFP = 172

TABLE (Required):

Function
Low Avg High
Units

Number of
3 4 6
inputs

Number of
4 5 7
outputs

Number of
3 4 6
inquiries

Number of files 7 10 15

Number of
5 7 10
interfaces

22
Step-4: Calculate Function Point.
FP = UFP * TCF
FP = 172*1.07
FP =184.04

COCOMO Model:

We are using the Basic COCOMO Model.

.
Step 1 : Calculate Effort (E)

Effort (E) = a1 × (KLOC)^a2 person-month

Effort = 2.4*10^1.05
Effort = 26.92 person-month

Step 2 : Calculate Timedev (Time required for development):

Timedev = b1 × (Effort)^b2 months
Timedev = 2.5* 26.92^0.38
Timedev = 8.73months

Step 3 : Calculate Project Cost (C)

Project Cost (C) = E * Manpower cost per month
Project Cost (C) = 26.92 * Rs.15,000
Project Cost (C) = Rs. 403,800

Step 4 : Calculate Productivity (P)

Productivity (P) = KLOC / E KLOC per person-month
Productivity (P) = 10/26.92 26.92
Productivity (P) = 0.37 KLOC per person-month

Step 5 : Calculate Average Staffing Size (SS)

Average Staffing Size (SS) = E / Timedev persons
Average Staffing Size (SS) = 26.92/8.73
Average Staffing Size (SS) = 3.08 persons.

23
References: -

https://www.javatpoint.com/spring-boot-tutorial
https://www.tutorialspoint.com/maven/index.htm
https://www.tutorialspoint.com/mongodb/index.htm
https://davcollegetitilagarh.org/wp-content/uploads/2020/09/fundamentals-of-
software-engineering-fourth-edition-rajib-mall.pdf
https://www.tutorialspoint.com/software_testing_dictionary/software_requirement
_specification.htm
https://www.w3schools.com/angular/default.asp

24