Airlines Reservation System

The assignment content outlines the non-functional requirements, inverse requirements, design constraints, logical database requirements, and other requirements for an Airlines Reservation System. The system should utilize low memory, run efficiently, have a high uptime (99.9%), and load within 5 seconds. It should also ensure user data security, maintainability, portability, and availability. Inverse requirements include avoiding technical terminologies, limiting user IDs to ten digits, and requiring email addresses. Design constraints are limited to using UML diagrams only. Logical database requirements involve storing user information and flight details separately.

<Airline Reservation System>
Software Requirements Specification
<Version 1.0>
<Date>
<Your Name/Team Name>
Prepared for
Marymount University, School of Business
IT210, Software Engineering

< Airline Reservation System >
Revision History
Date Description Author Comments
<date> <Version 1> <Your Name> <First Revision>
Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature Printed Name Title Date
<Your Name>
SRSTemplate.doc Page 2

< Airline Reservation System >
Table of Contents
REVISION HISTORY II
DOCUMENT APPROVAL II
1. INTRODUCTION 1
1.1 PURPOSE 1
1.2 SCOPE 1
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS 1
1.4 REFERENCES 2
1.5 OVERVIEW 2
2. GENERAL DESCRIPTION 2
2.1 PRODUCT PERSPECTIVE 2
2.2 PRODUCT FUNCTIONS 3
2.3 USER CHARACTERISTICS 3
2.4 GENERAL CONSTRAINTS 3
2.5 ASSUMPTIONS AND DEPENDENCIES 4
Following are the application based on the distributed airline database system: 4
3. SPECIFIC REQUIREMENTS 5
3.1 EXTERNAL INTERFACE REQUIREMENTS 5
3.1.1 User Interfaces 5
3.1.2 Hardware Interfaces 5
3.1.3 Software Interfaces 5
3.1.4 Communications Interfaces 5
3.2 FUNCTIONAL REQUIREMENTS 5
3.3 USE CASES 7
3.3.1 Use Case #1 8
3.3.2 Use Case #2 8
3.3.2 Use Case #3 8
3.3.2 Use Case #4 9
3.3.2 Use Case #5 10
3.4 CLASSES / OBJECTS 10
3.4.1 <Class / Object #1> 10
3.4.2 <Class / Object #2> 10
3.5 NON-FUNCTIONAL REQUIREMENTS 10
3.5.1 Performance 11
3.5.2 Reliability 11
3.5.3 Availability 11
3.5.4 Security 11
3.5.5 Maintainability 11
3.5.6 Portability 11
3.6 INVERSE REQUIREMENTS 11
3.7 DESIGN CONSTRAINTS 11
3.8 LOGICAL DATABASE REQUIREMENTS 11
3.9 OTHER REQUIREMENTS 11
4. ANALYSIS MODELS 11
4.1 SEQUENCE DIAGRAMS 11
SRSTemplate.doc Page 3

< Airline Reservation System >
4.3 DATA FLOW DIAGRAMS (DFD) 11
4.2 STATE-TRANSITION DIAGRAMS (STD) 11
5. CHANGE MANAGEMENT PROCESS 11
A. APPENDICES 12
A.1 APPENDIX 1 12
A.2 APPENDIX 2 12
SRSTemplate.doc Page 4

< Airline Reservation System >
1. Introduction
The current paper is a software requirement specification for an airline reservation system. The
understanding of airline reservation is likely to help in further development and assessment. The
various sections within this paper discuss the various aspects of the software requirements such
as the scope, use case, data flow diagram, functional and non-functional requirements.
1.1 Purpose
The purpose of the paper is to describe the software requirement specification report which is
used for the airline reservation. The development of airliner reservation will be based on the
requirements mentioned in this document. The reservation system will help the users in booking
online ticket from anywhere. The reason behind the development of this system is that the airline
is unable to cater to increasing demand at the airport. It is expected that the online system will
help in reducing the rush on the airport and thus eventually will reduce the cost that is incurred.
1.2 Scope
The scope of the online system is to develop the easy to use and convenient online system which
helps to easily buy the airline tickets. The system is mainly based on the relational database with
the reservation functions and flight management (Abdullah et al., 2016). The database supports
many cities across the world and various numbers of flights through using the airline companies.
The systems aim to provide the best user service with the best price which is available in the
industry.
1.3 Definitions, Acronyms, and Abbreviations
Following are the acronyms and abbreviations:
SRSTemplate.doc Page 5

