This week you will perform requirements analysis. Using the details you provided in the "Specific Requirements/Functionality" section, you need to extract the use cases and create a use case diagram...

This week you will perform requirements analysis. Using the details you provided in the "Specific Requirements/Functionality" section, you need to extract the use cases and create a use case diagram by following these steps:

• Identify the actors


• Identify the Use Cases (at least 5) and write a brief description of each


• Identify the actors and the Use cases relationship


• Use the above to create your use case diagram using UML notation.


• Outline at least 2 individual Use Cases with details.

Add your use case diagram and use cases outline to your SRS document Appendix.

Software Requirements Engineering Individual Project Demetricus Dixon 2/24/2021 Table of Contents Introduction3 Overall Description3 Product Perspective3 Functions3 User Characteristics3 Constraints3 Requirements4 requirements analysis4 References5 Introduction This document can be used to get the requirement specification for the airline ticket reservation system. With this document it would be easier to maintain the changes for the project progresses. This report is based on the digital version of the airline ticket reservation from the manual system. Overall Description Product Perspective The existing manual system needs each customer to visit to the airline office to make booking. All the customers do not have enough time to come to the office and it creates long waiting area for the customers. The new system will allow the customers to make their booking for airlines from their home with the help of the system. Functions The new system will allow the customers to search for the flights description and also specify the description about the passengers. The passenger can sort the flights as per the description and they can also book flights. The system will allow the customer to cancel their booking or add new flights. The user can also modify the flight details or removed any existing flights from the system. The admin will be able to cancel the request and check for the booking details. User Characteristics The airline ticket reservation system can have 2 types of the user. One is the administration and another one is the customer. The customer does not need any training to use the system but he will be provided the instructions for making the reservation for the flight over the website. That administrator needs to be trained to use the application. Constraints The system has few constraints also. The flights dates and the hours need to be displayed as per the city of departure and time zone of destination. The daylight-saving time settings should be considered for every country. If there is any changes in the database then it should be displayed without any delay. Requirements · The customer should be able to search for the flights on the basis of specific date. · The system should allow the customer to manually enter the name of cities for departure and arrival. · The system should be able to accept the specific number of children while the customer is searching for the flight. · The customer should be able to request for cancellation regarding an existing booking. · The admin should be able to check details about flights, booking of the customer or the request for cancellation. · The system should validate all the information entered by the user. requirements analysis TBD References Copeland, D. G., & McKenney, J. L. (1988). Airline reservations systems: lessons from history. MIS quarterly, 353-370. Beckmann, M. J. (1958). Decision and team problems in airline reservations. Econometrica: Journal of the Econometric Society, 134-145. Law, R., & Leung, R. (2000). A study of airlines’ online reservation services on the Internet. Journal of Travel Research, 39(2), 202-211. Park, S., & Kim, S. I. (2019). A Study on the User Experience for Airline ticket Reservation Service-Focusing on Skyscanner App. Journal of the Korea Convergence Society, 10(2), 195-200.