Use Case Diagram for the Airline Management System
Explore the design of a use case diagram for an airline management system by identifying primary and secondary actors and outlining their interactions. Understand how customers, front desk officers, admins, system, and crew participate in flight searches, reservations, payments, and notifications. This lesson helps you grasp how to represent system functionalities and relationships effectively in UML diagrams to prepare for object-oriented design interviews.
Let’s build the airline management system’s use case diagram and understand its components. First, we’ll define the different elements of our airline, followed by the complete use case diagram of the system.
System
Our system is an airline.
Actors
Now, we’ll define the main actors of the airline management system.
Primary actors
Customer: The customer is the primary actor for the airline. The customer can search for flights, create an itinerary, make a payment, and update or cancel the flight reservation.
Front desk officer: This actor can perform all the actions that the customer can. The front desk officer can create an itinerary, make payments, update or cancel flight reservations on behalf of customers, assign seats, and search for flights.
Admin: The admin is responsible for performing various operations, including adding aircraft to the system, creating or modifying flights, flight instances, and their schedules, canceling flights, and assigning crew to flights. ...