< Airline Reservation System >
● DB: Database
● ER: Entity relationship
● DDB: Distributed database
1.4 References
For the reference, two sources have been chosen. The first is a book by Shamkant B. Navathe
and Elmarsi named Fundamentals of Database Systems, Fifth Edition. The second is an online
resource named krazytech.com.
1.5 Overview
It is the project of the college level students which is used to implement the guidelines of college
professors. The project can be used by professionals who are willing to develop an online
reservation system based on the requirements given in the software requirement system. The user
of the current requirement system can update areas as per their individual requirements. There is
myriad possibility to develop the current system.
2. General Description
2.1 Product Perspective
Following is the information which is stored in the distributed airline database system:
● Flight details
It includes the details of flights such as destination terminal, flight terminal of the
destination with the information of the number of stops between the arrival and
destination of the flight, number of reserved and unreserved seats (Jasuja et al., 2016).
● Consumer description
It includes the information of customers such as customer code, phone number, address,
SRSTemplate.doc Page 6

< Airline Reservation System >
and name. The information can be used to inform the customer regarding the flight delay
or any other purpose.
● Reservation description
It includes the details of reservation such as flight number, date of traveling, date of
booking and customer code number.
2.2 Product Functions
The system can be used to retrieve the information of flight among the two counties/cities with
the date and time of the traveling from the database. The function can be used by the customers
and employee. The employee can access both the flight management function as well as the
customer function, but the customer can access the customer function only.
● Customer function
The customer can use for the various types of reservations such as round trip, one way,
flexible day time, multi-city, confirmation, and round trip.
● Employee function
It includes the access of customer function and administrative function. The
administrative function includes add/ delete flight, add/delete new airport and others.
2.3 User Characteristics
The basic knowledge of handling the system is required.
2.4 General Constraints
There are three constraints, namely, document software, document template, and projects.
SRSTemplate.doc Page 7

< Airline Reservation System >
2.5 Assumptions and Dependencies
Following are the application based on the distributed airline database system:
● It can be used for the cancellation and booking of flight if there is no direct flight
between the two specific destinations (Barth et al., 2013).
● The high fliers can be calculated, and the appropriate reward points can be calculated for
the fliers.
SRSTemplate.doc Page 8

