SOFTWARE REQUIREMENT SPECIFICATION

AIRLINE RESERVATION SYSTEM:

Objective:

The Software is titled ARS (AIRLINE RESERVATION SYSTEM).

The main goal of the proposed system is to make online the processes of the air ticket reservation and cancelation
system. It includes user registration, user login, contact the company, booking instructions, book flights, book
motel, booking packages, login/logout, add delete or modify (package, motel, customer and flight) information,
cancellation of reservations, email confirmations and modify details regarding web page. It also includes viewing
flight details, reserving and cancelling tickets, constraints, reservation details, flight number and name,
start and destination stations, seat availability, Accessibility, Privacy , Security, Reliability,
Response time, Robustness, Scalability.

Introduction:

Purpose

The purpose of this SRS is to describe the requirements involved in developing a Airline
Reservation system. The project is mainly made to set stage for design phase of the project. The
intended audience is any person who wants to reserve or cancel tickets or to check the
availability of Airline tickets.

Project Scope

The product will perform the following tasks. 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. If the tickets are available to the user’s needs and 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.
Step 2:

Overall Description

Product Perspective

Every Airline company is charged with the responsibility of ensuring to give safe and comfortable service for its
customers. In the manual system, the daily reservation list for all flights is generated and sent. Very often, they
cannot put up the reservation list on time. Owing to the inefficiencies in the manual system, when passengers
cancel tickets, the reservation list is not updated in time. The limitations of the manual system are:

1. Only few bookings could be made due to manual operation.

2. It takes enormous amount of time for recording transactions.

3. Requires a large amount of manual laborers.

4. Customers should go to ticket offices to reserve a ticket and cancel it.

1|Page
SOFTWARE REQUIREMENT SPECIFICATION

To overcome this, it is decided to create a system, which is

 Integrated
 Reliable
 Consistent
 Flexible
 Secure
In this system customers could reserve and cancel tickets from anywhere which have an internet access.

Product Features:

The product functions include viewing flight details, reservation tickets and cancelling of the
tickets. Viewing flight details including flight number, flight name, flight route, flight timings
and seat availability. Reservation details include flight number and route. At last cancelling of
tickets include quoting of ticket number, credit card number and bank name.

User Classes and Characteristics

There are two kinds of users for the Airline Reservation System. One is the customer and
the other is the administrator. The customers do not need to have any training to use the application. 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. However, instructions for
making flight and reservations would be provided to them on the airline website. The
administrators would however need to be trained in order to use the application. The end user is
at a high level of abstraction that allows easier, faster operation and reduces the knowledge
requirement of end user.

Operating Environment

Airline Reservation System should be accessed using any popular versions of the
following: web browsers Microsoft internet explorer and Google Chrome.

Design and Implementation Constraints:

Requires 256 MB on-board memory. Based completely on Windows functionality platform. The
software must be portable and be inaccessible to unauthorized issues. It is mandatory that no text
book will be left empty or contains insufficient data.

Control functions: The software must be very user-friendly and display appropriate error
messages.

Parallel operations: It must support many users simultaneously.

Reliability requirements: Data redundancy and use of special/blank characters must be avoided.

Safety/security considerations: The application must be exited always normally

2|Page
SOFTWARE REQUIREMENT SPECIFICATION

System Features:
System features basically means main entities like flight details, booking and cancellation of
tickets in airline reservation system.

System Feature 1

1 Description and Priority:

The ability of the software is to provide the details of the
flights available and al l o w t h e cus t om e rs t o c hoo s e a p a r t i c ul ar
de st i n at i on an d m ak e a reservation. The purpose of this is to enable the users
to view the different flights available so as to make it convenient for him to make a
reservation

2 Stimulus/Response Sequences:
Once the user chooses the particular option, the web pages corresponding to
that are to be displayed on the screen i.e. it will display the different flights available to
their respective destinations and allow the customer to book a ticket.
3 Functional Requirements
Once the user makes a reservation, he must be provided with a pin code. The user
must be provided with the required information within seconds. The user must enter the
reservation destination date and timings by giving his personal details. When all the
details are entered it displays message of confirming and gives pin code.
FEATURE 2
The software modifies the user to make change in existing reservation if in case there are
any changes which had to be made.
1 Description and priority:
This feature will allow the users to make any changes in his personal details or
flight booking details.
2 Stimulus/ Response sequence:
Once the user requests for changing in reservation, it must be displayed on the
screen prompting the customer to enter his pin code.
3 Functional requirements:
If the pin code provided must not match then it displays error messages. The
system will allow modifying the customer provided correct pin code has entered by him.
The user should enter his pin code which gives him access to to modify his reservation.
Giving the correct pin code thus user can get allow to access his reservation as he will
receive new pin code by this.

3|Page
SOFTWARE REQUIREMENT SPECIFICATION

MORE REQUIREMENTS:

Form no Input Expected output Actual Status

output

Main menu Menu option Required form is Required Pass

