Software Requirements

Specification
For

Air Ticket Reservation

System
Software Requirements Specification for Air Ticket Reservation System
Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History............................................................................................................................iii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Scope..........................................................................................................................................1
1.3 Definition, Acronym, Abbreviation..............................................................................................1
1.4 References...................................................................................................................................1
1.5 Overview.....................................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective.....................................................................................................................2
2.2 Product Functions.......................................................................................................................2
2.4 Operating Environment...............................................................................................................4
2.5 Design and Implementation Constraints......................................................................................4
2.6 User Characteristics....................................................................................................................4
2.7 Assumptions and Dependencies...................................................................................................5
3. External Interface Requirements............................................................................................5
3.1 External Interfaces Requirements................................................................................................5
3.1.1 User Interfaces.................................................................................................................5
3.1.2 Hardware Interfaces.......................................................................................................13
3.1.3 Software Interfaces........................................................................................................13
3.1.4 Communications Interfaces............................................................................................13
    3.2     Functional Requirements……………………………………………………………...13
4. System Features......................................................................................................................14
4.1 Login........................................................................................................................................14
4.2 Book Tickets.............................................................................................................................14
4.3 View Flight Schedule................................................................................................................14
4.4 View Ticket...............................................................................................................................15
4.5 Cancel Ticket............................................................................................................................15
4.6 Logout......................................................................................................................................15
5. Other Nonfunctional Requirements.....................................................................................16
5.1 Performance Requirements........................................................................................................16
5.2 Safety Requirements.................................................................................................................16
5.3 Security Requirements..............................................................................................................16
5.4 Software Quality Attributes......................................................................................................17
Appendix A: Glossary..................................................................................................................17
Appendix B: Analysis Models.....................................................................................................18
Use case Diagram...........................................................................................................................20
Software Requirements Specification for Air Ticket Reservation System
Page iii

Revision History
Name Date Version
Air Ticket Reservation System 1st November 2019 1.0.0
Software Requirements Specification for Air Ticket Reservation System
Page 1

1. Introduction
Ticket reservation system for airlines 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 has 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 the availability of tickets, the ticket has to be issued. The ticket issued
should contain the following information –ticket number, flight no, flight name, date
of journey, number of passengers, sex, age and departure time.
6. Cancellation of booked tickets should be available.

1.1 Purpose

The purpose of this SRS is to describe the requirements involved in developing a 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
1) The product is titled Airline Reservation system (ARS).
2) The product will perform the following tasks –
i) The software that is being developed can be used to check the availability of
the flight tickets for the specified flight, destination and date of journey
ii) If the tickets are available to the user needs and specification, then the software
provide a facility to book the tickets.
iii) If the passenger wants to cancel the tickets, he can use the cancellation module
of the Airline Reservation System. .
Software Requirements Specification for Air Ticket Reservation System
Page 2

1.3 Definition,  Acronym,  Abbreviation

ATRS : Airline Ticket Reservation System

1.4 References
The references for the above software are as follows:-

i. www.google.co.in

ii. www.wikipedia.com

iii. IEEE. Software Requirements Specification Std. 830-1993.

1.5 Overview

 The SRS contains an analysis of the requirements necessary to help easy design.
 The overall description provides interface requirements for the Airline Reservation
system, product perspective, hardware interfaces software interfaces,
communication interface, memory constraints, product functions, user
characteristics and other constraints.
 Succeeding pages illustrate the characteristics of typical naïve users accessing the
system along with legal and functional constraints enforced that affect Airline
Reservation system in any fashion.
Software Requirements Specification for Air Ticket Reservation System
Page 3

2. Overall Description

2.1 Product Perspective

The ATRS is designed for everyone who wishes to easily book air tickets. This
software provides options for viewing different flights available with different
timings for a particular date and provides customers with the facility to book a
ticket, modify or cancel a particular reservation but it does not provide the
customers with details of cost of the ticket and it does not allow the customer to
modify a particular part of his reservation and he/she can modify all his details.

2.2 Product Functions

