Software Requirements Specification (SRS) is a document that describes the nature of a project, software or application. In simple words, SRS document is a manual of a project provided it is prepared by you before starting any project/application. This document is also known as SRS report, software document. Software document is mainly prepared for a project, software or any type of application.
There are certain guidelines to be followed while preparing software requirements specification document. This includes the project’s purpose, scope, functional and non-functional requirements, software and hardware requirements. In addition, it also includes information about the required environmental conditions, safety and security requirements, software quality characteristics of the project, etc.
What is a Software Requirements Specification Document?
The software requirements specification document describes the intended purpose, requirements and nature of the software to be developed. This also includes the yield and cost of the software.
In this document, the Flight Management Project is used as an example to explain some points.
Why use SRS?
If developers don’t have clear guidelines when creating a new product, you may end up spending more time and money than expected to get the software to match what you have in mind.
Creating an SRS document helps you get your idea down on paper and set a clear list of requirements. This document becomes your sole source of product integrity, so all your teams—from marketing to maintenance—are on the same page.
Because software requirements specifications are living documents, they can also serve as a point of communication between each stakeholder involved in the product development process. Product iterations abound during any software development project – taking into account changes to the SRS, all parties can validate them in the document. This will reduce any confusion regarding product requirements.
How to go Incognito Mode incognito Mode in Chrome, Safari ,Opera , Edge, and Firefox | How to go incognito in Google Chrome | Private browsing mode chrome
1. INTRODUCTION of Software Requirements Specification document
The purpose of this document is to build an online system for managing flights and passengers to make flight management easier. <<Include the objective applicable to your project >>
1.2 Document Convention
This document uses the following conventions. <<Include conventions according to your application >>
1.3 INTENDED AUDIENCE AND READING SUGGESTIONS
The project is a prototype for a flight management system and is restricted within the college campus. It is implemented under the guidance of college professors. This project is useful for the flight management team as well as the passengers.
1.4 Project Scope
The Online Flight Management System aims to simplify flight management and create a convenient and easy-to-use application for travelers 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 different airline companies. Above all, we hope to provide a comfortable user experience with the best pricing available.
What is the Metaverse reality Headset | Metaverse: The New Web is Here, Where are You?
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
A distributed airline database system stores the following information.
- Flight details:
This includes the originating flight terminal and destination terminal as well as stops in between, number of seats booked/number of seats available between two destinations, etc.
- Customer description:
This includes the customer code, name, address and phone number. This information may be used to keep customer records in case of an emergency or for any other type of information.
- Reservation description:
This includes customer details, code number, flight number, date of booking, date of travel.
2.2 PRODUCT FEATURES
The salient features of Airline Database System as shown below entity–relationship model (ER model)
2.3 USER CLASS and CHARACTERISTICS
Users of the system should be able to retrieve flight information between two given cities along with the given date/time of travel from the database. The route from city A to city B is a sequence of connecting flights from A to B: a) there are at most two connecting stops, excluding the starting city and destination city of the journey, b) the connecting time is between one and two hours. The system will support two types of user privileges, customer and employee. Customers will have access to customer functions, and employees will have access to both customer and flight management functions. The customer should be able to do the following:
- Make a new reservation
• Flexible Date/time
- 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.
• 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 many flights that depart or arrive at different dates and times from different cities.
2.4 Operating Environment
The operating environment for the Airline Management System is listed below. <<Include details as per your application>>
- distributed database
- client/server system
- Operating system: Windows.
- database: sql+ database
- platform: vb.net/Java/PHP
2.5 DESIGN and IMPLEMENTATION CONSTRAINTS
- Global schema, fragmentation schema, and allocation schema.
- SQL commands for above queries/applications
- How will the response be generated for Application 1 and 2. Let’s say these are global queries. Explain how the different pieces will be connected to make this happen.
- Implement the database using at least one centralized database management system.
2.6 ASSUMPTION DEPENDENCIES
Let’s assume this is a distributed airline management system and it is used in the following application:
- Request for booking/cancellation of flight from any source to any destination, granting connected flights in case there is no direct flight between specified source-destination pair.
- Calculation of high fliers (most frequent fliers) and calculation of appropriate reward points for these fliers.
Assuming that both the transactions are single transactions, we have created a distributed database which is geographically spread across four cities of Delhi, Mumbai, Chennai and Kolkata as shown in Fig. Below.
3. SYSTEM FEATURES
The airline reservation system holds information about flights, classes of seats, personal preferences, prices and bookings. Of course, this project has a high priority because it is very difficult to travel across countries without prior reservation.
- STIMULUS/RESPONSE SEQUENCES
- Find airline flights for two travel cities
- Displays a detailed list of available flights and makes “reservations” or booking tickets on a particular flight.
- Cancel existing reservation.
Other system features include:
Merry Christmas 2022: Quotes ,Images, Messages, Greetings ,Wishes, Cards, Pictures and GIFs
Distributed database implies that a single application should be able to operate transparently on data which is spread across different databases and connected over communication networks as shown in the figure below.
Distributed database located in four different cities
The term client/server primarily refers to an architecture or logical division of responsibilities, the client is the application (also known as the front-end), and the server DBMS (also known as the back-end) Is.
A client/server system is a distributed system in which,
- Some sites are client sites and others are server sites.
- All data resides on server sites.
- All applications execute on client sites.
4. EXTERNAL INTERFACE REQUIREMENTS4.1 USER INTERFACES
- Front-end software: Vb.net version
- Back-end software: SQL+
4.2 HARDWARE INTERFACES
4.3 SOFTWARE INTERFACES
Following are the software used for flight management online application. <<Include software details according to your project >>
||We have chosen the Windows operating system for its best support and user-friendliness.
||We have chosen SQL+ database to store flight records, passengers records.
||To implement the project we have chosen Vb.Net language for its more interactive support.
4.4 COMMUNICATION INTERFACES
This project supports all types of web browsers. We are using simple electronic form for reservation form, ticket booking etc.
5. NONFUNCTIONAL REQUIREMENTS