Functional Requirements of the system

 

...Start of the Functional Requirements of Airline Reservation System...

This project deals with the development of a Software Requirements Specification (SRS) document that specifies what an airline reservation system should and should not do. The SRS document is divided into five sections namely .. This section lists all the goals and objectives of the system categorized based on the viewpoint of the airline company and the customer (passenger). These are higher-level goals which are somewhat broad in nature. They help in a top-down development of the SRS.

             ...Middle of the Functional Requirements of Airline Reservation System...

The system shall now ask the user to enter the following details – class, one-way or round trip, departure date and the number of adult passengers, children and senior citizens. ‘Class’ refers to business class/first class/club class/smoking/non smoking. This choice shall be made by the user through a drop down menu indicating all the possible combinations of choices. One-way/round trip shall be either a drop down menu or a check box selection. ‘Departure date’ refers to either a single date or a range of dates, entered through a calendar-like menu.

            ...End of the Functional Requirements of Airline Reservation System...

Information about the kind of meals served in a flight and the type of entertainment offered on a flight should be incorporated into the system. Provide service integration with auto rental agencies and hotel chains. Interface for the travel agents shall be provided in the future versions with additional features like informing them of any availability of seats on a flight which was earlier booked to capacity. Choices like aisle or window seats shall be provided to the users. The ARS shall be able to handle the situation where flight services are available to multiple airports in a single city.