1. A system is to be implemented which can run on the web server.
2. The system shall be able to generate Login Id and password to the system
operator.
3. There are 3 types of members in the reservation system: User, Airlines and Admin.
4. The administrator shall be able to maintain details of all the flights.
5. The administrator shall be able to maintain details of all the users.
6. The system shall be able to book tickets.
7. The system should give the user the option to cancel the confirmed ticket.
8. A guest user can only check the availability of tickets and cannot block or buy
tickets.
9. The system shall be able to fetch all the flights from origin to destination.
10. The system shall allow user to access the details about the arrival and departure
times by requesting the user to input the flight number and date.
11. The user should be able to view all the past bookings.
12. The system shall be able to update the profile of the users.
13. The system shall be able to update the schedules of flights

2.3 Operating Environment

The ATRS is designed to be accessed through most of the versions windows operating
systems such as:

 Windows 2000
 Windows XP
Software Requirements Specification for Air Ticket Reservation System
Page 4

 Windows Vista
 Windows 7
 Windows 8
 Windows 10

2.4 Design and Implementation Constraints

At the time of reservation, each user is provided a unique ticket number that must be
used for further operation like cancellation. Hence the user is required to remember or
store this number carefully.

2.5 User Characteristics

1. The intended users of this software need not have specific knowledge as to what is
the internal operation of the system. Thus the end user is at a high level of
abstraction that allows easier, faster operation and reduces the knowledge
requirement of end user
2. The Product is absolutely user friendly, so the intended users can be the naïve
users.
3. The product does not expect the user to possess any technical background. Any
person who knows to use the mouse and the keyboard can successfully use this
product.

2.6 Assumptions and Dependencies

The requirements stated in the SRS could be affected by the following factors:

One major dependency that the project might face is the changes that need to
be incorporated with the changes in the airline policies regarding different
services. As the policies changes the system needs to be updated with the
Software Requirements Specification for Air Ticket Reservation System
Page 5

same immediately. A delay in doing the same will result to tremendous loss to
the airline. So this should be changed as and when required by the
developer..
At this stage no quantitative measures are imposed on the software in terms
of speed and memory although it is implied that all functions will be optimized
with respect to speed and memory.

It is furthermore assumed that the scope of the package will increase considerably in
the future.

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

1. Login Interface
Software Requirements Specification for Air Ticket Reservation System
Page 6

2. Book Ticket Interface

3. View Flight Schedule Interface

4. View Ticket Interface

Software Requirements Specification for Air Ticket Reservation System
Page 7

5. Cancel Ticket Interface

6. Logout Interface
Software Requirements Specification for Air Ticket Reservation System
Page 8

3.1.2 Hardware Interfaces

The minimum hardware requirements of Air Ticket Reservation System are a 1 Gegahertz
CPU and 2 Gegabytes of RAM. The system must interface with the standard output
device, keyboard and mouse to interact with this software.

3.1.3 Software Interfaces

ATRS is a desktop application and designed to be accessed by most of the versions of

windows operating systems.

ATRS can be connected with a PostgreSQL or MySQL database but the current
development is on MS Access

3.1.4 Communications Interfaces

ATRS might require an internet connection to install new updates.

3.2 Functional Requirements

3.2.1 Login Use Case Description

LOGIN:
Introduction:
This use case describes all the steps followed in order to login into Air Ticket Reservation
System.
Actors:
Administrator, Customer, Airline Staff

Pre-condition:
Administrator/Airline Staff/Customer must have valid username and password.

Post-condition:
If username and password is valid, the actor is successfully logged in to the system; else an
error message will be displayed.

Basic Flow:
Software Requirements Specification for Air Ticket Reservation System
Page 9

1. The system will request the actor to enter their login details for the system.
The actor fills in the following details: -
- Username
- Password
2. If login details are valid after clicking the login button, the actor is successfully
logged into the system.

Alternate Flows:
Alternative Flow 1: Invalid Entry
If username/password entered by actor is invalid or if any field username /password are
empty then the system will display an error message and the actor returns to the basic flow.

Alternative Flow 2: User Exits

User can exit at any time and use case ends.

Special Requirements:
None

