Software Requirements

Specification
for

<AIRLINE RESERVATION
SYSTEM>
Version 1.0 approved

Prepared by:

Arslan Azhar(026),

Umair Raza(044),

A R Arslan(061),

M Usman(112)

<05-10-2016>

<ARSL PRODUCTION>

Copyright1999byKarlE.Wiegers.Permissionisgrantedtouse,modify,anddistributethisdocument.

SoftwareRequirementsSpecificationfor<Project>

Pageii

TableofContents
TableofContents...........................................................................................................................ii
RevisionHistory.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5

Purpose...........................................................................................................................................1
DocumentConventions..................................................................................................................1
IntendedAudienceandReadingSuggestions.................................................................................1
ProductScope.................................................................................................................................1
References......................................................................................................................................1

2.1
2.2
2.3
2.4
2.5
2.6
2.7

ProductPerspective........................................................................................................................2
ProductFunctions...........................................................................................................................2
UserClassesandCharacteristics....................................................................................................2
OperatingEnvironment..................................................................................................................2
DesignandImplementationConstraints.........................................................................................2
UserDocumentation.......................................................................................................................2
AssumptionsandDependencies.....................................................................................................3

3.1
3.2
3.3
3.4

UserInterfaces................................................................................................................................3
HardwareInterfaces........................................................................................................................3
SoftwareInterfaces.........................................................................................................................3
CommunicationsInterfaces............................................................................................................3

2. OverallDescription..................................................................................................................2

3. ExternalInterfaceRequirements...........................................................................................3

4. SystemFeatures.......................................................................................................................4
4.1 SystemFeature1............................................................................................................................4

5. OtherNonfunctionalRequirements.......................................................................................4
5.1
5.2
5.3
5.4

PerformanceRequirements.............................................................................................................4
SafetyRequirements.......................................................................................................................5
SecurityRequirements....................................................................................................................5
SoftwareQualityAttributes............................................................................................................5

6. OtherRequirements................................................................................................................5
AppendixA:Glossary....................................................................................................................5
AppendixB:AnalysisModels.......................................................................................................5
AppendixC:ToBeDeterminedList............................................................................................6

RevisionHistory
Name

Date

ReasonForChanges

Version

SoftwareRequirementsSpecificationfor<Project>

1.

Introduction

1.1

Purpose:

Page1

The main purpose of this vision document is to list the requirements of the Airline Reservation
System project. This document also helps us to collect and analyze the ideas gathered for the
project. This vision document will be subject to change, if more requirements are added to the
project. This document is mainly prepared to set stage for the design phase of the project. The
document being prepared is the first version of vision document for the Airline Reservation
System project. C#.NET is a new technology which is being used a lot in the IT field. My interest
to learn this new technology has prompted me to take up this project.

1.2

DocumentConventions:

All system development activities should follow the final version of this document. Any
discrepancy that found during in later phases should be modified subject to SRS. However, this
document may be subject to change dependent on the decision of the group members.

1.3

IntendedAudienceandReadingSuggestions:
Reading sequence
Introduction
Overall description
External interference Requirement
System Features
Other Non Functional Requirements

1.4

Other Requirements

ProductScope:

The name of the software is AIRLINE RESERVATION SYSTEM.This software provides

options for viewing different flights available with different Timmings 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 the details of cost of the ticket and it does not allow the
customers to modify a particular part of his reservation and he can modify all his details.

1.5

References:

Some of the references used for preparing the vision document include:
1. http://inkboard.sourceforge.net/docs/VisionDocument.pdf
2. www.orbitz.com

SoftwareRequirementsSpecificationfor<Project>

Page2

3. IEEE document for Software Requirements Specifications

4. E-Draw software is used to generate the use case diagrams
5. Wikipedia
6. MSE Portfolio presentation I lecture by Dr. Deloach, on the CIS website would set the stage
for the applications I would be developing in the future.

2.

OverallDescription

2.1

ProductPerspective:

The Airline Reservation System project uses the Net FrameWork and is completely
independent. The project itself is a bigger product and does not need to be introduced into a
larger system. The application would be running on a Windows 7 ultimate Operating system.

2.2

ProductFunctions:

The major functions include

Providing flight details
Flight bookings for a particular destination, date and time and also providing with a pin
code.
Allowing the customer to modify or cancel his reservation provided the correct pin code is
given.
Displaying a report of the number of people flying in a particular flights.

2.3

UserClassesandCharacteristics:

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 prior training to use the
application. However, instructions for making flight and motel reservations would be provided to
them on the airline website. The administrators would however need to be trained in order to use
the application. They may wish to update/add/delete any information in online reservation
database . They may need to create and manage temporary views of fetched records from the
databases of airlines.

2.4

OperatingEnvironment:

Airline Reservation System should be accessed using any popular versions of the

following Web browsers: Microsoft Internet Explorer, Mozilla Firefox, and Google Chrome.

SoftwareRequirementsSpecificationfor<Project>

2.5

Page3

DesignandImplementationConstraints:

The system database design will be based ER modeling which will in turn transfer to
database schema formulated using SQL DDL statements.
All HTML code should conform to the HTML 4.0 standard.

2.6

UserDocumentation:

Final release will be accompanied with a user guide to inform new users how to use
Airline Reservation System.
The system will be designed as user friendly as possible.

2.7

AssumptionsandDependencies:

Users of Airline Reservation System are assumed to have a computer with internet
access.
Credit and debit card authorization services are assumed to be available.
Airline Reservation System has collaboration with every airlines databases thus it
must be able to communicate with these systems. Also it has to obey airlines
business rules.
Only domestic flights are supported.

3.

ExternalInterfaceRequirements

3.1

UserInterfaces:

There are two types of users for the Airline Reservation System project. One 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 E-mail
Id field, push down buttons like the Login button etc. The administrator of the website would also
have a similar Graphical User Interface. After an administrator logs onto the system, the home
page for the administrator would be as follow.

3.2

HardwareInterfaces:

No hardware interface specified for Airline Reservation System.

SoftwareRequirementsSpecificationfor<Project>

3.3

Page4

SoftwareInterfaces:

The application should run on a Windows 7 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. All the coding will be done in C.

3.4

CommunicationsInterfaces

4.

Airline reservation System should send an e-mail 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
HTTP protocol.

SystemFeatures:

The search feature allows the user to search for an airline flight on a variety of dimensions.

4.1

SystemFeature1

4.1.1

DescriptionandPriority:

This Feature allows users to book a reservation for a trip.

User will be able to specify the Flight Class which will be with respect to the flight
chosen. [Priority = Low]

The user will be able to choose from a listing of available seats. [Priority = Low]

The system shall accept reservations for 1 person per flight and seat number.
[Priority = High]

The user must complete all the necessary steps to book the flight for the seat
reservation to be guaranteed. [Priority = High]

The user must specify a valid e-mail address when booking a flight. [Priority =
High]

Users may only book flights within the United States. [Priority = High]

All times displayed are expressed in local time, specific to the location. [Priority =
High]

The user will only be able to book flight within one year of the present date. (Cutoff
time may be applied) [Priority = High]

SoftwareRequirementsSpecificationfor<Project>

4.1.2

Page5

After booking, the user may cancel/modify their flight. [Priority = Low]

Stimulus/ResponseSequences:
Reservation Use case
Use Case ID: 1
Use Case Name: Place reservation
Created By: Arsl
Last Updated By: Arsl
Date Created: 06/08/2016
Date Last Updated: 05/10/2016
Actors: Customer
Description: A customer accesses the AFIRS from the Internet, optionally search for
specific ticket/flight information of interest, selects ticket(s), and places reservation.
Preconditions: None
Post conditions: 1. Database of available tickets is updated to reflect items in this order.
2. Remaining tickets number is updated.
Normal Flow: 1.0 Order a Single Ticket
1. Customer uses the web interface to enter a certain query to view flight information for a
specified interest.
2. System displays available flight information satisfied the query.
3. Customer selects one or more items from page. Customer can also click on a particular
ticket to see the detailed information.
4. System displays reservation with detailed price information including all taxes.
5. Customer confirms reservation or requests to modify reservation (back to step 3).
6. Customer specifies payment method. 7. Customer indicates that reservation is
complete. 8. System confirms acceptance of the order.
9. System sends Customer an e-mail confirming order details, price, and additional links to
access the ticket details or for potential modification.
10. System stores order in database, and updates available ticket information.

SoftwareRequirementsSpecificationfor<Project>

4.1.3

Page6

FunctionalRequirements:

The functional requirements of the Airline Reservation System are divided among the
customer and the administrator of the application. These functional requirements,
4.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,
motels, 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.

4.1.4

4.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
informationuirements can be explained 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.1.5

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

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

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

SoftwareRequirementsSpecificationfor<Project>

Page7

Output:
The application verifies the authenticity of the username and password and then displays
information related to various flights to the customer.
4.1.8

4.6 Use Case name: Book Motel

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 customers destination.
4.1.9

4.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 ticket reservation.
Output: The application verifies the authenticity of the username and password of the customer
and then displays information of various touring packages available at customers choice of place.
The administrator activities use cases will be described here:
4.1.10 4.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.
4.1.11 4.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.
4.1.12 4.10 Use Case name: Add/Delete or Modify flight 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.

SoftwareRequirementsSpecificationfor<Project>

Page8

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.

4.1.13 4.11 Use Case name: Cancellation 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 e-mail to the customer.
4.1.14 4.12 Use Case name: E-mail confirmations
Description: This use case describes the scenario where the administrator sends e-mail
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 e-mail confirmations to the customer. These e-mail confirmations may be
sent in cases where the customer has cancelled a reservation or changed the personal
information available on the website
4.1.15 4.13 Use Case name: Modifying details of webpage
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 browse through the website and
change the details of any webpage in the Airline Reservation system application.
4.1.16 4.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. He can even update the price per room of each motel. To make it easier, the
administrator might assign a unique id for each hotel.
4.1.17 4.15 Use Case name: Add/Delete or Modify package information

SoftwareRequirementsSpecificationfor<Project>

Page9

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

5.

OtherNonfunctionalRequirements

5.1

PerformanceRequirements:

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.

5.2

SafetyRequirements:

Nosafetyrequirementshavebeenidentified.

5.3

SecurityRequirements:

Users shall be required to log in to the Airline Reservation System for their own reservation
information and modification with e-mail 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.

5.4

SoftwareQualityAttributes:

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

SoftwareRequirementsSpecificationfor<Project>

Page10

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.
Consistancy: 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.
Reliability:
The system will have redundant hardware.In the event of a website
outage,support personnel will respond within 30 minutes.In the event of a less
severe problem support personnel will respond within 3 hours.
Maintainability:
This product shall be maintained by an administrator in case of
any detect.In addition any update or change that is made will be changed on
server side computers without any patches required by the customer.

6.

OtherRequirements:

A List of Airline including:

o Pakistan International Airline
o PIA
o Location City State zip code (If possible) Time zone
The information about several Flights, more specifically:
o Flight id
o Flight number
o Departure/Arrival Date/Time
o Departure/Destination Airport
o Seats
o Total / Vacant
o Seat Number
o First Seats
o Coach Seats

AppendixA:Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>

AppendixB:AnalysisModels
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>

AppendixC:ToBeDeterminedList
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>