use case diagram case study

Use Case Diagram Tutorial (Guide with Examples)

Use case diagram is a behavioral UML diagram type and frequently used to analyze various systems. They enable you to visualize the different types of roles in a system and how those roles interact with the system. This use case diagram tutorial will cover the following topics and help you create use cases better.

What is a UML Use Case Diagram

Importance of use case diagrams.

• Use Case Diagram Objects

Use Case Diagram Guidelines

Relationships in use case diagrams, identifying actors, identifying use cases.

• When to Use “Include”
• How to Use Generalization
• When to Use “Extend”
• Use Case Diagram Templates of Common Scenarios

A UML (Unified Modeling Language) use case diagram is a visual representation of the interactions between actors (users or external systems) and a system under consideration. It depicts the functionality or behavior of a system from the user’s perspective. Use case diagrams capture the functional requirements of a system and help to identify how different actors interact with the system to achieve specific goals or tasks.

Use case diagrams provide a high-level overview of the system’s functionality, showing the different features or capabilities it offers and how users or external systems interact with it. They serve as a communication tool between stakeholders, helping to clarify and validate requirements, identify system boundaries, and support the development and testing processes.

As mentioned before use case diagrams are used to gather a usage requirement of a system. Depending on your requirement you can use that data in different ways. Below are few ways to use them.

• To identify functions and how roles interact with them – The primary purpose of use case diagrams.
• For a high-level view of the system – Especially useful when presenting to managers or stakeholders. You can highlight the roles that interact with the system and the functionality provided by the system without going deep into inner workings of the system.
• To identify internal and external factors – This might sound simple but in large complex projects a system can be identified as an external role in another use case.

Use Case Diagram objects

Use case diagrams consist of 4 objects.

The objects are further explained below.

Although use case diagrams can be used for various purposes there are some common guidelines you need to follow when drawing use cases.

These include naming standards, directions of arrows, the placing of use cases, usage of system boxes and also proper usage of relationships.

We’ve covered these guidelines in detail in a separate blog post. So go ahead and check out use case diagram guidelines .

There are five types of relationships in a use case diagram. They are

• Association between an actor and a use case
• Generalization of an actor
• Extend relationship between two use cases
• Include relationship between two use cases
• Generalization of a use case

We have covered all these relationships in a separate blog post that has examples with images. We will not go into detail in this post but you can check out relationships in use case diagrams .

How to Create a Use Case Diagram

Up to now, you’ve learned about objects, relationships and guidelines that are critical when drawing use case diagrams. I’ll explain the various processes using a banking system as an example.

• Look for Common Functionality to Reuse

Is it Possible to Generalize Actors and Use Cases

Optional functions or additional functions.

• Validate and Refine the Diagram

Actors are external entities that interact with your system. It can be a person, another system or an organization. In a banking system, the most obvious actor is the customer. Other actors can be bank employee or cashier depending on the role you’re trying to show in the use case.

An example of an external organization can be the tax authority or the central bank. The loan processor is a good example of an external system associated as an actor.

Now it’s time to identify the use cases. A good way to do this is to identify what the actors need from the system. In a banking system, a customer will need to open accounts, deposit and withdraw funds, request check books and similar functions. So all of these can be considered as use cases.

Top level use cases should always provide a complete function required by an actor. You can extend or include use cases depending on the complexity of the system.

Once you identify the actors and the top level use case you have a basic idea of the system. Now you can fine tune it and add extra layers of detail to it.

Look for Common Functionality to Use ‘Include’

Look for common functionality that can be reused across the system. If you find two or more use cases that share common functionality you can extract the common functions and add it to a separate use case. Then you can connect it via the include relationship to show that it’s always called when the original use case is executed. ( see the diagram for an example ).

There may be instances where actors are associated with similar use cases while triggering a few use cases unique only to them. In such instances, you can generalize the actor to show the inheritance of functions. You can do a similar thing for use case as well.