Associated use case:

None

3.2.2 Book Ticket Use Case Description

Book Ticket :
Introduction
This use case describes the steps taken in order to book a ticket.
Actors
• Customer
• Administrator
• Airline
Pre Condition
Administrator/Customer/Airline must be logged onto the system before use case begins.
Post Condition
If the use case is successful, a ticket is booked and the database is updated else, the system remains
unchanged.
Software Requirements Specification for Air Ticket Reservation System
Page 10

Book Ticket :
Introduction
This use case describes the steps taken in order to book a ticket.
Flow of Events
Basic Flow
1. This use case starts when the Administrator/Customer/Airline wishes to book a ticket.
2. The system requests Administrator/Passenger/Airline to enter basic details that includes
- Name
- DOB
- Airline
- Class
- Phone No
- Email ID
- Source
- Destination
3. After Successful insertion of all the details the user will be asked to pay for the ticket and the
ticket is successfully booked.

Alternate Flow
• Invalid Details
If in Book Details any invalid detail is mentioned or left blank, the system will display an error
message and return to basic flow.
• Booking Cancelled
If in Book Ticket Use Case Administrator/Customer decided to not book the ticket, the system will
display an error message.
• User Exit
User exit Unexpectedly, the system starts from beginning.

Special Requirement
None
Associated Use case
LOGIN

3.2.3 Cancel Ticket Use Case Description

CANCEL TICKET :
Introduction
This use case describes the steps taken in order to cancel a ticket.
Actors
Administrator
Customer
Software Requirements Specification for Air Ticket Reservation System
Page 11

CANCEL TICKET :
Introduction
This use case describes the steps taken in order to cancel a ticket.
Pre Condition
Administrator/Customer must be logged onto the system before use case begins.
Post Condition
If the use case is successful, a ticket is cancelled and the database is updated else, the system
remains unchanged.
Flow of Events
Basic Flow
1. This use case starts when the Administrator/Customer wishes to cancel a ticket.
2. The use case requires the Administrator/Customer to enter the BOOKING ID into the system
that he/she wants to cancel.
3. The user selects cancel ticket.
4. The appropriate databases are updated and the refund is given to user and the ticket is cancelled.

Alternate Flow
• Invalid Booking ID
If the Booking ID entered is not present, the system will display the message of BOOKING ID
NOT FOUND and will ask the user to enter the BOOKING ID again.
• Time to Cancel ticket is exceeded
If the user cancels the ticket after the 24 hours period, no refund will be given to the user and
ticket will be cancelled.
• User Exit
User exit Unexpectedly, the system goes from beginning and no changes in the system takes place.

Special Requirement
None
Associated Use Case
LOGIN, REFUND

3.2.4 View Ticket Use Case Description
Software Requirements Specification for Air Ticket Reservation System
Page 12

VIEW TICKET :
Introduction
This use case describes the steps taken in order to view a ticket.
Actors
Administrator
Customer
Pre Condition
Administrator/Customer must be logged onto the system before use case begins.
Post Condition
If the use case is successful, a ticket is shown to the user else, the system remains unchanged.
Flow of Events
Basic Flow
1. This use case starts when the Administrator/Customer wishes to view a ticket.
2. The user clicks on the VIEW TICKET tab to view the tickets booked.
Alternate Flow
• User Exit
User exit Unexpectedly, the system goes from beginning and no changes in the system takes place.

Special Requirement
None
Associated Use Case
LOGIN

3.2.5 Refund Use Case Description

REFUND:
Introduction:
This use case describes all the steps followed in order to apply for the refund of cancelled
ticket in Air Ticket Reservation System.

Actors:
Customer

Pre-condition:
Customer must be logged into system and applied for cancellation of ticket.

Post-condition:
Refund if any must be processed in accordance with refund policy of the system.

Basic Flow:
1. The system will request the actor to cancel the ticket in order to apply for refund.
2. If ticket is cancelled in given time period, refund will be processed according to
refund policy of the system.
Software Requirements Specification for Air Ticket Reservation System
Page 13