displayed form was
displayed.

Ticket Flight route Seats availability Flight seats Pass

availability must be displayed availability
are
displayed.

Reservation Personal details Ticket must be Ticket was Pass

form are entered booked and database booked and
updated. database
was
updated.

Cancellation Ticket number Ticket must be Ticket was Pass

form is entered cancelled and cancelled
database must be and
updated database
was
updated.

1: Use Case name: user Registration

• Description: This use case describes the scenario where the user registers with the application by providing
all the necessary details, in order to make reservations or bookings for flights, models, special
packages.
• Actor: user or the Customer
• Input: The user or the customer will have to provide all the necessary details present in the
customer registration form of the application
• Output: All the details entered in the customer registration page will be verified and accepted
by the system into the database

2: Use Case name: User Login

• Description: This use case describes the scenario where the user logs into the application, with
the username and password he has provided while registering with the system.

• Actor: user or the Customer

• Input: The user or the customer creates a username and password at the time of registering with the system.
He then uses them to logon to the system and make reservations or view any information
requirements can be (planned in detail as follows)
• Output: The application then verifies the authenticity of the username and password that the
customer has provided and allows the user to view the information available on the system, if the username
and password are valid.

4|Page
SOFTWARE REQUIREMENT SPECIFICATION

3: Use Case name: Contact the company

• Description: This use case describes the scenario where the user contacts the company for any
information.

• Actor: User or the Customer

• Input: The customer can contact the airline company, requesting them for any information he
needs.
• Output: The application verifies the authenticity of the username and password that the
customer has provided and allows the user to view the contact information for the company.
.
4: User Case name: Booking Instructions

• Description: This use case describes the scenario where the user views the instructions for
booking flights, packages, or motels.

• Actor: user or the Customer

• Input: After the customer logs onto the application with his username and password, he can
look up the instructions posted on the website for booking flights, packages or motels.
• Output: The application verifies the authenticity of the username and password and displays
the how to book instructions page.

5 User Case name: Book flights.

• Description: This use case describes the scenario where the user books airline tickets
. • Actor: User or the Customer

• Input : After logging into the application, the customer looks up the information related to
various airlines and checks the availability of seats on flights. If he finds that there are any
available tickets, he then purchases them.
• Output: The application verifies the authenticity of the username and password and then
displays information related to various flights to the customer.

6 User Case name: Book motels"

• Description: This use case describes the scenario where the user books motels at the time of
airline ticket reservation.
• Actor: Customer or the user

• Input: After logging onto the application, the customer looks up the information for all the
available motels at his destination.
•Output: The application verifies the authenticity of the username and password and then
displays information pertaining to various motels at the customer’s destination.

7 Use Case name: Booking packages

5|Page
SOFTWARE REQUIREMENT SPECIFICATION

• Description: This use case describes the scenario where the user books different touring
packages at the airline ticket reservation

• Actor: Customer or the user

• Input: The customer looks up information regarding various touring packages available at his
destination at the time of airline reservation system.

• Output: The application verifies the authenticity of the username and password of the customer
and then displays information of various touring packages available at customer’s choice of
place.

8 Use Case name: Login (Logout)

• Description: This use case describes the scenario where the administrator of the application, logs
into the system and logs out after the work is done.
• Actor: Administrator
• Input: The administrator of the website logs into the application with the username and
password provided to him.
• Output: The application verifies the authenticity and displays the home page of the
administrator.

9 Use Case name: ADD(Delete or Modify Customer information)

• Description: This use case describes the scenario where the administrator adds, deletes or
modifies customer information in the system database

• Actor : Administrator

• Input: The administrator of the applications logs onto the system with his username and
password.
• Output: The application authenticates the administrator, and then displays the page where the
administrator can add new customers to the database, or delete existing customers or modify
details of customers in the database.

10 : Use Case name: ADD(Delete or Modify fight information)

• Description: This use case describes the scenario where the administrator adds, deletes or
modifies flight information in the application database
• Actor: Administrator

• Input: The administrator logs onto the system with the username and password provided to him.

• Output: The application authenticates the administrator, by verifying the username and
password. Then the application displays the page where the administrator can add new flights to
the database, delete the flights that have been cancelled or modify information for the flights.

11: Use Case name: Cancelation of reservations

6|Page
SOFTWARE REQUIREMENT SPECIFICATION

• Description: This use case describes the scenario where the administrator handles the
cancellation of reservations by the customers.
• Actor: Administrator
• Input: The administrator logs onto the system with the given username and password
• Output: The application authenticates the administrator and then displays the page where the
administrator looks up the id of the customer who has requested cancellation of reservation.
After canceling the reservation, the administrator then sends a confirmation email to the
customer
.
12: Use Case name: Email confirmations

• Description: This use case describes the scenario where the administrator sends email
confirmations to the customers of the application.

• Actor: Administrator