One of the best examples of this is “Make Payment” use case in a payment system. You can further generalize it to “Pay by Credit Card”, “Pay by Cash”, “Pay by Check” etc. All of them have the attributes and the functionality of payment with special scenarios unique to them.

There are some functions that are triggered optionally. In such cases, you can use the extend relationship and attach an extension rule to it. In the below banking system example “Calculate Bonus” is optional and only triggers when a certain condition is matched.

Extend doesn’t always mean it’s optional. Sometimes the use case connected by extending can supplement the base use case. The thing to remember is that the base use case should be able to perform a function on its own even if the extending use case is not called.

Use Case Diagram Templates

We’ve gone ahead and created use case diagram templates for some common scenarios. Although your problem or scenario won’t be exactly like this you can use them as a starting point. Check out our use case diagram templates .

Questions Regarding the Use Case Diagram Tutorial

We’ve tried to comprehensively cover everything you need to know about creating use case diagrams. If you have doubts about any section or can think of ways to improve this tutorial please let us know in the comments.

More Diagram Tutorials

• Sequence Diagram Tutorial: Complete Guide with Examples
• Business Process Modeling Tutorial (BPM Guide Explaining Features)
• Ultimate Flowchart Guide (Complete Flowchart Tutorial with Examples)

FAQs on Use Case Diagrams

When to apply use case diagrams.

• Requirement analysis : Use case diagrams aid in understanding and documenting the functional requirements of a system by identifying actors and their interactions.
• System design : Use case diagrams provide a high-level overview of system functionality, helping to define scope and design system components.
• Communication with stakeholders : Use case diagrams facilitate discussions and ensure a shared understanding with stakeholders.
• Project planning and management : Use case diagrams assist in defining scope, prioritizing requirements, and identifying risks.
• Test planning : Use case diagrams help identify scenarios and generate test cases for comprehensive test coverage.
• Documentation : Use case diagrams serve as documentation artifacts for future development, maintenance, and upgrades.

What are the best practices for drawing use case diagrams?

• Identify actors and use cases : Clearly identify the actors, representing external entities interacting with the system, and the use cases, representing system functionalities.
• Use descriptive names : Choose meaningful and descriptive names for actors and use cases to ensure clarity and understanding.
• Define relationships : Establish relationships between actors and use cases to depict their interactions. Use arrows to show the direction of the interaction.
• Keep it simple : Avoid overcomplicating the diagram by focusing on the most essential actors and use cases. Too many details can make the diagram confusing and less effective.
• Use appropriate notation : Follow the standard UML notation for use case diagrams, including ovals for use cases, stick figures for actors, and arrows for relationships.
• Organize and layout : Arrange the actors and use cases in a logical and organized manner, ensuring a clear flow of information. Use lines and connectors to connect related use cases.
• Use hierarchical structure : If the system has complex functionality, consider using a hierarchical structure with primary use cases at the top level and detailed use cases nested beneath.

What is included and not included in a use case diagram?

In a use case diagram, the following elements are typically included:

• Actors: Represent external entities interacting with the system.
• Use cases: Represent specific functionalities or actions performed by the system.
• Relationships: Connect actors and use cases to show interactions and dependencies.
• System boundary: Encloses use cases and actors within the scope of the system.
• Communication paths: Arrows or lines indicating the flow of communication.

On the other hand, use case diagrams do not include the following:

• Internal system details: Focus on high-level functionality, not specific components.
• Sequence of actions: No specific order of execution shown.
• Implementation details: Independent of implementation specifics.
• User interface details: No depiction of visual design or interface elements.

Software engineer turned tech evangelist. I handle marketing stuff here at Creately including writing blog posts and handling social media accounts. In my spare time, I love to read and travel.

Related Tools and Resources

Join over thousands of organizations that use Creately to brainstorm, plan, analyze, and execute their projects successfully.

What is a use case?