Alternate Flows:
Alternative Flow 1: User Exits
User can exit at any time and use case ends.

Special Requirements:
None

Associated use case:

Cancel Ticket

3.2.6 Logout Use Case Description

LOGOUT:
Introduction:
This use case describes all the steps followed in order to logout the Air Ticket Reservation
System.
Actors:
Administrator, Customer, Airline Staff

Pre-condition:
Administrator/Airline Staff/Customer must be logged into the system.

Post-condition:
The actor is successfully logged out of the system.

Basic Flow:
1. The system will request the actor to go to the logout button of the system.
2. The actor will logged out of the system and return to the login page.

Alternate Flows:
Alternative Flow 1: User Exits
User can exit at any time and use case ends.

Special Requirements:
None

Associated use case:

Login

3.2.7 View Passengers List Use Case Description

View Passengers List:

Introduction:
This use case describes all the steps followed in order to view passengers list in Air Ticket
Reservation System.

Actors:
Admin
Software Requirements Specification for Air Ticket Reservation System
Page 14

Pre-condition:
Admin must be logged into system.

Post-condition:
Passengers list should be displayed.

Basic Flow:
1. The system will request the actor to select a flight and click on view passengers list.
2. If the corresponding flight has any bookings then passengers details will be shown.

Alternate Flows:
Alternative Flow 1: User Exits
User can exit at any time and use case ends.

Alternative Flow 1: Flight has no bookings

If the flight has no bookings then message will be displayed with zero passengers.

Special Requirements:
None

Associated use case:

None

3.2.8 View Flight Occupancy Use Case Description

View Flight Occupancy:

Introduction:
This use case describes all the steps followed in order to check occupancy in a flight in Air
Ticket Reservation System.

Actors:
Admin, Airline

Pre-condition:
User must be logged into system.

Post-condition:
User must be able to see occupancy in a particular flight.

Basic Flow:
1. The system will request the actor to select a flight and click on view flight
occupancy.
2. The system will display an occupancy list in which details of all booked and vacant
seats of a flight will be displayed.

Alternate Flows:
Alternative Flow 1: User Exits
User can exit at any time and use case ends.
Software Requirements Specification for Air Ticket Reservation System
Page 15

Special Requirements:
None

Associated use case:

None

3.2.9 Check Flight Schedule Use Case Description

INTRODUCTION
This use case describes all the steps followed in order to check the flight schedule in Air
Ticket Reservation System.

ACTORS
Administrator, Customer

Pre-Condition
Actors must be logged in to the system

Post-Condition
Flight schedules are displayed with all the details.

Flow Of Events
Basic Flow
1. This use case starts when the Administrator/Customer wishes to check the flight
schedule.
2. The Administrator/Customer needs to enter the following details:
a. Source City
b. Destination City
c. Date of flight.
3. All the flights of that day is shown to the actor.

Alternate Flow
1. Invalid Date of flight
If the Date of flight is not in correct format or the date entered is before the current
date, the system will display the message RE-ENTER DATE.
2. Source/Destination City is blank
If the Source/Destination city is left blank, the system will show the message
SELECT SOURCE/DESTINATION.
3. User Exit
User exit Unexpectedly, the goes to beginning and no changes in the system takes
place.

Special Requirement
None

Associated Use Case

Software Requirements Specification for Air Ticket Reservation System
Page 16

Login

3.2.10 Update Flight Schedule Use Case Description

INTRODUCTION
This use case describes all the steps followed in order to update the flight schedule in Air
Ticket Reservation System.

ACTORS
Administrator

Pre-Condition
Administrator must be logged in to the system

Post-Condition
Flight schedules are updated with all the details saved in appropriate databases.

Flow Of Events
Basic Flow
1. This use case starts when the Administrator wishes to update the flight schedule.
2. The Administrator needs to enter the following details to update the flight record :
a. Source City
b. Destination City
c. Date of flight.
d. Time of Flight
e. Airline Name
3. The updated details are saved to appropriate databases.