< Airline Reservation System >
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
The menu structure and screen format should be used in such a way that enables to provide easy
to use for the users. The product should be inter-active and user friendly. There are various
functions which are provided by the system such as error message display that should be adapt
itself to the various users of the system.
3.1.2 Hardware Interfaces
There is no hardware interface required. The system can successfully run on hardware with basic
system capability running windows and other operating system successfully. It is basically a
web-based program and therefore can run successfully on devices that can run web browsers.
3.1.3 Software Interfaces
Visual basic is used to develop the resultant system.
3.1.4 Communications Interfaces
The local area network is used for communication between the different client systems.
3.2 Functional Requirements
● User accounts
The user is a passenger who has three choices according to the reservation system. The
user will firstly register or login as the guest in order to check the availability of seat for
the particular airways on the specific date. The user id and password will be received
after completing the registration form of the reservation system (O'sullivan et al., 2016).
The existing user already has the user id and password whereas the new user needs to
register them in order to check the availability for the particular period of time.
SRSTemplate.doc Page 9

< Airline Reservation System >
● Registration and creation of user profile
After receiving the registration id and password then the user can login into the system in
order to buy the ticket after checking the availability of ticket within the particular period
of time.
● Checking availability
The details can be filled by the user in order to determine the availability of the particular
ticket. The details include entering of two cities which include the city from which the
origin city and destination city.
● Making reservation
After checking the availability, the reservation can be made by the user by selecting the
origin and destination city (Wiegers et al., 2013). The user can check if there is a direct
flight to indirect flight in order to make a reservation on the basis of checking the
availability of seats on the particular flight.
● Confirm ticket
After checking the availability of seats and the suitability of the user then the ticket can
be confirmed by the user within the particular period of time. The seats should be booked
immediately as there is a specific time of booking the ticket.
● Reschedule ticket
If the ticket is booked for the wrong day and the user is not available to take the flight on
that particular day, then the flight can be rescheduled by checking the flights on other
days. The rescheduling of flight can be done within the specific period of time as after the
expiry of those days there is no option to reschedule the ticket.
● Cancellation
SRSTemplate.doc Page 10

< Airline Reservation System >
The cancellation can also be made if the user is not available or the plan of the user has
been canceled. Then, in this case, the user can cancel the ticket, but the cancellation
option is also available for some days. In the case of cancellation the total amount is not
refunded by the airways then some proportion of amount is refunded to the user within
the specific period of time.
● Update profile
The user can update their profile for example change in address, phone number, and
others. It can only be updated by the user through login into their account in order to
update the existing profile.
● View ticket status
The status of a ticket can be viewed by the user through login into the system through
their specific user id and password. The confirmation number is asked by the system after
logging which enables to access the DB-reservation and the information can be retrieved
by the user in their convenient format (Blessing et al., 2017).
● Query flight details
The details of the particular flight can be accessed by the user which helps to resolve the
specific issue regarding the arrival, departure and other information within the specific
period of time through login into the system with the respective user id and password.
● Telephone access
The system can be access through touch mobile phone which provides the facility of
checking the fight details to the user.
3.3 Use Cases
The section below shows the different use cases developed for the current reservation system.
SRSTemplate.doc Page 11

< Airline Reservation System >
3.3.1 Use Case #1
The use case above shows the diagram connecting the user and the agent with the aspects like
login, flight search, flight booking, adjusting, cancelling, and confirmation. The use case above
indicates the various activities that will be performed by the online users. The agent on the other
hand will be able to conduct the booking adjustments as per the requirements of the flight.
3.3.2 Use Case #2
The use case diagram above shows the customer engaging in flight search, purchasing ticket,
SRSTemplate.doc Page 12

< Airline Reservation System >
cancelling reservation and making reservation. These aspects are interlinked as visible above.
3.3.2 Use Case #3
The use case diagram above shows the three actors, namely, passengers, admin and the bank.
This use case shows the transactional aspect of ticket booking.
3.3.2 Use Case #4
The use case shown below shows the two actors, namely customer and the payment processor.
The customer is being shown engaging in activities like reservation of ticket, searching the
flights, viewing the status of the flights, cancelling the reservation or rescheduling the flight. In
this use case, payment processor is shown that engages in validation of the credit card.
SRSTemplate.doc Page 13

< Airline Reservation System >
SRSTemplate.doc Page 14

< Airline Reservation System >
3.3.2 Use Case #5
The use case diagram above shows two actors, namely, traveller or the customer and the agent.
There are multitudes of activities that have been show in this diagram. The
3.4 Classes / Objects
The classes/objects diagram is shown in the diagram below:
SRSTemplate.doc Page 15

< Airline Reservation System >
3.4.1 Attributes
The various attributes in the current diagram are flight details, store, and database.
3.4.2 Functions
The fuctions include addition and update of the required data.
3.5 Non-Functional Requirements
Non-functional requirements may exist for the following attributes. Often these requirements
must be achieved at a system-wide level rather than at a unit level. State the requirements in
the following sections in measurable terms (e.g., 95% of transaction shall be processed in less
than a second, system downtime may not exceed 1 minute per day, > 30 day MTBF value, etc).
3.5.1 Performance
It is expected that the system should use as low memory as possible. The processor should be
SRSTemplate.doc Page 16

< Airline Reservation System >
utilized by the system very efficiently. The users should be able to finish their job on the system
within minimum time possible. The system should run with 99.9% uptime and should take less
than 5s to load.
3.5.2 Reliability
The system should deliver what is requested by the user over certain period of time. The
reliability of the system should be such that it repeats the same ability every time user visits the
system for operation.
3.5.3 Availability
The system should always be available for the access to the user and it should deliver what it is
meant to deliver as per the user request. If the system fails to bring in what is requested by the
user, then it will be denoted as bad on the availability and further improvements will be required.
3.5.4 Security
The system should secure all the information entered by the user and it should not share the
information to other party without any intentional go ahead. The system should protect itself
from any kind of external threat such as hacking, intrusions, etc.
3.5.5 Maintainability
When the system will be under use, it is likely that the changes will occur and, therefore, it is
expected that the system will allow such changes as and when required. It is necessary to ensure
that the system can be updated periodically.
3.5.6 Portability
The system should be easy to transfer from one machine to another as changes in hardware are
considered as prerequisite to constantly developing environment. If the system fails to be
portable then it will be of no use once certain OS or hardware gets useless with time.
3.6 Inverse Requirements
Inverse Requirements are referred to as the things that should not be done by the system.
These are the constraints on the allowable behavior. The inverse requirements for the current
system are that the system should not contain heavy technical terminologies that are not
understandable by the users, the user id should be of ten digits, and email is must.
3.7 Design Constraints
The design of the system will be done using the UML diagrams only.
3.8 Logical Database Requirements
There are two types of databases that were under consideration. One database is concerned
with the storage of user information and another data base is concerned with the flight
information. The data base containing user information stores data such as user name, country,
passwords, and others. The flight database contains information such as arrival or departure
time, flight number, and others.
SRSTemplate.doc Page 17

< Airline Reservation System >
3.9 Other Requirements
The test plan for the system will be done at the end of the system and no intermediary test will
be conducted.
4. Analysis Models
4.1 Sequence Diagrams
Appendix 2.1 shows the sequence diagram developed for the system. The sequence diagram
developed here contains aspects such as user, flight details, store, and database. The sequence
diagram effectively helps in modeling the object interaction within the system.
4.3 Data Flow Diagrams (DFD)
The data flow diagram is shown in the Appendix 1.1, 1.2, and 1.3. The Appendix 1.1 contains
DFD at Level 0, the Appendix 1.2 contains the DFD at level 1, and the Appendix 1.3 contains
DFD at level 3. The Appendix 1.4 contains the context DFD.
4.2 State-Transition Diagrams (STD)
It showcases the single object. This shows the impact of external factors overtime. It identifies
the overall software system behavior. Appendix 2.3 shows he STD.
5. Change Management Process
The change management process requires the initiation of change request from the system
administrator. The change request will be assessed and verified by the upper management and
then proper approval will be given to make the changes.
A. Appendices
A.1 Appendix 1
Appendix 1.1
SRSTemplate.doc Page 18

< Airline Reservation System >
The figure above shows the level 0 DFD of Airlines Reservation System. It
contains a process that represents the system to model. It also shows the
participants who will interact with the Airlines Reservation System. Users are the
only entity here who will book a ticket via online airlines reservation system.
Appendix 1.2
SRSTemplate.doc Page 19

< Airline Reservation System >
The airlines reservation system breaks into two parts. In one part, user is able to
book flight ticket. The first role in this module is that user search for a particular
flight and then book tickets in those flights. In the second module user is able to
cancel the tickets that he had already booked.
Appendix 1.3
SRSTemplate.doc Page 20

< Airline Reservation System >
In this there is another module added of payment which is being followed by the
user after he selects the ticket to confirm it.
Appendix 1.4: Context DFD
A.2 Appendix 2
● Sequence Diagram
● State Chart Diagram
● Deployment Diagram
SRSTemplate.doc Page 21

< Airline Reservation System >
● Component Diagram
● Collaboration Diagram
● Activity Diagram
Appendix 2.1: Sequence Diagram is shown below
First, the sequence starts when the user search for a flight, then the system displays
the ticket information of all the flight. After the user book a ticket, user ticket
information is added in the database. If a user wants to modify the details of ticket
then he can also do so as well. If user wants to cancel the ticket the data, it will be
deleted from the database.
SRSTemplate.doc Page 22

< Airline Reservation System >
Appendix 2.2: State Chart Diagram
SRSTemplate.doc Page 23

< Airline Reservation System >
SRSTemplate.doc Page 24

< Airline Reservation System >
State chart diagram shows the states of the user when he books a ticket. First user
have to login to the system, then system checks for the valid credentials, then user
search the flight and book a seat, then system check for the availability of the seat,
then user make payment for that and then he got confirm ticket.
Appenddix 2.3: Deployment Diagram
This above simple diagram displays the layout of airlines reservation system. Users
will directly interact with the application hardware.
Appendix 2.4: Component Diagram
SRSTemplate.doc Page 25

< Airline Reservation System >
The details of the features of the system that the user will come across are the
reserve a ticket; check the status of flight and its details.
Appendix 2.5: Collaboration Diagram
User can only have one identification, and one identification have only one user
SRSTemplate.doc Page 26

< Airline Reservation System >
one identification can have any number of booking. Flight details are stored in the
Database and, the Database can have many flight details and user identification.
Appendix 2.6: Activity Diagram
SRSTemplate.doc Page 27