Benefit of use cases, building a use case diagram step-by-step.

• Excellent use case examples

Testing and validating use cases

Validation criteria, use case diagramming best practices and examples.

Explore how dashboards can showcase critical app information effectively. Dive into our expert tips for crafting the perfect dashboard design.

In this article, we’re diving deep into the world of use cases—what they are, why they matter, and how to create them step-by-step. You’ll get a clear understanding from start to finish, complete with awesome examples that bring each concept to life. Whether you’re just starting out in UX or looking to level up your skills, this guide has everything you need to master use cases like a pro. Let’s do this!

Design your use case diagrams with Justinmind!

20 Excellent use case diagram examples

The wrap-up.

To start, we need to define what it is. Firstly, let’s cover the difference between use case vs user story so you don’t end up confusing the two as you read on. 

A user story is a short, simple description of what a product should do, who it’s for, and why it’s needed. It’s usually just one or two sentences long and uses an easy-to-understand format so everyone can quickly grasp and act on it. 

Whereas a use case is a technique used in software development to capture the functional requirements of a system. It represents the interactions between users (actors) and the system itself to achieve specific goals. 

The purpose of a use case is to provide a clear understanding of how the system should behave under various conditions and to guide the development process by managing scope, establishing requirements, outlining the ways a user will interact with the system, visualizing system architecture, and communicating technical requirements to business stakeholders.

At first use cases seem to work in the same way as user flows charts, however, the aim here is to focus on functional requirements and covering all possible scenarios. The use of use cases (no, that’s not just a clever play on words) offers several benefits in the software development process.

Use cases help identify potential issues and edge cases early in the development process, allowing for more effective problem-solving and preventing costly rework later on. To break it down further, a use case achieves its purpose through several key mechanisms listed below:

Descriptive narratives

Each use case is a narrative that describes how users (actors) interact with the system to achieve specific goals. 

These narratives include several key elements, such as the title and description summarizing the goal and functionality of the use case, actors identifying the users or external systems interacting with the system, as well as preconditions that state the conditions that must be true before the use case begins. 

Furthermore, the basic flow outlines the steps for a successful interaction, focusing on the “happy path” where everything goes as planned, and alternative flows describe variations and exceptions from the main flow, including error handling and alternative paths.

Visual representation

Use case diagrams visually depict the interactions between actors and the system, providing a clear and concise overview. These diagrams typically include actors, represented as stick figures or roles outside the system boundary, and use cases, shown as ovals within the system boundary, each representing a specific function or goal. Interactions are illustrated by lines connecting actors to use cases, showing how they interact.

Structuring scenarios

Use cases structure the interaction scenarios by detailing the main success scenario, which is also referred to as the ¨Happy Path.¨ It is the standard sequence of steps that lead to a successful outcome. Alternative scenarios, on the other hand, outline different paths that may be taken, including handling of exceptional situations and errors.

Defining requirements

By capturing the expected behavior of the system from the user’s perspective, use cases help define requirements, or functional specifications . Which, in short, means that they help illustrate what the system should do, but not how it should do it.

Communication tool

Communication is key in the digital world. Use cases act as a bridge between stakeholders, such as business analysts, developers, testers, and end-users. They provide a common language and a clear understanding of system behavior, which helps in receiving stakeholder input by gathering requirements . They also facilitate clarification, ensuring that all parties have a clear and consistent understanding of the system’s functionality.

Driving implementation

Use case diagrams guide the development process by defining scope, clearly outlining what is included in the system and what is not. They also help in creating test cases by providing a basis for developing scenarios that ensure the system meets its requirements and behaves as expected. 

Additionally, use case diagrams help validate system design by ensuring all user interactions are accounted for and properly implemented. As the project evolves, use cases can be updated to reflect changes in requirements, helping in managing changes and ensuring the development process remains aligned with user needs and system goals.