Alternate Flow
1. Invalid Date of flight
If the Date of flight is not in correct format or the date entered is before the current
date, the system will display the message RE-ENTER DATE.
2. Source/Destination City is blank
If the Source/Destination city is left blank, the system will show the message
SELECT SOURCE/DESTINATION.
3. Airline name is blank
If the Airline name is blank, the system will show the message ENTER THE
AIRLINE.
4. User Exit
User exit Unexpectedly, then goes to beginning and no changes in the system takes
place.

Special Requirement
None
Software Requirements Specification for Air Ticket Reservation System
Page 17

Associated Use Case

Login

4. System Features
This section demonstrates ATRS’s most prominent features and explains how they can
be used and the results they will give back to the user.

4.1 Login

 This function allows a registered user to login his account using hisfrequent flyer
number with the airline and password. If a user is not registered, the website shall
allow the user to enroll first. The system will check both the frequent flight number
and password, when a user attempts to login.
 This provides security to the system by authenticating each member and provides
confidence to the consumer that his/her personal information is secure

4.2 Book Tickets

 The user can use the Book Ticket function to purchase seats for an airplane flight.
The system shall present the user with information on all current flights. The user
may then select a pair (departure and return) of flights on which to purchase seats.
The user can indicate the number of seats and placement of such. Finally, the
system shall guide the user completely through the checkout process.
 The heart of the business is selling seats on flights. This section provides the
primary source of system transactions.

4.3 Check Flight Schedule

 The user can use the Check Flight Schedule function to check the schedule of
flight in which the user has booked ticket. Details about departure time, arrival time,
number of hops will be shown by this function.
Software Requirements Specification for Air Ticket Reservation System
Page 18

 There may be instances when flights get delayed or cancelled due to bad weather
or some technicality, so changes in flight schedule will also be shown.

4.4 View Ticket

 The user can use the View Ticket function to view the booked tickets. Every
information about the ticket which is booked by the user will be shown by this
function such as time of booking, no of tickets, details of passenger, source and
destination, class of ticket, payment details etc.

4.5 Cancel Ticket

 The user can use the Cancel Ticket function to cancel the already booked tickets
for an airplane flight. The system shall present the user with information on which
tickets to be canceled if booked more number of tickets from a single account . The
user may then select the corresponding ticket of flight, which needs to be
cancelled. Finally, the system shall guide the user through the cancellation
process and refund policy.

4.6 Logout

 The Logout section provides a way for the user to securely log out of the system.
This process will save all user operations when he/she exits the system. If a user
wishes to continue accessing the website, he/she must log-in again to access user
features.
 Customers often use shared computers. Providing a way to clear stateand log-out
gives our customers confidence that nobody else will use their flight-booking
session.
Software Requirements Specification for Air Ticket Reservation System
Page 19

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The minimum hardware requirements of Air Ticket Reservation System are a 1 Gegahertz
CPU and 2 Gegabytes of RAM. The system must interface with the standard output
device, keyboard and mouse to interact with this software.

5.2 Safety Requirements

To ensure that no one of ATRS’s users loses any data while using ATRS (due to a
crash or a bug of some kind) the developer team updates ATRS regularly.

5.3 Security Requirements

ATRS has three levels of users each with different privileges i.e.
- Administrator who is the super user and can perform most of the functions in the
system such as creating users, view passengers list, view flight occupancy etc.
- Customer/User who can book tickets, cancel tickets, view ticket, view flight
schedule etc.
- Airline Staff who are the employees to the Airline Company. They include
authorize clericals. They can basically view the flight occupancy and if
overbooked can take necessary steps.

5.4 Software Quality Attributes

ATRS provides the users with very simple features. Due to its well designed and
easy to use interface it can be used by any users. However, users must already have
a basic knowledge of using a computer.

Appendix A: Glossary
SRS - Software Requirements Specification
Software Requirements Specification for Air Ticket Reservation System
Page 20

ATRS – Air Ticket Reservation System

IEEE – Institute of Electrical and Electronics Engineers
CPU – Central Processing Unit
RAM – Random Access Memory
Software Requirements Specification for Air Ticket Reservation System
Page 21

Appendix B: Analysis Models

Use case Diagram