SOFTWARE REQUIERMENT SYSTEM OF

AIRLINE RESERVATION SYSTEM

INTRODUCTION:

The Airline Reservation System is a benefit for the passengers

to book flights using online system. By using this system, passengers
can book their seats online.
The Reservation of Airlines will be upgraded to online by using
this software Passengers who want to travel by air, they have to face
difficulty to buy tickets and reserve their seats. We should introduce a
system by using which passenger can reserve their seats online.

USERS OF THIS SRS:

This SRS can be used by the:
1. Development Team: The development team writes all the
information regarding the project in the SRS and this document will
be use by the development team later.
2. Maintenance Team: This document will be used by the
maintenance team later on if there will be any issue in the system.
3. Technical Writers: This document will also help technical
writers to write the technical aspects of this system.
This document will also help the clients if they have any issue
regarding the use of this system.

PURPOSE:
 Allow passengers to reserve their seats through online system.
 Public can also check the availability of any Airline system.
SCOPE:
The product can be used to perform the following tasks:
 The software which we are going to develop can be used to
check the availability of the flight tickets and for specified flight,
destination of date of travel.
 If the tickets are available for passenger according to their
needs and specifications, then this software will provide the
facility to book the ticket.
 If the passenger wants to cancel the ticket after he has booked
it, this software allows hit to cancel the ticket.
 The passengers and the Airline office, both will connect
together through internet and if the internet connection losses,
they will be unable to connect together.

ABBREVIATIONS:
 ARS: Airline Reservation System
 GUI: Graphical User Interface
 SRS: Software Requirements Specifications
 SQL: Structured Query Language
 ATM: Automated Teller Machine

User/Admin: The person who uses the system and control and
manage all the operations of the system.
End-User: The person who uses system to get services.
Accounts: To use the system for the first time, user have to
register himself called Account.
OVERVIEW:
The Airline Reservation System is an upgradation of traditional
system. The website will helps the customers to find any flight
towards their destination and the different packages available with the
reservations. SRS contains analysis of the requirement to help easy
diagram.
 The overall description provides interface requirements for the
Airline Reservation System, product perspective, hardware interface
software interfaces, communication interface memory constraints,
products user characteristics and other constraints.
 The upcoming pages tells the characteristics of typical users
accessing the system along with legal and functional constraints
enforced on the system.

REFERENCES:
 https://www.youtube.com/channel/UCKvjEXuc-tomU0sW_iBZ3fw

 IEEE SRS Template

 https://www.agoda.com/?site_id=1829995&tag=b2d62ab4-3d7a-9476-75b3-
c98386c162fd&device=c&network=g&adid=369056108842&rand=10872871215179733
556&expid=&adpos=&gclid=CjwKCAjwvtX0BRAFEiwAGWJyZLFJRjhbLx_8Eh_mra7Q_MFn
7-5NT_UIFCblspDFPqDTY550yzDMGRoCSIIQAvD_BwE&checkin=2020-04-
23&checkout=2020-04-24&adults=1&childs=0&rooms=1&los=1
 https://www.orbitz.com/

PRODUCT PERSPECTIVE:
1) Hardware Perspective:
The database connectivity requires a hardware configuration with a
fast database system which has a very high speed hard disk
permitting complete data redundancy and backup system. So that the
system provide fast data transfer rate and the system will be reliable.
2) Software Interface: We will use two type of software in our
system. One for the front end and the other for the backend.
i) MS Access 2019: This is a powerful database management
system by Microsoft Organization. We will use this software to design
and manage the backend database of the system.
ii) Microsoft Visual Basics 6.0 is used to design the front end of
the system

Operations:
The end-user will be allowed to perform end user operations
like checking the flight schedule, checking the availability, reserving
and cancelling the flight tickets.

PRODUCT FUNCTIONS:
The users of this system will have three types, front-desk,
passengers and the administration of this system.
END-USER FUNCTIONS:
I. Has access to Homepage.
II. Create account and login
III. Book Flights
IV. View details of the flight like flight timing, seat availability, flight
route, flight number.
V. Book Motels and Packages
VI. Contact the Company
VII. Cancel the ticket
USER/Admin FUNCTIONS:
I. Login / Logout
II. Add / Delete / Modify Customer Information
III. Add / Delete / Modify Flight Information
IV. Add / Delete / Modify Motel Information
V. Cancellation of Reservations
VI. E-mail confirmations