Creating use case diagrams can seem daunting, but breaking down the process into manageable steps can make it much more approachable. These diagrams are essential for visualizing the interactions between users and a system, helping to clarify requirements and streamline development. 

This guide will walk you through the process of building use case diagrams, from identifying actors to structuring and visually representing use cases. Follow these steps to ensure that your use case diagrams effectively capture the necessary interactions and support the development of a robust system.

1. Identifying actors

This is where we figure out who will be using our system. Think about all the different types of people or systems that will interact with what we’re designing. For example, if we’re making a social media app, our actors might be regular users, administrators, and maybe even external systems like a messaging service.

• Users : Start by identifying the different user types who will interact with the system. These users may have varying goals and requirements.
• External Systems : Identify any external systems or integrations that the system will interact with, such as databases or third-parties.

2. Structuring a use case diagram

In this section, we’ll explore the key elements involved in structuring a use case, from defining its title and description to outlining the main flow and considering alternative paths. By following this structured approach, we can develop comprehensive and user-centric systems that cater to both the expected scenarios and the unexpected challenges that may arise during interaction.

• Title & Description : Each action or task the system can perform needs a clear name and a short explanation of what it does.
• Actors : We need to know who’s involved in each action. Are users doing this task? Or is it something the system does automatically?
• Preconditions : Before we can do anything, are there any conditions that need to be met? Like, maybe you need to be logged in before you can post something.
• Basic Flow : This is the main path we expect users to follow when they’re doing this task. It’s like a step-by-step guide to success.
• Focus on the Happy Path : This means we’re looking at the best-case scenario, where everything goes smoothly. It’s the most common way people will use our system.
• Alternative Flows : But life isn’t always perfect, right? So, we also need to think about what could go wrong or how people might do things differently. These are like detours from the main path, but we still need to plan for them.

3. Visual representation

Now, we take all that information and put it into a diagram. This diagram shows who’s doing what and how they’re doing it. We’ve got the main steps laid out clearly, but we also show those alternate paths we talked about. This way, anyone looking at the diagram can understand how our system works, from start to finish, even if things don’t always go according to plan.

In this section, we present 20 excellent use case diagram examples, each highlighting different aspects and applications of this powerful modeling tool. These examples span a range of industries and scenarios, showcasing the versatility and utility of use case diagrams in capturing system requirements and user interactions.

1. Online therapy platform

The Online Therapy Platform use case example brilliantly showcases its key functions, making it super easy to understand how users can navigate the platform. With features like booking therapy sessions, attending them online, checking out therapist profiles, and managing bookings, it’s like having a personal guide through the whole process.

Whether you’re scheduling a session through “Book Therapy Session,” chatting with your therapist via the “Attend Therapy Session” feature, exploring therapist backgrounds with “View Therapist Profile,” or keeping track of all your appointments with “View Bookings,” everything feels smooth and user-friendly.

2. Ride sharing service

In the ride-sharing service use case template, the primary actors include the Rider, Driver, and Administrator. Riders can request rides, view driver details, track their rides in real-time, make payments, rate drivers, and manage complaints. Drivers can accept or decline ride requests, view rider details, navigate to pick-up and drop-off locations, rate riders, and manage their profiles.

Administrators oversee the system by managing drivers, viewing various reports, handling rider complaints, and updating system settings. These functions collectively ensure a seamless, efficient, and user-friendly experience for all users.

3. Supply chain management system

The supply chain management system use case example includes six main actions: Track Shipments, Manage Distributions, Manage Manufacturers, Manage Suppliers, Manage Inventory, and Process Orders. 

Users can track shipments, manage product delivery logistics, handle manufacturer contracts and quality standards, manage supplier relationships, monitor inventory levels, and manage the flow of orders through the supply chain. This diagram helps improve communication, reduce errors, and enhance the efficiency and success of the supply chain operations.

4. Railway reservation

