Scribd
Upload
21 views

Software Requirements Specification

Uploaded by

Makkapati Deepthi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views

Software Requirements Specification

Uploaded by

Makkapati Deepthi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Requirements Specification (SRS) Document for

Flight Database System

1. Introduction

The Flight Database System is designed to provide a centralized repository of information about
flight departures from an airport. This system will be used by airport personnel, airlines,
passengers, and other stakeholders to keep track of flight departure details.

2. Scope

The Flight Database System will contain the following information about flight departures:

a. Departure Airport
b. Date of Departure
c. Time of Flight
d. Aircraft Type
e. Aircraft Registration
f. Origin Airport
g. Scheduled Time of Departure
h. Actual Time of Departure
i. Status
j. Delay Time (if any)

3. Functional Requirements

The Flight Database System will have the following functional requirements:
a. User Management: The system will have the capability to manage user access and
permissions to the system.

b. Flight Management: The system will allow users to add new flights, update or delete existing
flight details.

c. Search and Filter: The system will allow users to search and filter flight information based on
various parameters such as aircraft type, registration, origin airport, etc.

d. Reporting: The system will allow users to generate reports on flight departures based on
various parameters.

e. Alerting: The system will have the capability to alert users of delays or cancellations for
flights.

f. Integration with external systems: The system will be able to integrate with external systems,
such as airline reservation systems or airport information displays.

4. Non-functional Requirements

The Flight Database System will have the following non-functional requirements:

a. Security: The system will ensure the security of data and user access by implementing
authentication and authorization protocols.

b. Performance: The system will be designed to handle a large amount of data and provide fast
response times.

c. Reliability: The system will be designed to ensure data consistency and minimize data loss.
d. Scalability: The system will be designed to accommodate future expansion of data and users.

5. Assumptions and Constraints

a. The system will only contain information about flight departures and not about other
aviation-related entities such as airports, airlines, or pilots.

b. The system will be developed using the Microsoft SQL Server database management system.

c. The system will be developed using .NET Framework.

6. Glossary

a. Departure Airport: The airport from which the flight is departing.

b. Date of Departure: The date on which the flight is scheduled to depart.

c. Time of Flight: The time at which the flight is scheduled to depart.

d. Aircraft Type: The make and model of the aircraft.

e. Aircraft Registration: The unique identifier assigned to the aircraft by its national aviation
authority.

f. Origin Airport: The airport from which the flight is departing.

g. Scheduled Time of Departure: The time at which the flight is scheduled to depart.
h. Actual Time of Departure: The time at which the flight actually departs.

i. Status: The status of the flight, such as on-time, delayed, or cancelled.

j. Delay Time: The amount of time by which the flight is delayed.

7. Conclusion

The Flight Database System will be an essential tool for airport personnel, airlines, and
passengers to manage and maintain information about flight departures. The system will ensure
that flight departure information is easily accessible, accurate, and up-to-date, providing a
smooth and efficient experience for all stakeholders.

You might also like