USER CHARACTERISTICS:
There will be three types of users in our system:
a) Administrators
b) Reception Staff
c) Passengers
The end user of this software need not have specific knowledge
as to what is the internal operation of the system. This software is
made by keeping mind the comfort level of the user. This system is
completely user friendly. The customers do not need to have any
prior training to use the application. The administrators will have to
train their staff to use this software.
The product do not expect the user to possess any technical
background. The user with least knowledge of computer can use this
software.

GENERAL CONSTRAINTS:
 When the Admin modify the records on database, application
should be show the updated information on webpage, without
much delay.
 The database for the project is designed to be of moderate size.
 The webpage is designed to run on JavaScript supported
browsers. The Airline Reservation system will be designed in
 such a way that, it can be run on a Windows 7/8/10 and IIS
server.
 SQL server 2000 will act as the database for the project. The
project will run only on those web browser who support
JavaScript and it should be installed on User’s system.
 At the time of registration, each user is provided a unique ticket
number and that number will be used for further process.

ASSUMPTIONS AND DEPENDENCIES:

This system totally depends upon internet. Without internet, this
system cannot be operated. Admin and end-users cannot interact.
Power backup must be available.

SPECIFIC REQUIREMENTS:
EXTERNAL INTERFACES

There will be different type of appearance that would be displayed on the

screen while using this system.
 User Interface: One is Admin and the other is end-user that will
use this system. Interfaces for both type of the users will be GUI.
 Hardware Interface: Any specific hardware is not required for this
system.
 Software Interface: The application should run on a Windows
7/8/10 Operating System. SQL server 2000 would be used to
manage the database of the system.

FUNCTIONAL REQUIERMENTS:

Fictional Requirements of ARS for END-USER are as follows:

 Allow user to register himself on website and then login.

  Allow user to read the booking instruction from the webpage.

 Allow user to book flights.

 Allow user to contact the company.

 Allow user to see the schedule of flight.

 Allow user to cancel the booking.

Fictional Requirements of ARS for Administrator are as follows:

 Allow user to Login / Logout

 Allow user to Add / Delete / Modify Customer Information

 Allow user to Add / Delete / Modify Flight Information

 Allow user to Add / Delete / Modify Motel Information

 Allow user to Cancellation of Reservations

 Allow user to E-mail confirmations

 Allow user to Change the content of Webpage.

REPORT GENERATION:

In this system, after booking a seat in flight, a report will be

generated which will contain the flight name, flight number, seat number,
date of flight, time of flight and destination of the flight.

RETRIEVING AND DISPLAY UNIT INFORMATION:

 When the end-user register with our system, his login information
will be saved to the server. The Admin can view the details of the
registered user any time by just entering the passport number of the end
user. The number entered by the admin will be sent to the main server
and all entries will be searched. Then the information of the matching
one will be retrieved and displayed to the admin. The admin can change
or remove that information.

DATA ENTRY:

After creating this system, we have to enter data in it which will

contain the information of the administrator, airline companies, schedule
of flights, number of available seats, and some other information
regarding airlines. System will store the information of the system
operator at the admin side i.e. their logins and passwords. This system
will also store the information of the end users.

For this purpose, we have to enter all the data in the database of
the new system. We will assign this task to a team who will do this job.

DESIGN CONSTRAINSTS:

This design of this software is totally dependent upon the

centralized system. If that system fails, the whole server will be down
and the system fails. This system needs connectivity of internet to
communicate with other user and end-user, if the internet is disturbed,
the whole system will fail. Register the user, login, user can view its
profile, availability of seats in flights etc.

NON-FUNCTIONAL REQUIERMENTS:
 Non-functional requirements like the security and privacy issue.
Only authorized persons can access the database. Unauthorized
persons must not be allowed to the system. For this purpose, biometric
scanners, PIN codes and password will be used. Only Admin of the
system is allowed to add or modify records in the server. Details of the
user must be safe in database.

The system should access the records from database quickly.

Whenever we update the records in the database, it must show the
updated records with in very less time. The system should be reliable.
The software should be enough powerful so that it can engage huge
numbers of user at a time.

APPENDIX:

LOGIN:

LOGIN username

SUCCESSFULLY Login Password

Type

VALID ADMIN:

Maintain Information

View and edit info

VALID ADMIN PROCESS add a flight

 Update flight info

Update user info

Delete a flight

USE CASE DIAGRAM:

Search for Flight

Make Reservation

Cancel Reservation

Purchase Ticket