The railway reservation system use case diagram outlines key functions including Search Trains, Book Tickets, Cancel Tickets, Register User, Login, and Generate Reports. Passengers can search for trains, book and cancel tickets, and manage their user accounts. 

Administrators handle user registrations, generate reports, and oversee system operations, ensuring efficient and effective management of the railway reservation process.

5. Online bookshop

The UML communication use case example models interactions between objects in a sequence, illustrating both the static structure and dynamic behavior of a system. It shows how objects collaborate through a series of messages to fulfill a specific use case or functionality.

This diagram helps in understanding object interactions and system architecture, enhancing communication and design clarity.

6. Hotel Booking

The hotel booking platform use case template spotlights five key functionalities: Search for Availability, Select Accommodations, Manage Reservations, Account Management, and Confirmation. This translates to users enjoying seamless room searches based on specific criteria, effortless selection of their ideal accommodations, and convenient reservation management tools. 

Additionally, the platform empowers users with centralized account management and provides clear confirmation emails for peace of mind. This visual roadmap fosters clear communication between users and the platform, minimizing booking errors and streamlining the entire hotel booking experience.

7. Library management system

The library management system use case example shines a light on the key interactions between two user groups: librarians and borrowers. It maps out the actions each can perform within the system. Librarians wield the system to efficiently manage the library’s collection.

This includes adding new books, updating existing information, removing outdated materials, searching for specific titles, and viewing detailed information about any book in the system.

8. Online banking system

We love this use case diagram of an online banking system because it clearly outlines the roles and responsibilities within a banking system, making it easy to understand how different users interact with various functions.

It effectively uses visual elements to show relationships and dependencies between tasks, such as how security management extends to customer support and how account management includes loan management.

9. Online education platform

The online education platform use case diagram highlights the key interactions between users and the platform, guiding them through their learning journey. Firstly, users can explore the course catalog, viewing descriptions, instructors, and durations to find the perfect fit.

Once a course piques their interest, users can seamlessly enroll, gaining access to course content and embarking on their learning path. The platform empowers users to track their progress throughout the course, monitoring completed tasks, upcoming deadlines, and their earned grades with instructor feedback.

10. Health and fitness tracker

The health and fitness tracker use case example focuses on three key players: the user, their trainer, and their doctor. It illustrates a collaborative approach to health and fitness. Firstly, the user can easily share their progress data with both their trainer and doctor. This empowers all parties with a holistic view of the user’s health. Secondly, the trainer and doctor can access the user’s profile and work together to set personalized goals. 

The trainer can then leverage the app to track the user’s progress towards those goals, ensuring they stay on track. This visual representation highlights how clear communication and collaboration between the user, trainer, and doctor can contribute to achieving optimal health and fitness outcomes. We’re here for it!

11. Flight reservation system

The flight reservation system use case template encompasses various functionalities for both customers and administrators. Customers can select flights by searching based on criteria like departure and arrival locations and travel dates. They can then book flights by entering personal and payment details, choosing seats, and specifying any additional services required.

Additionally, customers have the option to cancel their bookings without needing to contact the airline directly. On the administrative side, admins have the ability to manage flights by adding, editing, or canceling flight schedules to adapt to demand and other operational needs. This comprehensive system ensures smooth operation and user-friendly interactions for both parties.

12. Movie ticket reservation

The movie ticket reservation system use case is designed to illustrate that booking tickets can be a breeze for everyone. As a user, you can easily browse through a list of movies, check out detailed information, pick your favorite showtimes, and select the best seats. Once you’re ready, you can securely make your payment. After the payment is confirmed, you can print your tickets right away, skipping those long lines at the theater.

For administrators, managing the system is just as simple. You can add new movies, set up schedules, and organize seating arrangements without any hassle. This system aims to provide a smooth and enjoyable experience for both movie lovers and theater staff.

13. Medical prescription use case diagram