Input: The administrator logs onto the application with the username and password provided.
• Output: The application then authenticates the administrator and displays the page where the
administrator can send email confirmations to the customer. These email confirmations may be
sent in cases where the customer has cancelled a reservation or changed the personal information
available on the website

13: Use Case name: Modifying details of web page:

• Description: This use case describes the scenario where the administrator logs onto the
application to modify the details of the airline website
• Actor: Administrator
• Input: The administrator logs onto the application with the username and password provided to
him
• Output : After verifying the username and password of the administrator, the application then
allows the administrator to login. The administrator can then browses through the website and
change the details of any webpage in the Airline Reservation system application.

14: Use Case name: ADD (Delete or modify motel information)

• Description: This use case describes the scenario where the administrator adds, deletes or
modifies motel information in the database.
• Actor: Administrator
• Input: The administrator logs onto the system with the username and password provided to him.
• Output: The application authenticates the administrator, by verifying the username and
password. Then the application displays the page where the administrator can add new motels to
the database, delete a specific motel from the list of motels, since there are no more available
rooms there. &e can even update the price per room of each motel. To make it easier, the
administrator might assign a unique id for each hotel.

15: Use Case name: ADD(Delete or modify package information)

• Description: This use case describes the scenario where the administrator adds, deletes or
modifies package information in the application database

7|Page
SOFTWARE REQUIREMENT SPECIFICATION

• Actor: Administrator
• Input: The administrator logs onto the system with the username and password provided to
him.
• Output: The application authenticates the administrator, by verifying the username and
password. Then the application displays the page where the administrator can add new packages
to the database, delete the packages that are no longer available or modify information for any

particular package .

External Interface Requirements

User Interfaces

There are two types of users for the Airline Reservation System project. 'ne is the customer and the
other is the administrator. Both the customer and administrator user interface would be a
graphical user interface. The graphical user interface for the customer home page would be as
follows The graphical user interface would mainly consist of hyperlinks, /data entry fields like
the "email id field, push down buttons like the login button etc. The administrator of their
website would also have a similar graphical user interface.

Hardware Interfaces:

Hard disk:
The database connectivity requires a hardware configuration with a fast database
system running on high rpm hard-disk permitting complete data redundancy and back-up
systems to support the primary goal of reliability. The system must interface with the standard
output device, keyboard and mouse to interact with this software.

Software Interfaces:

The application should run on a windows 8 ultimate operating System. Since

the application needs a database to store all the customer details, airline, motel and package
information. visual Studio would be used for creating the application.

Communications Interfaces:

Airline reservation System should send an email message to the user to

confirm the acceptance of acceptance of reservation. Airline Reservation System is a web
database system, all kinds of user system interaction is presented by user side web browser. So
the communication standard is &TT; protocol.

8|Page
SOFTWARE REQUIREMENT SPECIFICATION

Nonfunctional Requirements

Performance Requirements:

The Airline Reservation System application should be able to respond to the

queries submitted by the customer without much delay. When a user searches for a flight leaving from a
particular place to another place, the application should not take much time to return the results, similarly for the
motel and package information. Considering that the application is of moderate size, it should be able to display
10 results at a time on each page, when the customer looks up for any particular data. Since the Airline
Reservation websites have much traffic, the user should also be able to logon to the system using high speed
internet. Most of the requests sent to the application should be answered in less than 5 seconds.

Safety Requirements:

Users shall be required to log in to the Airline Reservation System for their own
reservation information and modification with email address and password. The system shall permit only
authorized members who are on the list of authorized menu managers to do administrators task. The
system shall permit customers to view only their own previously placed orders, not orders placed
by other customers
Security Requirements:

Users shall be required to log in to the Airline Reservation System for their own
reservation information and modification with email address and password. The system shall permit only
authorized members who are on the list of authorized menu managers to do administrators task. The
system shall permit customers to view only their own previously placed orders, not orders placed
by other customers.

Software Quality Attributes

AVAILABILITY:

The Airline system shall be available to users on the internet 99.9% of the time
between 5am and midnight local time and 95% of the time between midnight and 5am local
time. And it should be available to administrators all the time.

ROBUSTNESS:

If the connection between the user and the system is broken prior to an order being
either confirmed or canceled, the online system shall enable the user to recover an incomplete
reservation.

9|Page
SOFTWARE REQUIREMENT SPECIFICATION

CONSISTENCY:

The ticket availability in Airline system shall be updated when a transaction

(more, administrators update operation) is finalized to ensure that the most updated information
is delivery to any following queries from other customers. When administrator is updating the
information, the consistency should also hold among user view.

Scalability:

Whenever some resources are added within the existing function it helps in
increasing the quality of the system.

ENTITY RELATIONSHIP DIAGRAM:

10 | P a g e
SOFTWARE REQUIREMENT SPECIFICATION

USE CASE DIAGRAM

11 | P a g e
SOFTWARE REQUIREMENT SPECIFICATION

CLASS DIAGRAM:

12 | P a g e