The Airline Reservation System Use Case Diagram is the behavioral diagram that summarizes activities done in the airline reservation system and its user details. It depicts the graphical representation of the system’s behavioral structure.
Additionally, the diagram consists of processes (use cases) and users or “actors”. It uses defined symbols to describe the overall workflow of the airline reservation system.
Check out the linked and suggested articles below to learn more about Diagrams and other topics.
- Online Airline Reservation UML Diagrams
- Activity Diagram for Airline Reservation
- ER Diagram for Airline Reservation
- Use Case Diagram for Online Ticket Reservation
- Airline Reservation System Class Diagram
- Component Diagram for Airline Reservation
Project Overview
| Name: | Airline Reservation System Use Case Diagram in UML |
| Users: | Airline Crews and Passengers |
| Tools Used: | Any Diagram tools that provide use case diagram symbols. |
| Designer: | ITSourceCode.com |
What is a Use Case Diagram?
The use case diagram in software engineering shows the sample adaptive behavior of the airline reservation system. It encapsulates the project’s functionality by incorporating use cases, actors, and their interactions.
Importance of UML Use Case Diagram
To help the developers and enterprises in developing the system is the importance of the UML use case diagram. It includes the procedures from the viewpoint of users.
Airline Reservation Use Case Diagram
The sample airline reservation system use case diagram includes actors, processes (use case), and their relationships.
General Use Case Diagram
This diagram presents the general use case of an airline reservation system. It shows the general processes or functions of the system. That are based on the activities done by the users during reservations.
The general use case is the most common application of a use case diagram. It shows the system’s main components as well as the flow of information between them. This helps programmers to have the basis on what could be put into consideration in creating the airline reservation system.
Use Case Diagram for Airline Reservation using Include and Extend
The broken arrows are indications that the following diagrams connected to them are parts of a process. They could either be one of the indications which were the include or extend.
The “include” indication means that the following use case was compulsory to finish the task and the “extend” indication is otherwise.
Downloadable Pdf File
How to draw a Use Case Diagram?
Time needed: 2 minutes
Here’s the complete guide on how to draw a use case diagram for airline reservation system.
- Step 1: Familiarize Use Case Diagram Symbols
For beginners in the field of designing the diagram, you need first to familiarize the symbols to be used.
- Step 2: Determine the targeted users
The next step is to determine your targeted users. They will be the ones to use your project.
You may ask the users about the typical activities done in airline system.
- Step 3: Analyze the use cases included
The gathered information from the users needs to be evaluated to know the general use cases.
- Step 4: Plot the Use Case Diagram
To plot the diagram you will need the users, use cases, container (scope), and their indicators (association). You will base the flow of use cases on the evaluated information from the users.
You need to place first the users involved.
Then place the figured use cases included in doing the process.
After that, you will trace the association of the use cases to know the interactions between the user/s and the system.
Finally, put the container in the plotted diagram to separate the objects’ (users and system) scope.
Conclusion:
The use case diagram is one of the methods that contribute to the airline reservation system design and development. It helps developers know the possible inputs and scenarios that the project should process and perform.
Inquiries
If you have inquiries or suggestions about the Use Case Diagram for Airline Reservation System, just leave us your comments below.
How to read a use case diagram
A use case diagram has 3 main elements: actors (stick figures outside the system), use cases (ovals inside the system boundary), and relationships between them.
- Actor. A role played by a human or external system that interacts with the system.
- Use case. A specific goal the actor accomplishes with the system.
- System boundary. The rectangle around the use cases marks what is inside vs outside.
- Association. Line between an actor and a use case they perform.
Use case relationships
- Include. Dashed arrow with “<<include>>” — one use case ALWAYS calls another (e.g., Login is included in Place Order).
- Extend. Dashed arrow with “<<extend>>” — an optional add-on to a base use case (e.g., Apply Discount extends Place Order).
- Generalization. Solid arrow with hollow triangle — one actor or use case is a specialized form of another.
Common capstone mistakes to avoid
- Too granular. Do not create a use case for each button. Focus on business goals like “Manage Inventory.”
- Missing actors. Every use case must be associated with at least one actor.
- Confusing include vs extend. Include is mandatory; Extend is optional.
- System actors as human. External payment gateways, email servers, etc. are actors too.
- No system boundary. Missing rectangle is a common panel critique.
Where the use case diagram fits in Chapter 3
- Section 3.1 (System Overview) or 3.2 (Functional Requirements).
- List each use case with a brief description in a table alongside the diagram.
- Reference each use case when explaining the workflow in later sections.
Official documentation
Working source code for this system
Download the actual implementation of this system in your preferred language. Each project includes source code, database, and setup instructions for BSIT capstone use.
Frequently asked questions
What is a use case diagram used for in BSIT capstone?
A use case diagram shows what the system does from the user’s perspective: actors, use cases, and their relationships (include, extend, generalization). It goes in Chapter 3 and communicates the functional requirements of the system.
What tool should I use to draw the use case diagram?
Free options: draw.io (browser-based, saves to Google Drive), Lucidchart free tier, PlantUML (text-based, version-controllable), StarUML (30-day trial then reduced feature set), Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.
How detailed does the use case diagram need to be for capstone defense?
Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification. Aim for 1-2 diagrams that fully cover the system, not many partial ones.
Should I use black-and-white or colored diagrams?
Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity (e.g., grouping subsystems). Ensure text is readable at printed size (10pt minimum for labels).
Where does this diagram go in the capstone documentation?
Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it. Reference specific elements in the surrounding text so panel members can follow the design rationale.
Mary Grace G. Patulada
Programmer & Technical Writer at PIES IT Solution
Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.
Expertise: UML Diagrams · DFD · ER Diagrams · Use Case Diagrams · Activity Diagrams · Capstone Documentation · PHP
· View all posts by Mary Grace G. Patulada →