SOFTWARE REQUIREMENT SPECIFICATION

AIRLINE RESERVATION SYSTEM:

Objective:

The main goal is to make online the processes of the air ticket reservation and cancelation system. It includes user
registration, user login, contacts to our company, booking details, login and logout, add remove or modify
(package, motel, customer and flight) information, cancellation of reservations, email confirmations and modify
details of our web page. It also includes flight number and name, start and destination stations, seat
availability, accessibility, privacy, security, reliability, response time, robustness, scalability of
system.

Introduction:

Purpose

The main aim of this SRS is to describe the requirements used in developing Airline
Reservation system (ARS). The project is mainly made for design phase of the project. The
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 these tasks such as, 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 an option to book those tickets. If the passengers want to cancel those tickets, he can use
the cancellation option of the ARS.
Step 2:

Overall Description

Product Perspective

Airline companies must be charged with the responsibility of giving safe and useful service for its users. In our
system, the daily reservation list for all flights is created. Very often, they cannot put up the reservation list on time.
Owing to the inefficiencies in the manual system, the limitations of the manual system are:

1. Only few bookings could be made with manual system.

2. It takes large amount of time for transaction records.

3. It requires large amount of workers.

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

1|Page
SOFTWARE REQUIREMENT SPECIFICATION

To overcome this, we 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 (including flight number, flight name, flight
route, flight timings and seat availability). 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 ARS. One is the customer and the other one is
administrator. The customers do not need to have any kind training to use the application. 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 are need to be trained.
Operating Environment
ARS should be accessed using any popular versions of the following: web browsers
Microsoft internet explorer and Google Chrome. The application should run on a windows 8 ultimate
operating System. Visual Studio would be used for creating the application.

Design and Implementation Constraints:

It requires 256 MB memory. It is based on Windows functionality platform.

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

Parallel operations: It must support many users at a time.

Reliability requirements: Data superfluousness and use of special/blank characters must be

avoided.

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

System Features:
System features basically means main entities like user and administrator

2|Page
SOFTWARE REQUIREMENT SPECIFICATION

1. Description and Priority:

The ability of the software is to provide the details of the flights a nd al l o ws ,
t h e cus t om e rs t o c h oos e d est i n at i o n t o m ak e a reservation,
the purpose of this is to enable the users to view the different available flights, so they can
easily make a reservation

2. Stimulus/Response Sequences:
Once the user chooses any option on the web pages, 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, they must be provided by a pin code. Before that 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 allows their users to change in existing reservation if in case there are any
changes are required.
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 display error messages. The user
should enter his pin code which gives him access to modify his reservation.

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.

3|Page
SOFTWARE REQUIREMENT SPECIFICATION

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 case describes user registration with the application by providing all details, in order to
make reservations or bookings for flights, models and special packages.
Actor: user.
Input: The user will have to provide all details present in the customer registration form of the
application on web page
Output: All the details entered in the customer registration page will be verified and accepted by
the system.

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.
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.

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.
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.

4|Page
SOFTWARE REQUIREMENT SPECIFICATION

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

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.

5|Page
SOFTWARE REQUIREMENT SPECIFICATION

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

Description: This use case describes the scenario where the administrator adds, deletes or
change 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

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.

6|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 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
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 package.

External Interface Requirements

User Interfaces

There are two types of users for the ARS project. Customer and the other is the administrator. Both the
customer and administrator user interface would be a graphical user interface. The graphical user
interface would mainly consist of hyperlinks, /data entry fields like the "email id field, like the
login button etc.

Hardware Interfaces:

Hard disk: The hardware configuration with a fast database system running on high rpm hard-
disk allowing complete data redundancy and back-up systems to support the primary goal of
reliability. The system must interface with output device such as keyboard and mouse.
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 and package information.
Visual Studio would be used for creating of application.

Communications Interfaces:

ARS should send email message to the user to confirm the acceptance of reservation. ARS is a
web database system, so the communication is &TT; protocol.

Nonfunctional Requirements

Performance Requirements:

7|Page
SOFTWARE REQUIREMENT SPECIFICATION

If user searches for a flight leaving from a particular place to another place, the application should not take much
time to return with results, considering it should be able to display 10 results at a time , when the customer looks
up for any particular data. Since the ARS websites have much traffic, the user should also be able to login to our
system using high speed internet. Most of the requests sent to the application should be answered in less than 5
seconds or more less than that.

Safety Requirements:

Users shall be required to login to the ARS for their own reservation information and modification with email
address and password. The system only allows authorized members who are on the list of
authorized managers to do administrators task.
Security Requirements:
Users is required to login to ARS only for their own reservation information and modification with email
address and password. The system allow only customers to view only their own previously placed
orders, not orders placed by other customers.

Software Quality Attributes:

1. Availability:
The ARS shall be available to users between 5am and midnight local time. And it is available to
administrators all the time.

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

3. Consistency:
The ticket availability in ARS shall be updated only when transaction is finalized to ensure that
the most updated information is delivery to any customers. When administrator is updating the
information, the consistency should also hold among user point of view.

4. Scalability:
Whenever some resources are added within the existing system it helps system to
increasing the quality.

REFERENCES:

https://www.academia.edu/17657886/SOFTWARE_Engineering_LAB_CS041
1.
8|Page
SOFTWARE REQUIREMENT SPECIFICATION

https://www.academia.edu/29638633/SE_PROJECT_Finalize

9|Page