Airline reservation system – Functional and Non-functional requirements

Functional requirements of the airline reservation system

The following are some functional criteria for an airline reservation system:

  1. Users should be able to view and change their existing bookings.
  2. Provide customer service via a call centre or online chat.
  3. Allow users to find flights depending on their origin, destination, and preferred travel dates.
  4. Display available flights, together with information such as departure and arrival timings, layover duration, and ticket price.
  5. Provide real-time flight status updates, including delays and cancellations.
  6. Allow users to check in online for their travel, including selecting a seat and printing a boarding card.
  7. Integrate with the airline’s loyalty programme to allow users to redeem points for flights.
  8. Allow consumers to choose and purchase flights.
  9. Accept payment for the flight reservation.
  10. Please provide a booking confirmation with a reservation number and itinerary.
  11. These are only a few examples of functional requirements for an airline reservation system.
    The particular requirements will be determined by the airline’s objectives and aims.

Non Functional requirements of airline reservation system

Non-functional requirements specify how a system should function rather than what it should do.
Non-functional needs for an airline reservation system could include:

  1. Performance: The system should be able to manage a high volume of requests and transactions with minimal delays or performance concerns.
  2. Scalability: The system should be able to scale up or down to meet changing demand.
  3. Security: The system should protect sensitive client data and maintain the security of all transactions.
  4. Interoperability: As needed, the system should be able to integrate with other systems and platforms.
  5. Compliance: The system must meet all essential regulatory and industry security, privacy, and data protection standards.
  6. Availability: The system should be available at all times, with as little downtime as possible for maintenance or updates.
  7. Usability: The system should be simple to use for both customers and staff, with a simple and straightforward interface.
  8. Maintainability: The system should be simple to maintain and update, with low downtime.

Leave a Reply

Your email address will not be published. Required fields are marked *