Software Requirements

Specification
for

<Airline>

Version 1.0 approved

Prepared by <Hasaan Wahid>

<Comsats University Sahiwal>

<24-5-21>

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary...................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List...........................................................................................6
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose
The purpose of this document is to build an online system to manage flights and
passengers to ease the flight management.

1.2 Document Conventions

This document uses the following conventions.

DB Database

DDB Distributed Database

ER Entity Relationship

1.3 Intended Audience and Reading Suggestions

This project is a prototype for the flight management system and it is restricted within the
college premises. This has been implemented under the guidance of college professors.
This project is useful for the flight management team and as well as to the passengers.

1.4 Product Scope

The purpose of the online flight management system is to ease flight management and to
create a convenient and easy-to-use application for passengers, trying to buy airline
tickets. The system is based on a relational database with its flight management and
reservation functions. We will have a database server supporting hundreds of major cities
around the world as well as thousands of flights by various airline companies. Above all,
we hope to provide a comfortable user experience along with the best pricing available.

1.5 References

 Fundamentals of database systems by ramez elmarsi and shamkant

b.navathe
Software Requirements Specification for <Project> Page 2

2. Overall Description

2.1 Product Perspective

 Flight details:
It includes the originating flight terminal and destination terminal, along with
the stops in between, the number of seats booked/available seats between
two destinations etc.
 Customer description:
It includes customer code, name, address and phone number. This
information may be used for keeping the records of the customer for any
emergency or for any other kind of information.
 Reservation description:
It includes customer details, code number, flight number, date of booking, date
of travel

2.2 User Classes and Characteristics

Users of the system should be able to retrieve flight information between two given cities
with the given date/time of travel from the database. A route from city A to city B is a
sequence of connecting flights from A to B such that: a) there are at most two connecting
stops, excluding the starting city and destination city of the trip, b) the connecting time is
between one to two hours. The system will support two types of user privileges, Customer,
and Employee. Customers will have access to customer functions, and the employees will
have access to both customer and flight management functions. The customer should be
able to do the following functions:
 Make a new reservation
• One-way
• Round-Trip
• Multi-city
• Flexible Date/time
• Confirmation
 Cancel an existing reservation
 View his itinerary
The Employee should have following management functionalities:
 CUSTOMER FUNCTIONS.
• Get all customers who have seats reserved on a given flight.
• Get all flights for a given airport.
• View flight schedule.
• Get all flights whose arrival and departure times are on time/delayed.
• Calculate total sales for a given flight.
Software Requirements Specification for <Project> Page 3

 ADMINISTRATIVE
• Add/Delete a flight
• Add a new airport
• Update fare for flights.
• Add a new flight leg instance.
• Update departure/arrival times for flight leg instances.
Each flight has a limited number of available seats. There are a number of flights which
depart from or arrive at different cities on different dates and time.

2.3 Operating Environment

Operating environment for the airline management system is as listed below.  <<Include
the details as per your application >>
 distributed database
 client/server system
 Operating system: Windows.
 database: sql+ database
 platform: vb.net/Java/PHP 

2.4 Design and Implementation Constraints

1. The global schema, fragmentation schema, and allocation schema.

2. SQL commands for above queries/applications
3. How the response for application 1 and 2 will be generated. Assuming these
are global queries. Explain how various fragments will be combined to do so.
4. Implement the database at least using a centralized database management
system

2.5 Assumptions and Dependencies

Let us assume that this is a distributed airline management system and it is used in the following
application:

A request for booking/cancellation of a flight from any source to any destination, giving connected
flights in case no direct flight between the specified Source-Destination pair exist.
Calculation of high fliers (most frequent fliers) and calculating appropriate reward points for these
fliers.
Assuming both the transactions are single transactions, we have designed a distributed database that
is geographically dispersed at four cities Delhi, Mumbai, Chennai, and Kolkatta as shown in fig.
below
Software Requirements Specification for <Project> Page 4

3. External Interface Requirements

3.1 User Interfaces

 Front-end software: Vb.net version

 Back-end software: SQL+

3.2 Hardware Interfaces

 Windows.
 A browser which supports CGI, HTML & Javascript.

3.3 Software Interfaces

Following are the software used for the flight management online application
Software used Description

Operating system We have chosen Windows operating system for its best support and user-friendliness.

Database To save the flight records, passengers records we have chosen SQL+ database.

VB.Net To implement the project we have chosen Vb.Net language for its more interactive support.

3.4 Communications Interfaces

This project supports all types of web browsers. We are using simple electronic forms for
the reservation forms, ticket booking etc.

4. Other Nonfunctional Requirements

4.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them
here and explain their rationale, to help the developers understand the intent and make suitable
design choices. Specify the timing relationships for real time systems. Make such requirements
as specific as possible. You may need to state performance requirements for individual functional
requirements or features.>
Software Requirements Specification for <Project> Page 5

4.2 Safety Requirements

If there is extensive damage to a wide portion of the database due to catastrophic failure,
such as a disk crash, the recovery method restores a past copy of the database that was
backed up to archival storage (typically tape) and reconstructs a more current state by
reapplying or redoing the operations of committed transactions from the backed up log, up
to the time of failure.

4.3 Security Requirements

Security systems need database storage just like many other applications. However, the
special requirements of the security market mean that vendors must choose their
database partner carefully.

4.4 Software Quality Attributes

 AVAILABILITY: The flight should be available on the specified date and

specified time as many customers are doing advance reservations.
 CORRECTNESS: The flight should reach start from correct start terminal and
should reach the correct destination.
 MAINTAINABILITY: The administrators and flight in chargers should maintain
correct schedules of flights.
 USABILITY: The flight schedules should satisfy a maximum number of
customers needs.