This comprehensive system use case diagram ensures efficient ordering and management for customers, hospitals, and administrators. Customers can browse and search for available medicines, add selected items to their cart, provide delivery details, confirm their order, track its status, and complete the transaction through various payment methods. 

Administrators have the capability to manage the inventory by adding, updating, or removing medicines, as well as processing orders through verification, packaging, and dispatch. Hospitals benefit from the ability to place bulk orders for medicines, track and manage their orders, and confirm receipt of shipments.

14. Ride hailing service

The use case diagram for the ride-hailing service showcases the primary functionalities and interactions within the platform, highlighting different actors and their corresponding actions. It outlines roles such as the Rider and the Driver. 

The Rider can perform tasks like requesting and canceling rides, viewing ride details, rating drivers, updating their profile, and checking driver ratings. On the other hand, the Driver is capable of accepting ride requests, starting rides, and ending rides.

15. Stock trading platform

The use case example for the stock trading platform highlights the key functionalities and user interactions. Traders can register, log in, view market data, search for stocks, place and cancel orders, manage their portfolios, and handle funds. Admins oversee user accounts and trading activities, while customer support ensures traders receive the necessary assistance. 

External systems like the market data provider play crucial roles in delivering real-time data and handling financial transactions, respectively. This comprehensive representation aids in understanding the platform’s operational flow and user engagement.

16. Social network platform

The social networking platform use case example illustrates several key features for users. Users can create accounts by providing basic details like username, email, and password, enabling them to log in later. Once logged in, they can view their own profile and others’, including details like name, profile picture, and bio, with the ability to update their own information.

Users can also browse content shared by others in their feed, consisting of updates, photos, and videos. If users decide to leave the platform, they can delete their accounts, including all associated content. Additionally, users have the option to report inappropriate content, which platform administrators will review and potentially take action on, such as content removal or account suspension.

17. Virtual event platform

This virtual event platform is an online solution for organizations to host events virtually, comprising several crucial functionalities outlined in its use case template. These functionalities include managing speakers and attendees, scheduling sessions, providing networking opportunities, facilitating Q&A sessions, streaming sessions, and creating the event itself. 

Enabling networking opportunities fosters community engagement among attendees, while Q&A sessions facilitate interaction and knowledge exchange. Streaming sessions ensure accessibility for attendees worldwide. Managing speakers involves handling contracts, scheduling sessions, and maintaining quality standards. Session scheduling and attendee management are vital for event logistics, while creating the event encompasses coordinating sessions, speakers, and attendees to ensure seamless execution.

18. Restaurant management

The restaurant management use case diagram illustrates the key functionalities of a restaurant management system. Firstly, customers can view the menu, accessing item descriptions, prices, and optional allergen and dietary information. Secondly, they can place orders, facilitated either by a server or self-service kiosk, with orders transmitted to the kitchen for preparation and serving. 

Thirdly, customers can settle bills using various payment methods, including cash, credit card, or mobile payment, with options for bill splitting and receipt generation. Lastly, managers can utilize the system to oversee inventory levels, supplier management, and staff performance, with features for generating reports on inventory usage, sales trends, and labor costs for accounting purposes.

19. Project management

The project management system use case example encompasses several critical use cases, as illustrated here. Firstly, the case of assign task involves allocating tasks to team members with deadlines, aiding in clarity and efficiency. It may include features like prioritization and task dependencies for streamlined task management. Secondly, track progress enables real-time monitoring of project progress, ensuring timely identification and resolution of issues.

The use case template also illustrates features like progress tracking and milestone updates for enhanced transparency. Thirdly, generate report allows for the creation of comprehensive reports on project aspects such as progress and budget, aiding decision-making with tools like customizable templates. And finally, edit project facilitates alterations to project details while maintaining alignment with organizational goals through features like version control and approval workflows.

20. Grocery cart system

