Software Requirements

Specifications
Airport Management System

Kunj Dhami (17BIT017)

Dhruvin Navapara(17BIT018)
Haider Ali (17BIT025)
Jay Patel (17BIT033)
Surbhi Kathiriya (17BIT035)

1
Table of Contents
1. Introduction
1.1 Purpose
1.2 Intended Audience and Reading Suggestions
1.3 Project Scope
1.4 References

2. Overall Description
2.1 Product Perspective
2.2 Product Features
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 Assumptions and Dependencies

3. System Requirements
3.1 Functional Requirements
3.2 User Interfaces
3.3 Hardware Interfaces
3.4 Software Interfaces
3.5 Communications Interfaces

4. Non-Functional Requirements
4.1 Performance Requirements
4.2 Safety Requirements
4.3 Security Requirements
4.4 Software Quality Attributes

2
 1. Introduction
1.1 Purpose

The purpose of this document is to build an online system to manage flights

and passengers to ease the airport management. It outlines the requirements,
both Functional and Non-Functional and serves as a communication medium
between the developers and the stakeholders.

1.2 Intended Audience and Reading Suggestions

This project is a prototype for the airport management system and it is

restricted within the college premises. This has been implemented under the
guidance of college professors. This document serves as a communication
medium and a contract between the developers and the stakeholders; the
system must adhere to all the requirements that are listed. The intended
Audience for this document includes Prof. Smita Darandale, the software
engineering team, and all the other entities who may have interest in the AMS.

1.3 Project Scope

The purpose of the online airport management system is to ease airport

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. Above all, we
hope to provide a comfortable user experience along with the best pricing
available.

1.4 References
[1] https://krazytech.com/projects
[2] Fundamentals of Database Systems by Ramez Elmarsi and Shamkant
B.Navathe
[3] Elsa Tai. (2014). Requirements Definition Document

3
 2. Overall Description
2.1 Product Perspective

An airport management system stores the following information.

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 Product Features

In Progress

2.3 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:

4
 ▪ Make a New Reservation
▪ Cancel an Existing Reservation
▪ View his Itinerary

The Employee should have the following 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.

▪ Administrative Functions
• Add/Delete a flight
• Add a new airport
• Update fare for flights.
• Allocate Gates to the Flight
• Allocate Conveyor Belts

2.4 Operating Environments

Operating environment for the airport management system is as listed below.

• Database: MySQL
• Client/Server System
• OS: Windows
• Platform: React, HTML, CSS, Bootstrap, PHP, Laravel
2.5 Design and Implementation Constraints

2.6 Assumptions and Dependencies

5
 3. System Requirements
3.1 Functional Requirements

(FR-1) Checking availability:

1. After logging in, the user should be able to check the available
flight details.
2. He will be able to see all the airline details
(FR-2) Making Reservations/Blocking/Confirmation/Reschedule/Cancel Ticket
1. Users can make reservations for the tickets, also can hold the tickets for
24 hrs.
2. They can Confirm their tickets and also can reschedule the tickets.
3. Users will also be able to cancel their tickets within the cancellation
policy.
(FR-3) User Account
1. Users will have to create their profile and give their personal details to
the system for proper management.
2. They can also update their profile at any time.
3. Users will be able to view ticket status.
4. Users will be able to view their travelling history.
(FR-4) Gate Allocation
1. To allocate the gates available to the flights.
2. Customers will be allocated the gate and the location of the gate
allocated before some time so that they can reach the allocated gate on
given time.
(FR-5) Counter Allocation
1. To allocate from different counters to airlines.
2. Customers will have to verify themselves at the allocated counter.
3. They can collect their tickets from their respective airline counter which
will be allocated by the particular airline.
(FR-6) Baggage Carousel/Conveyor Belt Allocation
1. Customers will be allocated to their respective airline carousel.
2. Customers will have to collect their baggage from the allocated
carousel.

6
 3.2 User Interfaces

3.3 Hardware Interfaces

3.4 Software Interfaces

3.5 Communication Interfaces

4. Non-Functional Requirements
4.1 Performance Requirements

No performance Requirements specified at this time.

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

7
• MAINTAINABILITY: The administrators and flight in chargers should
maintain correct schedules of flights.
• USABILITY: The flight schedules should satisfy a maximum number of
customer’s needs.