The grocery cart system use case example offers a comprehensive overview of the functionalities within an online grocery shopping platform, ensuring a seamless user experience. Customers can easily add and remove items from their cart, facilitating convenient shopping.

The diagram also highlights the checkout process, where customers can finalize their purchase by calculating the total price, securely processing payment, and receiving a confirmation of their transaction. This visualization ensures transparency and efficiency throughout the shopping journey, enhancing the overall usability of the platform.

Once you’ve developed your use case diagrams, it’s essential to test and validate them to ensure they meet their objectives. Testing and validation are critical because they help identify any flaws or gaps in the diagrams before they are implemented. This process ensures that the use cases accurately represent the intended functionality and can handle real-world scenarios effectively. Below we break down the importance of each for you to have a better idea of how to conduct them.

Testing and validating use case diagrams is a crucial step following their development to ensure they meet their intended purposes. To start, it is essential to create comprehensive test cases that cover various scenarios, including the primary flow and any alternate paths or exceptions. 

Each use case should be examined under different conditions to verify its robustness and functionality. These scenarios should encompass a range of user interactions, error situations, and edge cases to thoroughly evaluate the use case’s effectiveness.

Additionally, establishing clear validation criteria is key to assessing the adequacy and accuracy of each use case. These criteria act as benchmarks to confirm that all necessary functionalities are present and operational. Validation criteria might include ensuring that the system responds correctly to user inputs, handles errors smoothly, and meets performance standards. 

It is also important to validate the use cases under different conditions to ensure consistent behavior across various scenarios. This might involve testing the system’s responsiveness under varying loads, checking compatibility with different devices or browsers, and assessing its resilience to unexpected inputs or environmental factors.

In conclusion, use case diagrams serves as an invaluable tool in software development, offering a structured approach to capturing functional requirements and guiding the development process. By providing descriptive narratives, visual representations, structuring scenarios, defining requirements, facilitating communication, and driving implementation, use cases play a crucial role in ensuring the successful development of robust systems. Testing and validating use cases are essential steps to guarantee that they accurately represent system functionality and can effectively handle real-world scenarios, ultimately contributing to the overall success of software projects.

Related Content

• Prototyping tools
• Interaction design tools
• UI design software
• Collaboration
• Requirements
• UI libraries
• All features
• Web design software
• Mobile app design software
• VR & AR design
• All integrations
• Import from Sketch
• Start from Adobe
• Wireframe tool
• Mockup tool
• Login to account
• Download Justinmind
• Help Center
• Design templates
• Customer Stories
• Brand Assets
• Privacy Policy
• Terms of use
• Download Free

Make a diagram in 3 steps.

UML Use Case Examples

What is a Use Case Diagram?

When a system software is in the developing phase, then for making it perform efficiently, the developers specify different use cases to check the possible behavior of the software in different cases or situations. This diagram shows us the possible behavior of how the software will perform.

The benefit of using the use case diagram is that we develop the system with the user in mind. It is the best way to meet the requirements of the end-user. The use case diagram illustrates the relationship between the multiple use-cases, actors, and systems. The best practice is that the use case diagram should be small and crispy. The use case diagram specifies how a system will perform, which is why it shows only the functionality of the system.

Use Case Diagram Notation

In this section, we will talk about the four basic types of use case diagram notations. They are as follows.

The use cases tell us about how the system will perform in different cases. These use cases are made by keeping in mind what a user wants from the system. Depending on the user's wants and needs, the use cases are made, and then the system is developed and tested according to these cases.

An actor is simply the end-user. That can be anyone, a human, an organization, a machine, or anything. The actors are placed with different cases on the diagram to illustrate how the user will interact with the system.

The subsystems in the UML are the different fixed systems that behave independently in a system. They are used in UML diagrams to represent different units in the system.

Relationships in the Use Case Diagram

They show the relationship between the model elements. It shows the behavior between model elements.

Source: www.ibm.com

All-in-One Diagram Software

• Superior file compatibility: Import and export drawings to various file formats, such as Visio
• Cross-platform supported (Windows, Mac, Linux, Web)

Use Case Diagram Examples of Common Scenarios

This section will present multiple practical use case diagram examples that will clear out the mind and concept.

1. Use Case Diagram for ATM

The Automatic Teller Machine (ATM) is the banking subsystem that enables the end-users to interact with the multiple functionalities of the bank like transactions, depositing, etc.

In this diagram, we have two actors, the customer, and the technician. The customer needs to check the balance, withdraw cash, deposit funds, and transfer funds. All these functionalities are the use cases. The technician repairs and maintains the ATM so that customers have no complaints. These are the use-cases too.

There is a relationship between the bank and the ATM because the user will only do such acts when the bank authenticates them.

2. Use Case Diagram for Website

In the above diagram, the site user and the webmaster are the actors of the UML diagram. The site user wants to search for documents, browse documents, and view events. These are the use cases or the functionality the user wants to do. The download and preview documents are the use cases too, and they are in relation to each other based on user requirements.

The webmaster upload documents, post new events to the homepage and add a user and these use cases are in relation with the managed folders and add company but still based on what the actor wants.

3. Use Case Diagram for Library Management System

In the diagram, we can see the multiple actors: staff and the student, librarian, and library database. And we have dozens of use cases like authenticating, reserve a book, renewing a book, paying a fine, etc. Some use cases are related to each other, like invalid renewal and renewing a book, registering a new user, getting a library card ID, etc.

The librarian also does multiple tasks. The thing to notice here is that one actor is a machine that is the library database. As mentioned above, the actor can be anyone, either a human and a machine.

4. Use Case Diagram for Online Shopping

In this illustration, we have an online shopping subsystem. It has use cases like view items, make a purchase, checkout, and client register. Then we have multiple actors like the registered user, web customer, and new customer. These actors are related to each other. The use cases are also in a relationship.

The actors PayPal and credit payment service are the organizations interacting with the subsystem with different use-cases.

5. Use Case Diagram for Hospital Management System

Source: www.uml-diagrams.org

It is the use case diagram of the hospital management system. In this diagram, the receptionist is the leading actor. The receptionist interacts with multiple use cases like a scheduled patient appointment, patient admission in the hospital, etc. These cases are related to each other.

6. Use Case Diagram for Car Rental System

It is an illustration of the car rental system use-case UML. Here, the insurance company is the actor that is the organization interacting with bill payment use-case and the customer is also an actor. Through the customer, the insurance company is also interacting with other use-cases of the car rental system. The employee and the manager are also the actors in this system.

7. Use Case Diagram for Student Registration System

Source: www.researchgate.net

It is the student registration system use-case UML diagram. Students, professors, and administrators are the actors. The system also has dozens of use-cases.

8. Use Case Diagram for Airline Reservation System

This system is the subsystem of the airline reservation system. The actors are passengers, admins, and the banks that are the organizations. The passenger is concerned with multiple use cases like login, check for availability, book ticket, etc. The book ticket use case is in relation to the choose seat use case. The admin cancels tickets, updates flight schedules. The bank sees the payment use cases.

Click the video below to learn more about how to create UML Modeling and EdrawMax .

Use EdrawMax for Use Case Diagram Creation

Describing your system with a use case diagram before developing is essential in itself. It helps you to understand what the user needs. It helps you in making system functions more feasible. The best thing is that the use cases are visible. It helps you in testing and improving the software quickly. The use case diagram helps you to make your product user-friendly.

You can use EdrawMax to make a use case diagram. EdrawMax is the best diagram-making software that helps you to make any diagram efficiently. The software contains all the packages and libraries that will suffice you in your diagram-making.

EdrawMax allows you to import your templates or use pre-generated examples to make your production faster. You are allowed to export your project to any site. The software is free to use for the preliminary work, but you have to go for the pricing options for premium features.