case study examples for use case diagram

We use essential cookies to make Venngage work. By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

Manage Cookies

Cookies and similar technologies collect certain information about how you’re using our website. Some of them are essential, and without them you wouldn’t be able to use Venngage. But others are optional, and you get to choose whether we use them or not.

Strictly Necessary Cookies

These cookies are always on, as they’re essential for making Venngage work, and making it safe. Without these cookies, services you’ve asked for can’t be provided.

Show cookie providers

• Google Login

Functionality Cookies

These cookies help us provide enhanced functionality and personalisation, and remember your settings. They may be set by us or by third party providers.

Performance Cookies

These cookies help us analyze how many people are using Venngage, where they come from and how they're using it. If you opt out of these cookies, we can’t get feedback to make Venngage better for you and all our users.

• Google Analytics

Targeting Cookies

These cookies are set by our advertising partners to track your activity and show you relevant Venngage ads on other sites as you browse the internet.

• Google Tag Manager
• Infographics
• Daily Infographics
• Popular Templates
• Accessibility
• Graphic Design
• Graphs and Charts
• Data Visualization
• Human Resources
• Beginner Guides

Blog Graphic Design 10 Use Case Diagram Examples (and How to Create Them)

10 Use Case Diagram Examples (and How to Create Them)

Written by: Letícia Fonseca Feb 15, 2022

Use case diagrams are a great tool that can help businesses and developers alike to design processes and systems.

By capturing requirements and expectations from a user’s point of view, they ensure the development of correct and efficient systems that will properly serve a user’s goals.

In this article, we will define what a use case diagram is and provide you with different use case diagram examples.

You can create your own use case diagrams using Venngage’s  Diagram Maker  and use case diagram templates . No design experience is required!

Click to jump ahead:

What is a use case diagram?

• 5 Use case diagram examples and templates that you can use

What are the benefits of a use case diagram?

Types of use case diagrams, what are the elements of a uml use case diagram, faqs about use case diagrams.

A use case diagram is a visual representation of the different ways and possible scenarios of using a system. It illustrates how a user will perform actions and interact with a particular system, such as a website or an app.

For example, this use case diagram depicts the different functions of a banking system for customers:

In Unified Modeling Language (UML), systems are presented at different levels of detail to show a specific perspective in the system’s design. Use case diagrams are considered UML diagrams.

UML diagrams define and organize the high-level functions and scope of a system. By modeling the basic flow of events in a use case, they help identify the goals that you need to achieve with every system-user interaction.

5 Use case diagram examples and templates that you can use:

Here are some use case diagram templates and examples to guide your diagram creation process:

Retail use case diagram

This use case diagram example depicts the internal functions and employee interactions within a retail system.

It features basic system functions represented by color-coordinated boxes to signify use cases based on the user’s role. A use case diagram like this can be of great use to retail stores with B2C e-commerce systems.

Design a use case or UML diagram that reflects your brand with Venngage’s My Brand Kit feature. 

Add your website when prompted and the editor automatically imports all your brand assets, including your logo, colors, and fonts.

Restaurant use case diagram

In this example, a restaurant’s daily operations serve as the system, the staff represent the actors, and their tasks are the use cases.

This use case diagram can be particularly helpful to restaurants or fast-food chains in terms of systemizing routine processes and presenting day-to-day activities to employees in a simpler and more orderly way.

Travel use case diagram

Here is a use case diagram that maps out how different types of users can engage with a travel booking website or application.

This comprehensive template includes extended use cases marked by dotted lines and arrows instead of simple lines. It can be scaled down or up for hotels, airlines, and other travel reservation systems.

Banking use case diagram

Designed for automated teller machine (ATM) systems, this use case diagram portrays different types of transactions as use cases.

As this example is very simple and contains only essential elements, it can be adapted for other banking systems like branch banking or online banking.

Consumer electronics store use case diagram

Last but not least, this use case diagram example illustrates how sales and management teams can use a retail system to carry out tasks.

It can be applied to retail systems for consumer electronics and home appliances, fast-moving consumer goods, and other retail sectors.

Ready to master use case diagrams? Check out our blog for everything you need to know and more use case diagram examples for your inspiration.

Use case diagrams can aid your development process with the following benefits:

• Guiding development:  Use case diagrams can help establish the cost and complexity of your system. It does so by specifying which functions become requirements that will make it to the development stage.
• User-driven approach:  Use case diagrams are written in natural language, which helps users easily understand them. Additionally, they provide businesses an excellent way to communicate with customers. Here is a use case diagram example that shows the basic transactional path of a banking customer:

• Simplifying solutions:  By breaking down solutions into practical functions or features, use case diagrams can decrease the complexity of the problem that your system is trying to solve.
• Tracking progress:  Use case diagrams can be used to monitor which use cases have been implemented, tested, and delivered and help you identify which functions work and which ones don’t.

Create use case diagrams that are easy to understand with Venngage’s extensive icon library. We offer 40,000+ icons, including diverse people icons, so your diagrams can reflect your users more accurately.

Double-click an icon in your chosen template, and choose from the options in the menu. 

There are many different  types of diagrams  that can be used for designing and representing systems and processes. As for UML use case diagrams, they are classified into two types: behavioral and structural UML diagrams.

Behavioral UML diagrams

Behavioral UML diagrams provide a standard way to visualize the design and behavior of a system. Under them are 7 other types of diagrams which are:

• Activity diagrams
• State machine diagrams
• Sequence diagrams
• Communication diagrams
• Interaction overview diagrams
• Timing diagrams
• Use case diagrams

As an example, this use case diagram portrays how an ATM system will behave or react when a customer or administrator performs an action.

Structural UML diagrams

Structural UML diagrams on the other hand focus on depicting the concepts involved in a system and how they relate to each other. There are also 7 types of structural UML diagrams:

• Class Diagram
• Component Diagram
• Deployment Diagram
• Object Diagram
• Package Diagram
• Profile Diagram
• Composite Structure Diagram

Use case diagrams contain a combination of different elements and specialized symbols and connectors. Whether you want your use case diagram to be simple or in-depth, it should include the following basic components:

• Actors  – An actor is anyone who performs an action using your system. Actors or users can be a person, an organization, or an external system. Actors are represented by stick figures in a use case diagram. In this example, the functions of a system are modeled for two types of actors: persons and organizations.

• System  – The system scope covers a sequence of actions and interactions between users and the system. To depict the system boundary, system boundary boxes are used to signify that a use case is within the scope of the system.
• Use cases  – Use cases are the different uses or applications that your system can offer users. Horizontally shaped ovals are used to symbolize use cases while lines are drawn to connect the user to the use case. Here is an example to illustrate the relationship between users and use cases:

• Goals  – The goal is the end result of a use case. An effective use case diagram should describe the activities involved in reaching the goals behind each use case.

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

Use case diagrams describe the relationship between the users, the system, and its use cases. They do not need to go into a lot of detail and explain how the system operates internally. Here is a guide on what to include and what not to include in your use case diagram:

What to include:

• Who is using the system
• How the user will use the system
• What the user’s goal is
• What steps the user takes to accomplish a task
• How the system responds to a particular action

What not to include:

• The order in which steps are performed
• Details about user interfaces
• Programming language

When to apply use case diagrams

Here are some situations where applying use case diagrams can be particularly useful:

Early stages of system development:

• Gather and visualize requirements:  Capture the needs and goals of different user groups and how the system interacts with them.
• Define system scope:  Ensure you’re building the right features and functions based on user needs.
• Identify potential issues:  Spot inconsistencies or missing functionalities early on in the development process.

Communication and collaboration:

• Explain system functionality to stakeholders:  Offer a clear and concise visual representation of what the system does and how it works.
• Facilitate discussions and feedback:  Use the diagram as a starting point for discussions and encourage user input into the design process.
• Align teams on system goals:  Ensure everyone involved has a shared understanding of the user experience and system objectives.

Testing and documentation:

• Derive test cases:  Use the diagram to identify different use cases and scenarios to test the system functionality.
• Document system behavior:  Provide a clear and easily understandable reference for future maintenance and updates.
• Support ongoing communication:  Explain complex system features to new team members or users.

Beyond these situations, consider using use case diagrams when:

• You want to focus on the  “what” and “why”  instead of the technical details.
• You need to deal with  multiple user types  with different needs and functionalities.
• You want to  increase understanding and agreement  among stakeholders.

How do you write a use case diagram?

Writing a use case diagram involves deconstructing processes in order to reveal a basic overview of your system. Here are some steps that you can follow:

Step 1:  Identify the actors (users) who are going to be engaging with your system. Categorize each type of user based on their roles.

Step 2:  Pick one type of user and list what actions they would take using the system. Each action becomes a use case.

Step 3:  Create a goal for every use case. Identify what is required from the system to achieve these goals.

Step 4:  Structure the use cases. Include in the description for each use case the basic course of events that will happen when a user performs a certain action. It should describe what the user does and how the system responds.

Step 5:  Take into consideration alternate courses of events and add them to extend the use case.

Step 6:  Repeat steps 2-5 to create a use case diagram for each type of user.

What software is used to create a use case diagram?

There are various tools and software available for creating a use case diagram. For starters, you can try Microsoft Visio which is a diagramming and vector graphics application that is part of the Microsoft Office family.

You can also go for web-based software if you don’t want the hassle of downloading, installing, and updating programs. Venngage’s diagram features include pre-made use case diagram templates that you can customize for your business and development needs.

Don’t guess, visualize: Use case diagrams map how you gain from this system

Creating a use case diagram can help you illustrate how your system can fulfill the needs and goals of your users. Make sure to use Venngage’s  diagram maker  to create a successful use case diagram for your next project.

Discover popular designs

Infographic maker

Brochure maker

White paper online

Newsletter creator

Flyer maker

Timeline maker

Letterhead maker

Mind map maker

Ebook maker

• System Design Tutorial
• What is System Design
• System Design Life Cycle
• High Level Design HLD
• Low Level Design LLD
• Design Patterns
• UML Diagrams
• System Design Interview Guide
• Crack System Design Round
• System Design Bootcamp
• System Design Interview Questions
• Microservices
• Scalability

Use Case Diagrams | Unified Modeling Language (UML)

• Class Diagram | Unified Modeling Language (UML)
• Unified Modeling Language (UML) Diagrams
• Activity Diagrams | Unified Modeling Language (UML)
• Collaboration Diagrams | Unified Modeling Language(UML)
• Behavioral Diagrams | Unified Modeling Language(UML)
• Object Diagrams | Unified Modeling Language (UML)
• Sequence Diagrams | Unified Modeling Language (UML)
• Class Diagrams vs Object Diagrams | Unified Modeling Language(UML)
• Deployment Diagram in Unified Modeling Language(UML)
• Structural Diagrams | Unified Modeling Language(UML)
• State Machine Diagrams | Unified Modeling Language (UML)
• Conceptual Model of the Unified Modeling Language (UML)
• Which UML Diagrams are mostly used?
• Introduction of Unified Database Language (UDL)
• Use Case Diagram for Library Management System
• Class Diagram for School Management System
• Class diagram for Mall Management system
• Class diagram for Hotel management system
• ER diagram of Bank Management System

A Use Case Diagram is a vital tool in system design, it provides a visual representation of how users interact with a system. It serves as a blueprint for understanding the functional requirements of a system from a user’s perspective, aiding in the communication between stakeholders and guiding the development process.

Important Topics for the Use Case Diagrams

• What is a Use Case Diagram in UML?
• Use Case Diagram Notations
• Use Case Diagram Relationships
• How to draw a Use Case diagram in UML?
• What are common Use Case Diagram Tools and Platforms?
• What are Common Mistakes and Pitfalls while making Use Case Diagram?
• What can be Use Case Diagram Best Practices?
• What are the Purpose and Benefits of Use Case Diagrams?

1. What is a Use Case Diagram in UML?

A Use Case Diagram is a type of Unified Modeling Language (UML) diagram that represents the interaction between actors (users or external systems) and a system under consideration to accomplish specific goals. It provides a high-level view of the system’s functionality by illustrating the various ways users can interact with it.

2. Use Case Diagram Notations

UML notations provide a visual language that enables software developers, designers, and other stakeholders to communicate and document system designs, architectures, and behaviors in a consistent and understandable manner.

1.1. Actors

Actors are external entities that interact with the system. These can include users, other systems, or hardware devices. In the context of a Use Case Diagram, actors initiate use cases and receive the outcomes. Proper identification and understanding of actors are crucial for accurately modeling system behavior.

1.2. Use Cases

Use cases are like scenes in the play. They represent specific things your system can do. In the online shopping system, examples of use cases could be “Place Order,” “Track Delivery,” or “Update Product Information”. Use cases are represented by ovals.

1.3. System Boundary

The system boundary is a visual representation of the scope or limits of the system you are modeling. It defines what is inside the system and what is outside. The boundary helps to establish a clear distinction between the elements that are part of the system and those that are external to it. The system boundary is typically represented by a rectangular box that surrounds all the use cases of the system.

Purpose of System Boundary:

• Scope Definition: It clearly outlines the boundaries of the system, indicating which components are internal to the system and which are external actors or entities interacting with the system.
• Focus on Relevance: By delineating the system’s scope, the diagram can focus on illustrating the essential functionalities provided by the system without unnecessary details about external entities.

3. Use Case Diagram Relationships

In a Use Case Diagram, relationships play a crucial role in depicting the interactions between actors and use cases. These relationships provide a comprehensive view of the system’s functionality and its various scenarios. Let’s delve into the key types of relationships and explore examples to illustrate their usage.

3.1. Association Relationship

The Association Relationship represents a communication or interaction between an actor and a use case. It is depicted by a line connecting the actor to the use case. This relationship signifies that the actor is involved in the functionality described by the use case.

Example: Online Banking System

• Actor: Customer
• Use Case: Transfer Funds
• Association: A line connecting the “Customer” actor to the “Transfer Funds” use case, indicating the customer’s involvement in the funds transfer process.

3.2. Include Relationship

The Include Relationship indicates that a use case includes the functionality of another use case. It is denoted by a dashed arrow pointing from the including use case to the included use case. This relationship promotes modular and reusable design.

Example: Social Media Posting

• Use Cases: Compose Post, Add Image
• Include Relationship: The “Compose Post” use case includes the functionality of “Add Image.” Therefore, composing a post includes the action of adding an image.

3.3. Extend Relationship

The Extend Relationship illustrates that a use case can be extended by another use case under specific conditions. It is represented by a dashed arrow with the keyword “extend.” This relationship is useful for handling optional or exceptional behavior.

Example: Flight Booking System

• Use Cases: Book Flight, Select Seat
• Extend Relationship: The “Select Seat” use case may extend the “Book Flight” use case when the user wants to choose a specific seat, but it is an optional step.

3.4. Generalization Relationship

The Generalization Relationship establishes an “is-a” connection between two use cases, indicating that one use case is a specialized version of another. It is represented by an arrow pointing from the specialized use case to the general use case.

Example: Vehicle Rental System

• Use Cases: Rent Car, Rent Bike
• Generalization Relationship: Both “Rent Car” and “Rent Bike” are specialized versions of the general use case “Rent Vehicle.”

4. How to draw a Use Case diagram in UML?

Step 1: identify actors.

Determine who or what interacts with the system. These are your actors. They can be users, other systems, or external entities.

Step 2: Identify Use Cases

Identify the main functionalities or actions the system must perform. These are your use cases. Each use case should represent a specific piece of functionality.

Step 3: Connect Actors and Use Cases

Draw lines (associations) between actors and the use cases they are involved in. This represents the interactions between actors and the system.

Step 4: Add System Boundary

Draw a box around the actors and use cases to represent the system boundary. This defines the scope of your system.

Step 5: Define Relationships

If certain use cases are related or if one use case is an extension of another, you can indicate these relationships with appropriate notations.

Step 6: Review and Refine

Step back and review your diagram. Ensure that it accurately represents the interactions and relationships in your system. Refine as needed.

Step 7: Validate

Share your use case diagram with stakeholders and gather feedback. Ensure that it aligns with their understanding of the system’s functionality.

Let’s understand how to draw a Use Case diagram with the help of an Online Shopping System:

2. use cases:.

• Browse Products
• Add to Cart
• Manage Inventory (Admin)

3. Relations:

• The Customer can browse products, add to the cart, and complete the checkout.
• The Admin can manage the inventory.

Below is the usecase diagram of an Online Shopping System:

5. What are common Use Case Diagram Tools and Platforms?

Several tools and platforms are available to create and design Use Case Diagrams. These tools offer features that simplify the diagram creation process, facilitate collaboration among team members, and enhance overall efficiency. Here are some popular Use Case Diagram tools and platforms:

6.1. Lucidchart

• Cloud-based collaborative platform.
• Intuitive drag-and-drop interface.
• Real-time collaboration and commenting.
• Templates for various diagram types.
• Integration with other tools like Jira and Confluence.

6.2. draw.io

• Free, open-source diagramming tool.
• Works offline and can be integrated with Google Drive, Dropbox, and others.
• Offers a wide range of diagram types, including Use Case Diagrams.
• Customizable shapes and themes.

6.3. Microsoft Visio

• Part of the Microsoft Office suite.
• Supports various diagram types, including Use Case Diagrams.
• Integration with Microsoft 365 for collaborative editing.
• Extensive shape libraries and templates.

6.4. SmartDraw

• User-friendly diagramming tool.
• Templates for different types of diagrams, including Use Case Diagrams.
• Integration with Microsoft Office and Google Workspace.
• Auto-formatting and alignment features.

6.5. PlantUML

• Open-source tool for creating UML diagrams.
• Text-based syntax for diagram specification.
• Integrates with various text editors and IDEs.
• Supports collaborative work using version control systems.

6. What are Common Mistakes and Pitfalls while making Use Case Diagram?

Avoiding common mistakes ensures the accuracy and effectiveness of the Use Case Diagram. Here are key points for each mistake:

6.1. Overcomplication:

• Mistake: Including excessive detail in the diagram.
• Impact: Confuses stakeholders and complicates understanding.
• Prevention: Focus on essential use cases and maintain an appropriate level of abstraction.

6.3. Ambiguous Relationships:

• Mistake: Unclear relationships between actors and use cases.
• Impact: Causes misinterpretation of system interactions.
• Prevention: Clearly define and label relationships with proper notation.

6.3. Inconsistent Naming Conventions:

• Mistake: Inconsistent naming of actors and use cases.
• Impact: Causes confusion and hinders communication.
• Prevention: Establish and adhere to a consistent naming convention.

6.4. Misuse of Generalization:

• Mistake: Incorrect use of generalization relationships.
• Impact: Misrepresentation of the “is-a” relationship between use cases or actors.
• Prevention: Ensure accurate usage to represent specialization relationships.

6.5. Overlooking System Boundaries:

• Mistake: Not clearly defining the system boundary.
• Impact: Challenges understanding of the system’s scope.
• Prevention: Clearly enclose relevant actors and use cases within a system boundary.

6.6. Lack of Iteration:

• Mistake: Treating the diagram as a static artifact.
• Impact: May become outdated and not reflect the current state of the system.
• Prevention: Use an iterative approach, updating the diagram as the system evolves.

7. What can be Use Case Diagram Best Practices?

Creating effective and clear Use Case Diagrams is crucial for communicating system functionality and interactions. Here are some best practices to follow:

7.1 Keep it Simple:

• Focus on High-Level Functionality: Avoid unnecessary details and concentrate on representing the system’s primary functionalities.
• Use Concise Language: Use clear and concise language for use case and actor names to enhance readability.

7.2 Consistency:

• Naming Conventions: Maintain a consistent naming convention for use cases and actors throughout the diagram. This promotes clarity and avoids confusion.
• Formatting Consistency: Keep a consistent format for elements like ovals (use cases), stick figures (actors), and lines to maintain a professional look.

7.3. Organize and Align:

• Logical Grouping: Organize use cases into logical groups to represent different modules or subsystems within the system.
• Alignment: Maintain proper alignment of elements to make the diagram visually appealing and easy to follow.

7.4. Use Proper Notation:

• Consistent Symbols: Adhere to standard symbols for actors (stick figures), use cases (ovals), and relationships to ensure understanding.
• Proper Line Types: Clearly distinguish between association, include, extend, and generalization relationships using appropriate line types.

7.5. Review and Iterate:

• Feedback Loop: Regularly review the diagram with stakeholders to ensure accuracy and completeness.
• Iterative Process: Use an iterative process, updating the diagram as the system evolves or more information becomes available.

By following these best practices, you can create Use Case Diagrams that effectively communicate the essential aspects of a system, fostering a shared understanding among stakeholders and facilitating the development process.

8. What are the Purpose and Benefits of Use Case Diagrams?

The Use Case Diagram offers numerous benefits throughout the system development process. Here are some key advantages of using Use Case Diagrams:

• Use Case Diagrams provide a visual representation of the system’s functionalities and interactions with external entities.
• This visualization helps stakeholders, including non-technical ones, to understand the system’s high-level behavior.
• Use Case Diagrams serve as a powerful communication tool, facilitating discussions between stakeholders, developers, and designers.
• They provide a common language for discussing system requirements, ensuring a shared understanding among diverse team members.
• During the requirements analysis phase, Use Case Diagrams help in identifying, clarifying, and documenting user requirements.
• They capture the various ways users interact with the system, aiding in a comprehensive understanding of system functionality.
• Use Case Diagrams center around user goals and scenarios, emphasizing the perspective of external entities (actors).
• This focus on user interactions ensures that the system is designed to meet user needs and expectations.
• In the system design phase, Use Case Diagrams aid in designing how users (actors) will interact with the system.
• They contribute to the planning of the user interface and help in organizing system functionalities.
• Use Case Diagrams are valuable for deriving test cases and validating system behavior.
• Testers can use the diagrams to ensure that all possible scenarios, including alternative and exceptional paths, are considered during testing.

9. Conclusion

In conclusion, a Use Case Diagram in UML serves as a powerful tool for capturing and visualizing the functional requirements and interactions within a system. By representing actors, use cases, and their relationships in a clear and concise manner, this diagram provides a high-level overview of the system’s behavior.

Please Login to comment...

Similar reads.

• Geeks Premier League 2023
• Geeks Premier League
• System Design

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

Filter by Keywords

Product Management

How to create user-focused use cases for ideal success scenarios [with examples].

Engineering Team

December 30, 2023

Are you steering a project, deciphering intricate business processes, or engineering complex software solutions? If so, you’re well aware that success hinges on clarity and precision. Good news! Use cases may spare you and your clients a great deal of trouble.

Imagine you’re constructing a building. Blueprints guide you, outlining each room’s purpose and layout. This is exactly what a use case is: a blueprint to guide system requirements and resulting project operations. It helps map out processes across user interactions, helping you build a system tailored to user goals and needs. 🏗️

A stitch in time saves nine, and similarly, mastering use cases now can save you countless hours later. In this practical guide, we’ll explain:

• The significance of a use case-driven approach in software development
• Steps to write a use case for multiple scenarios

Benefits of use cases in business processes

Step 1: come up with the title and description, step 2: identify the actors, step 3: identify the actors’ goal, step 4: capture stakeholders and their interests, step 5: specify pre-conditions or assumptions, step 6: outline basic flow, step 7: determine exceptions or error conditions, step 8: include extensions or variations to how the system functions, step 9: consider alternative flows, create and manage your use cases in clickup docs, try writing use cases with ai, use case #1: online shopping wishlist, use case #2: travel itinerary management.

What Is a Use Case, and What Purpose Does It Serve?

Use cases are indispensable for understanding user-specific interactions and narratives (or user stories) to create the intended design for a system.

In technical terms, a use case is a detailed description that outlines how a user will interact with an IT solution to achieve a specific goal. It maps out the steps they take , with a clear beginning, middle, and end.

If you’re new to use cases, you’re probably wondering why you should care about it. The truth is that every software development process carries the burden of user-focused project planning. It’s critical to understand the service or system requirements beforehand so that your end product works perfectly and is profitable.

This is where a use case comes in, helping you visualize user interactions from start to finish and pinpoint any hiccups along the way . Think of it as a walkthrough in a strategic game where every move is crucial. Your input, the system’s response, specific processes, and the final outcome are all explicitly stated, leaving no room for ambiguity in decisions.

The idea here is to help project managers, business analysts, and software developers align themselves on what the end user desires in a software application or a system , taking the guesswork out of the picture. The result? Smarter decisions on:

• Features to prioritize
• Design scope
• Bugs to fix

Tip: Need a quick start? Use the ClickUp User Story Mapping Template to initiate use case mapping right away! Its built-in infinite Whiteboard helps you track and prioritize user stories within minutes.

Use cases offer several benefits in developing and managing software systems and projects . Here are seven key advantages for various business stakeholders:

• Clarity into specific interactions : Use cases provide a clear understanding of how users interact with a system, helping define and document functional requirements
• Focused communication : Use cases serve as a bridge between business stakeholders , aligning developers, designers, project managers, and clients
• Identification of how a system behaves : They help identify and document various ways users interact with the system. This includes both normal and exceptional scenarios, providing a comprehensive view of the system’s expected behavior
• Project planning : Use cases help in planning by breaking down the desired functionalities into manageable units addressing specific system goals
• Flexibility : They provide a flexible framework that can accommodate modifications (alternative flows) or additions without disrupting the overall system flow
• Documentation and training : Use cases serve as valuable workflow documentation for future reference. They provide insights that can be useful for training new development team members
• Risk identification : By exploring various success and failure scenarios, use cases assist in identifying potential risks and challenges early in the development process

What to Include in a Project’s Use Case: With Practical Steps

Use cases can include a number of elements depending on the scale and complexity of the system you’re building. Here are some of the most significant options:

• Title and description
• Actors (users)
• Stakeholders
• Pre-conditions
• Exception to the basic flow
• Variations or what-if scenarios
• Alternative flows

These points can be better explained when we explore the practical side of things. Refer to the sections below to understand how to include these elements and distill complex use case scenarios into actionable steps .

Any use case study must have an engaging title. Keep it concise, specific, and indicative of the use case’s purpose. For instance, the title Optimizing Online Checkout: A Use Case for E-Commerce Conversion Enhancement immediately conveys the focus and scope.

Next, your case description should set the context concisely, pinpointing the use case actor or user, the system in question, and the ultimate goal. Here’s an example: This use case outlines the steps taken by an online shopper to complete a purchase, highlighting the system’s response at each interaction to ensure a smooth transaction and reduce cart abandonment.

Keep your language sharp, directly addressing the innovative outcomes you seek.

These are not Hollywood stars but rather the key entities— individuals, groups, or even other systems —interacting with the system under scrutiny. Identifying these actors is akin to casting characters in a play; each has a role, a purpose, and a set of actions that contribute to the unfolding narrative. 🎭

Actors within a use case diagram can be categorized as either primary or secondary . A primary actor seeks the system’s assistance by themselves to achieve a specific goal. On the other hand, a secondary actor provides a service to the system as a direct result of the primary use case. The system initiates interaction with the secondary actor for information or completion of a goal.

Let’s say a user applies for a loan online, which makes them the primary actor. In response to the loan application, the system triggers another resource to calculate interest rates—that resource is the secondary actor.

If you’re still in the research phase and need help identifying the primary actor, you may want to document your findings through the ClickUp User Research Plan Template . Its built-in features help software and UX teams map out user behavior and resolve problems within apps, websites, or projects in an orderly manner. 

Whether an actor is buying a product, signing up for a newsletter, or using a website, their goal is the driving force behind their interaction with your services . It’s your job to understand these goals so you can design a system that helps them achieve them in the most efficient way possible.

Let’s consider a real-world example: if you’re running a retail website, a customer’s goal might be to purchase a product in minimal steps. This use case would require you to outline the steps customers need to take to complete that purchase, from selecting the item to finalizing the payment.

Use this ClickUp SMART Goal Action Plan Template to list out the goals of all identified actors and monitor how they’re addressed by your team.

It’s super vital to identify all the stakeholders and understand their interests to ensure your use case is effective. A stakeholder could be an end-user, a system administrator, or even external actors or systems interacting with your service. They all have unique needs and expectations. Here’s what you should do:

• List all possible stakeholders involved in the use case
• For each stakeholder, identify their interests or what they aim to gain from the use case. For instance, a potential Interest for an online shopper would be an Intuitive and efficient user experience
• Consider how the use case can be fulfilled without compromising the overall goals
• Regularly revisit this list as your project or product develops , ensuring new needs are accounted for

Stakeholder analysis can be a stressful job, especially when there are multiple use cases to monitor. We recommend using quality stakeholder mapping templates to structure the process. 

Pre-conditions set the stage for action, ensuring that all necessary conditions are in place before the use case is initiated. Think must-haves for your scenario to work—like having an internet connection for an online transaction or a user account for access to a members-only area. Imagine the scenario from the user’s perspective and identify and list these prerequisites clearly.

Here’s an illustration showing how pre-conditions are used to outline use cases and automate the workflow for a banking website:

This is the minimum viable product (MVP) scenario, the one where everything clicks, and your use case unfolds just as envisioned. No errors, no hiccups, just a straightforward path to a happy user.

Imagine a scenario where a customer purchases a book from an online store. The basic flow would be:

• The customer logs in to their account
• They search for a book by title, author, or genre
• The customer reviews the book and adds it to their cart
• They proceed to checkout, confirm shipping details, and select a payment method
• They review the order summary and place the order
• A confirmation email is sent to the customer

Each step here is supposed to be clear and necessary, guiding the user towards a satisfying transaction. Fall back on the ClickUp User Flow Template to design efficient use case pathways and share them with your team.

These exceptions represent scenarios where the standard process flow doesn’t apply. Think about what could go wrong and how your system should respond. You can:

• Consider realistic scenarios : Think about all the ways an operation might deviate or lead to failure scenarios. This could be due to technical issues, user errors, or unexpected circumstances
• Document each exception : Clearly describe each exception, including its cause, effect, and how your system should respond
• Prioritize exceptions : Rank exceptions based on their likelihood and impact on user experience

Think of these as what-if scenarios that keep your processes agile . Say if a customer abandons their shopping cart, what’s the next step? This perhaps calls for creating an extension that activates a follow-up email sequence or a special discount offer to re-engage them.

Use cases should adapt to real-world complexities, offering innovative solutions that maintain user engagement. It’s about anticipating the unexpected and scripting a response that turns challenges into opportunities.

Consider alternative courses if challenges or process deviations occur. Imagine you’re designing a use case for an online shopping cart system.

Main Success Scenario (MSS):

• The user adds items to the cart
• The user proceeds to checkout and confirms payment

What if an item is out of stock?

• The system notifies the user immediately
• The system recommends similar products

What if the payment is declined?

• Prompt the user to try a different payment method
• Offer to save the cart for later completion

What if network issues occur?

• Save the user’s progress automatically
• Inform the user and attempt to reconnect

For each what-if , develop an alternative path that guides your system to a successful outcome. 

How to Write Effective Use Cases with ClickUp

Now that we have a thorough knowledge of the process of developing use cases, let’s explore how to write one professionally with ClickUp . This all-in-one project management tool comes with abundant user documentation and use case writing features. Let’s break down the process to showcase just how effortless it can be.🌹

To kick off your business use case model in ClickUp, head to ClickUp Docs , the platform’s integrated solution for creating and storing all types of documents—from user manuals and test case definitions to technical requirements.

Starting fresh? Great, create a new doc. You can use one of ClickUp’s free flowcharting templates to create use case diagrams or case study templates to document user research. Everything will be accessible from a centralized location, making it easier to keep track of the best possible outcome scenario or develop alternative paths.

Invite members from product and marketing teams to work on your use case document in real time. You may want to create Folders to store multiple use cases for your project. The best part is that you can connect your Docs with other project tasks to ensure a smooth work experience.

Let’s dive into the fun stuff! In the Doc editor, just type /ai. Boom! The ClickUp AI modal appears, ready for action. Click on Write with AI to get the party started. Type in your use case topic and add relevant technical requirements to generate a professional-grade, well-structured use case presentation within seconds.

Even with the AI-generated use cases, you’re in control. You can:

• Insert the content elsewhere : Seamlessly insert the AI-generated content into your Doc. Or, just copy-paste and merge it with manually written use cases
• Edit inputs : If the narrative needs a personal touch, edit your prompt or topic to guide the AI in the direction you want
• Regenerate : Fancy a different twist? Explore varied responses from the AI with the same prompt
• Give AI more direction : Extend the conversation by providing additional prompts or directions and get more contextual responses 🤖

Besides generating text, ClickUp AI can also fix the grammar and tone of your existing documents and even summarize lengthy case studies to save you time.

Examples of Use Cases for Software Development Projects

Let’s dive into some business use case examples to better illustrate what they look like and how they can streamline your projects.

An e-commerce platform aims to introduce a wishlist feature that enhances the online shopping experience for users.

Actors : Online shoppers

Goals : Add items to a wishlist; view wishlist contents

Stakeholders : E-commerce platform, online shoppers, product vendors, marketing team, developers

Pre-conditions : User must be logged in and browsing available products

Basic flow :

• User logs into the e-commerce platform
• User browses available products
• User selects the option to add a product to their wishlist
• System adds the selected product to the user’s wishlist
• User can view and manage their wishlist at any time
• System provides personalized product recommendations based on wishlist items

Extensions/Variations: 

• Implement a notification system to alert users when wishlist items are on sale
• Allow users to share their wishlist with friends or family for gift suggestions

Exceptions/Error conditions:

• If a selected product is no longer available, notify the user and provide alternate courses
• In case of technical issues, ensure users can still browse and add items to their wishlist without disruptions

Alternative flow :

• User selects the option to view their existing wishlist
• System displays a list of items in the user’s wishlist
• User can remove items from the wishlist or proceed to purchase
• System updates the wishlist and provides relevant suggestions for additional items

A travel planning app wants to implement a feature for users to create and manage their travel itineraries.

Actors : Travelers, travel app

Goals : Create and edit travel itineraries; receive recommendations

Stakeholders : Travel app companies, travelers, local businesses, tourism boards, developers

Pre-conditions : User must be logged in and have a trip planned

• User logs in
• User selects the option to create a new travel itinerary
• User inputs trip details, including destinations and dates
• System generates an initial itinerary and suggests local attractions
• User can modify the itinerary and add custom activities
• System provides real-time updates and recommendations based on user preferences

Extensions/Variations :

• Integrate a weather forecast feature for each destination
• Allow users to share their itineraries with fellow travelers.

Exceptions/Error conditions :

• If a selected attraction is closed or unavailable during the planned date, notify the user and suggest alternatives
• In case of a connectivity issue, ensure users can still access and modify their itineraries offline
• User logs into the travel app
• The user chooses an existing route
• System displays the current itinerary, including booked accommodations and activities
• User can modify the itinerary, add new activities, or remove existing ones
• System updates the itinerary and adjusts recommendations accordingly

Closing the Case on Success

Whether you’re looking to fine-tune your business process or enhance customer experience, use case modeling is a great tool for visual problem-solvers. If you need an observable result quickly, rely on the strategic use case development tools within ClickUp to accelerate your project timelines and bring your business objectives to fruition. 🍉

Sign up to explore the free-to-use solution .

Questions? Comments? Visit our Help Center for support.

Receive the latest WriteClick Newsletter updates.

Thanks for subscribing to our blog!

Please enter a valid email

• Free training & 24-hour support
• Serious about security & privacy
• 99.99% uptime the last 12 months

• Get started Get started for free

Figma design

Design and prototype in one place

Collaborate with a digital whiteboard

Translate designs into code

Get the desktop, mobile, and font installer apps

See the latest features and releases

• Prototyping
• Design systems
• Wireframing
• Online whiteboard
• Team meetings
• Strategic planning
• Brainstorming
• Diagramming
• Product development
• Web development
• Design handoff
• Product managers

Organizations

Config 2024

Register to attend in person or online — June 26–27

Creator fund

Build and sell what you love

User groups

Join a local Friends of Figma group

Learn best practices at virtual events

Customer stories

Read about leading product teams

Stories about bringing new ideas to life

Get started

• Developer docs
• Best practices
• Reports & insights
• Resource library
• Help center

What is a use case? How to write one, examples, + template

Designing a product takes more than listing features and goals. Before the first smartphone came out, how would you describe the ways users interact with it? Calling it a cellphone you can browse the web on is a good start, but that doesn’t explain the complexity of its systems. To map out the ways users interact with a system, tool, or product, you need a use case.

Use cases are descriptions of the ways users interact with systems to accomplish tasks or reach goals. Mapping these interactions can improve early planning and ensure a smooth development cycle. To help you work them into project planning, we’ll define a use case, explain how to write one, and share examples.

What is a use case

A use case explains how users interact with a product or system. It outlines the flow of user inputs, establishing successful and failed paths to meeting goals. This allows product teams to better understand what a system does, how it performs, and why errors occur. You can write one out or diagram a use case model for visual thinkers.

Use cases vary in complexity depending on your audience or system. But across the board, your use case should identify a few key components. The most important ones include:

• Actor: anything exhibiting behavior that interacts with a system, such as a single user, a team, or another piece of software
• System: the product or service with defined functionality
• Goal: the purpose or objective users reach with a system’s features

Actors, systems, and goals build the foundation for a use case. When you begin tracking system interactions, a few new elements come into play:

• Stakeholder(s): someone with a stake or interest in a system’s performance
• Primary actor: the actor who initiates a system’s function to reach a goal
• Preconditions: underlying factors required for the use case to happen
• Triggers: events that begin a use case
• Basic flows: use cases where systems work as intended to reach a goal
• Alternate flows: different outcomes based on when and how a system veers off course

Types of use cases

Use cases come in two forms: business and system. A system use case is a detailed look at how users interact with each part of a system. It highlights how unique inputs and contexts cause the system to reach different outcomes. This level of detail highlights how a system’s individual functions work in any scenario.

Business use cases paint a more general picture of how a user might interact with your business to reach their goals. Instead of focusing on technical detail, it’s a cause-and-effect description of different inputs. For example, if you run a code debugging platform, your business use case explains how users enter their code and receive error notices.

Some teams like to write a business use case to outline a system’s processes before development. As developers begin their work, a manager will outline more technical system use cases to follow.

Use scenario vs. use case

Use cases show all the ways a system functions when trying to reach goals, but a scenario only depicts one example. In a scenario, the system can succeed or fail at reaching the user’s goals. Put simply, multiple use scenarios build a use case.

Use case vs. user story

Use cases depict how users interact with a system, and user stories describe features from the user’s perspective. As a result, user stories are much shorter than use cases, typically consisting of brief descriptions teams use as a jumping-off point in development. Additionally, use cases can assist multiple teams in an organization, while user stories help product teams build their tool.

Use case vs. test case

While a use case covers how users and system features work to reach goals, test cases verify if a single feature works correctly. Unlike use cases, test cases look at functionality in isolation.

For example, a test case might involve validating login functionality on an email platform, ensuring users can log in on any browser at any time after creating their account.

How to write a use case

Writing a use case sounds complex, but only requires understanding your system and its users. You can write a use case by following these six steps:

1. Describe your system

Start by describing your system, or the product or service you and your team will build. Focus your description on what your system does for users. In a business use case, you can keep this background general and explain what it accomplishes. For a system use case, give an under-the-hood description of how your product functions.

Define your system by asking:

• What form does it take: product, service, or software?
• What features does it offer?
• What goals can you accomplish with it?
• How does it meet those goals?
• What can you learn about the system from other documents like project charters ?

2. Identify the actors

Actors generally refer to users and customers but can apply to any outside force that engages with your system. Your actor needs well-defined behaviors explaining how and why actors use your system.

Identify actors by asking:

• Are they individuals, teams, hardware, or another system?
• Will primary and secondary actors share the same behavior?
• Will stakeholders take on the role of actors in your use case?

3. Define your actors’ goals

Use cases highlight the outcome actors want from a system. Remember to focus on your actors’ wants over the system’s capabilities to understand why users come to your system. In some cases, customers want to use systems for more than one objective. Listing each of these objectives creates a more robust use case.

4. Create a scenario

In a use case, scenarios are the sequence of actions customers take when using a system and the flow of effects from that interaction. Your basic flows cover scenarios where a system works as intended. A user approaches the system, enters the right inputs, and your system helps them reach their goals.

Start with these successful, basic flows to create a baseline. You can use process mapping techniques to identify potential issues in the next flows.

5. Consider alternate flows

After writing a successful scenario, write alternate flows that lead to different outcomes. Typically, alternate flows involve the misuse of a system that keeps actors from reaching their goals. However, you can also note internal errors that cause a system to break down or unintended ways systems can reach goals.

Alternate flows show how different actors use a system and succeed or fail. They give a more nuanced view of everything your system can do to help you troubleshoot.

6. Repeat steps 2–5 to compile your use case

With enough variation of actors, goals, and scenarios, you can show how your system functions. Compiling these flows together gives you a use case, which can improve development and inform other documents like project status reports .

With simple systems, you can change a few elements to see every potential outcome. However complex systems may have too many elements to see each outcome. In cases like this, you can focus on testing the most common interactions. You can also design systems to prevent untested com

Try Figma’s use case template

Ready to start brainstorming use cases? Try the Figma use case template to break down your systems and find new solutions.

Use case example

Assume you’re a product manager developing a mobile banking app for your company. Your platform needs to streamline user registration and account setup. Here’s a sample use case format based on this app:

Background information:

• System: a mobile banking app
• Primary actor: customers who want to open an account
• Secondary actor: underwriters and automated tools calculating interest rates and maximum principal balances
• Goals: save time on account registration and onboarding
• Stakeholders: the CEO and product VP of your company
• Preconditions: users download the app and meet account requirements
• Triggers: the user chooses to create a new account from the app
• Basic flow: Users download your app and choose to create a new account. The application collects information about the user’s other accounts and credit scores. From there, it automatically shares the accounts they qualify for and their interest rates. The user finds an account that suits their needs and registers.
• Alternate flow 1: Users enter their financial information and the app quickly generates account options. However, each account defaults to the highest interest rate their financial background allows. So, users abandon the app to find a lower rate.
• Alternate flow 2: The onboarding process works as intended, but the app faces compliance issues such as Know Your Customer (KYC) requirements. While the app can provide account options, extra compliance steps slow the process.
• Alternate flow 3: Because the app only looks at other accounts and credit scores, it can’t offer a full range of account options. For example, it can only offer credit cards and lines of credit. So, customers looking for mortgages have to go elsewhere.

Benefits of use cases

In the planning stage, use cases define your project scope, requirements, and roadmap. Teams can also discuss the best user outcomes and design a path to them. With alternate flows, you can also anticipate risks before they hurt a user’s experience. If that isn’t enough reason to pen one, here are a few other benefits of use cases:

• Explains value: Use cases explain a system’s features in plain terms. So, when pitching your plans to stakeholders, a use case makes your system easier to understand.
• Predicts costs: A use case outlines the complexity of a system. More complexity may come with additional features or safeguards. By learning how complex your system is, you can estimate development costs.
• Improves planning: Without a use case, designers and developers focus on what a system does, not how it does it. However, use cases help teams consider all the ways to implement features and safeguards.
• Shares alternative uses: Not all alternative flows in a system lead to failed outcomes. Mapping out different scenarios finds new solutions to old problems or expands your understanding of what a system can accomplish.

Perfect your use cases with FigJam

Use cases go beyond describing what your product can do. They give stakeholders and teams a clear picture of user interactions and successful outcomes. Whether adding a new feature, rapid prototyping , or redesigning a system, your planning should start with writing a use case.

The more insights into actors, interactions, and outcomes, the better—which is why it's important to collaborate on use cases with your team and stakeholders. A shared online whiteboard like FigJam streamlines collaboration between remote teams to help you build out comprehensive use cases. Our gallery of 300+ templates can bring teams together at any stage of development.

UML Use Case Diagram Examples

What are your diagramming needs.

Lucidchart is a diagramming solution for UML with deep integration with third-party apps. Make the diagram itself in Lucidchart, and create your use case scenario document with a program like Google Docs!

3 minute read

Want to make a Diagram of your own? Try Lucidchart. It's quick, easy, and completely free.

What is a use case diagram in UML?

Outline your use case diagram.

Use case scenario documents break down a process by describing the actors, the typical workflow, and the things that could go wrong, called extensions. When managing projects that use UML conventions, there can be a temptation to jump straight into the use case diagram, with stick figures, ovals, and lots of lines. But if you don’t know your goals and who’s involved, take a step back and write your goals down in prose. Alistair Cockburn is a leader in designing use case scenarios; visit his website to get inspired!

This is a brief example the process of withdrawing money from an ATM. The outline goes through each of the steps that are likely to occur in the process, including each of the errors that could likely occur. Outlining the process like this will help you to outline the process, making the act of diagramming your use case scenario easier than ever.

Diagramming is quick and easy with Lucidchart. Start a free trial today to start creating and collaborating.

Use case diagram examples in Lucidchart

Book publishing use case diagram example.

This use case diagram is a visual representation of the prose scenario shown above. Whether you’re an author, an agent, or a bookseller, inserting this diagram into your use case scenario can help your team publish the next big hit. Try our demo template for a book publishing use case diagram here.

Railway reservation use case diagram example

This customizable template can be adapted for any process where a customer is purchasing a service. With attractive color schemes, text that’s easy to read and edit, and a wide-ranging UML shape library, you’re ready to go! Jump right in and  try our demo template to get started.

Banking system use case diagram example

Modern banking systems need to have clear objectives. This diagram presents a high-level overview of some of the most fundamental goals a customer has with his or her bank—opening an account, checking a balance, and withdrawing money. If you like this template  try it out in Lucidchart for a banking system use case diagram here.

How to make a use case diagram

In Lucidchart, creating a use case diagram from scratch is surprisingly simple.

Create a use case scenario document to organize the process and all possible alternative extensions.

Open a blank Lucidchart document or start with a template and enable the UML shape library.

Select the shape you want and drag out symbols from the toolbox to the canvas

Then model the process flow by drawing lines between shapes while adding text.

Dive deeper into this guide on how to draw a use case diagram in UML for additional insight. It's easy to resize and style any element. You can even import SVG shapes and Visio files for a custom solution. If you'd like to learn more about UML, check out our What is UML tutorial.

Additional Resources

• What is an BPMN and how to create one
• How to Make a Synoptic Table in Excel
• How to Make a Synoptic Chart in PowerPoint
• How to Make a Synoptic Table in Word
• Examples and Templates for Synoptic Tables
• What is and how to create an ERD
• What is an process map and how to create one
• What is a Data Flow Diagram (DFD) and How to Create One
• How to Make a Synoptic Table
• PowerPoint Flowchart Template Guide
• What is an Value Stream Map (VSM) and how to create one
• Workflow diagram tutorial
• What is a Swimlane Diagram and Steps to Create One
• What is an Network Diagram and how to create one
• What is and how to create a decision tree
• P&ID Examples
• How to Draw a Use Case Diagram in UML

Lucidchart is a flexible tool for building use case scenarios in prose or in diagrams. There’s no need to install expensive, slow software when you can edit, perfect, and publish your use case scenarios and diagrams from your browser!

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.

Use Case Diagram Relationships Explained with Examples

Updated on: 13 December 2022

When it comes to drawing use case diagrams one area many struggles with is showing various relationships in use case diagrams. In fact many tend to confuse <<extend>>, <<include>> and generalization. This article will look into various use case diagram relationships in detail and explain them using examples. To get a deeper understanding of use cases, check out our use case diagram tutorial . If you want to draw them while learning you can use our tool to create use case diagrams .

There can be 5 relationship types in a use case diagram.

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

Let’s take a look at these relationships in detail.

Association Between Actor and Use Case

This one is straightforward and present in every use case diagram. Few things to note.

• An actor must be associated with at least one use case.
• An actor can be associated with multiple use cases.
• Multiple actors can be associated with a single use case.

Different ways association relationship appears in use case diagrams

Check out the use case diagram guidelines for other things to consider when adding an actor.

Generalization of an Actor

Generalization of an actor means that one actor can inherit the role of the other actor. The descendant inherits all the use cases of the ancestor. The descendant has one or more use cases that are specific to that role. Let’s expand the previous use case diagram to show the generalization of an actor.

A generalized actor in an use case diagram

Extend Relationship Between Two Use Cases

Many people confuse the extend relationship in use cases. As the name implies it extends the base use case and adds more functionality to the system. Here are a few things to consider when using the << extend >> relationship.

• The extending use case is dependent on the extended (base) use case . In the below diagram the “Calculate Bonus” use case doesn’t make much sense without the “Deposit Funds” use case.
• The extending use case is usually optional and can be triggered conditionally. In the diagram, you can see that the extending use case is triggered only for deposits over 10,000 or when the age is over 55.
• The extended (base) use case must be meaningful on its own . This means it should be independent and must not rely on the behavior of the extending use case.

Lets expand our current example to show the <<extend>> relationship.

Extend relationship in use case diagrams

Although extending use case is optional most of the time it is not a must. An extending use case can have non-optional behavior as well. This mostly happens when your modeling complex behaviors.

For example, in an accounting system, one use case might be “Add Account Ledger Entry”. This might have extending use cases “Add Tax Ledger Entry” and “Add Payment Ledger Entry”. These are not optional but depend on the account ledger entry. Also, they have their own specific behavior to be modeled as a separate use case.

Include Relationship Between Two Use Cases

Include relationship show that the behavior of the included use case is part of the including (base) use case. The main reason for this is to reuse common actions across multiple use cases. In some situations, this is done to simplify complex behaviors. Few things to consider when using the <<include>> relationship.

• The base use case is incomplete without the included use case.
• The included use case is mandatory and not optional.

Lest expand our banking system use case diagram to show include relationships as well.

Includes is usually used to model common behavior

For some further reading regarding the difference between extend and include relationships in use case diagrams check this StackOverflow link .

Generalization of a Use Case

This is similar to the generalization of an actor. The behavior of the ancestor is inherited by the descendant. This is used when there is common behavior between two use cases and also specialized behavior specific to each use case.

For example, in the previous banking example, there might be a use case called “Pay Bills”. This can be generalized to “Pay by Credit Card”, “Pay by Bank Balance” etc.

I hope you found this article about use case relationships helpful and useful. You can use our diagramming tool to easily create use case diagrams online . As always if you have any questions don’t hesitate to ask them in the comments section.

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

More Related Articles

Many thanks for this great tutorial. It is really very clear with good examples and explanation methodology and most probably one of the best UML Tutorial on the web. Hope to come across such kind of good tutorials again…

Great tutorial! It’s probably the best one I’ve read

Does an included use case have to be used everytime the base case is used?

yes it does. the included use case is always be used everytime the base use case used. it’s like when someone’s sneezing he always close his eyes. sneezing is the base use case and closing eyes is the included use case.

is it possible to make extensions within a use case itself.

Yes, “The same extending UseCase can extend more than one UseCase. Furthermore, an extending UseCase may itself be extended.” – UML 2.5.1 Specification.

Found it better than other tutorials…. explaining everything as part of the development process. Thanks, hope to see other tutorials on OOAD and other topics.

This tutorial helped me to understand the difference between include and extend. Keep it up bro. Good luck!

Question: There are two sub usecases in a genaralized one. If I want a include to be attached to which one do I attach it. The main Usecase or the sub usecase

Awesome article … well and clearly explained all the concepts in use case diagrams

why use <> in use case?

In Visual Modeling we model according to some standard. Every shape or sign has a meaning.To draw relationship between Use cases we use to express the type of relationship by mentioning relationship type within . It’s a standard.

Fantastic. This is the most succinct and precise explanation of use case and their relationships that I have ever come across. Thanks

I agree – the best tutorial explaining the relationships that it can truly be understood! Thanks!!

What is the difference between “Extend” and “Generalization”?

I was preparing for my CBAP exam and this post helped me understand the difference between Extend and Include. Thanks.

what is diference between use case and use case modeling

A use case is a functionality performed by an actor(primary,secondary or offstage) Use case modeling is a process of drawing use cases in some modeling languages e.g StarUml

Nice tutorial, very helpful. Thanks a lot 🙂

Awesome Tutorial. now i understood use-case-relationship……..

Super Tutorial….. very very helpful for me to learn about Use Case Diagram……Thank u very much and I have a grate proud about u as a Sri Lankan. Keep up.

not generalized but specialised

Good tutorial! Really helpful for me

Leave a comment Cancel reply

Please enter an answer in digits: one × 1 =

Download our all-new eBook for tips on 50 powerful Business Diagrams for Strategic Planning.

UML Use Case Diagram Examples

Here we provide some examples of UML use case diagrams .

Examples of business use case diagrams

Purpose : An example of a business use case diagram for airport check-in and security screening.

Summary : Business use cases are Individual Check-In, Group Check-In (for groups of tourists), Security Screening, etc. - representing business functions or processes taking place in an airport and serving needs of passengers.

Purpose : Two alternative examples of business use case diagram for a Restaurant - external and internal business views of a restaurant.

Summary : Several business actors having some needs and goals as related to the restaurant and business use cases expressing expectations of the actors from the business.

Examples of system use case diagrams

Purpose : Show that ticket vending machine allows commuters to buy tickets.

Summary : The ultimate goal of a Commuter in relation to our ticket vending machine is to buy a ticket. We have a single Purchase Ticket use case, as this vending machine is not providing any other services. Ticket vending machine is a subject of the example use case diagram. Commuter and Bank are our actors , both participating in the Purchase Ticket use case .

Purpose : Describe use cases that an automated teller machine (ATM) or the automatic banking machine (ABM) provides to the bank customers.

Summary : Customer uses a bank ATM to check balances of his/her bank accounts, deposit funds, withdraw cash and/or transfer funds (use cases). ATM Technician provides maintenance and repairs to the ATM.

Purpose : An example of use cases for a Point of Sale (POS) Terminal or Checkout in a supermarket.

Summary : Checkout use case involves Customer, Clerk and Credit Payment Service actors and includes scanning items, calculating total and taxes, and payment use cases. This is an example of a large and complex use case split into several smaller use cases.

Purpose : List top level use cases for e-Library online public access catalog.

Summary : Patrons of a library can search library catalog online to locate various resources - books, periodicals, audio and visual materials, or other items under control of the library. Patrons may reserve or renew item, provide feedback, and manage their account.

Purpose : Provide top level use cases for a web customer making purchases online.

Summary : Web customer actor uses some web site to make purchases online. Top level use cases are View Items , Make Purchase and Client Register .

Purpose : Define major use cases for a credit card processing system ( credit card payment gateway ).

Summary : The merchant submits a credit card transaction request to the credit card payment gateway on behalf of a customer. Bank which issued customer's credit card is actor which could approve or reject the transaction. If transaction is approved, funds will be transferred to merchant's bank account.

Purpose : Website management or administration UML use case diagrams example.

Summary : Website Administrator actor could manage user groups, users, user sessions, and logs. Help Desk staff uses a subset of functions available to the Website Administrator.

Purpose: Describe major services (functionality) provided by a hospital's reception.

Summary : This UML use case diagram example shows actor and use cases for a hospital's reception. Hospital Reception subsystem or module supports some of the many job duties of a hospital receptionist. Receptionist schedules patient's appointment and admission to the hospital, collects information from the patient by phone and/or upon patient's arrival to the hospital.

For the patient that will stay in the hospital ("inpatient") she or he should have a bed allotted in a ward. Receptionists might also receive patient's payments, record them in a database and provide receipts, file insurance claims and medical reports.

Purpose: Radiology diagnostic reporting UML use case diagram example for Simple Image and Numeric Report (SINR) IHE Radiology Integration Profile.

Summary : In the initial stage of diagnostic reporting, a reading physician records a diagnosis by generating a draft DICOM Structured Report (SR) object. Report Creator actor transmits that DICOM SR object to the Report Manager. External Report Repository Access actor is a gateway to obtain other enterprise department reports, such as Laboratory and Pathology, from within the Imaging department.

Purpose: Use case diagram example shows some simplified view of software licensing use cases supported by Sentinel EMS Application.

Summary : Sentinel License Development Kit (Sentinel LDK) is a Software Digital Rights Management (DRM) solution by SafeNet Inc. that delivers strong copy protection, protection for Intellectual Property (IP), and secure and flexible licensing. The Sentinel EMS application handles three major workflows - license planning, order processing and production, and activation of trial software.

Home » Use Case Analysis » Creating Sequence Diagrams with a Use Case-Driven Approach: A Comprehensive Guide

Creating Sequence Diagrams with a Use Case-Driven Approach: A Comprehensive Guide

• Posted on March 21, 2023
• / Under Use Case Analysis , Visual Modeling

What is a Sequence Diagram

Software development requires an efficient communication and understanding between all stakeholders involved in the project. One of the essential tools for effective communication and understanding is the sequence diagram. A sequence diagram is a graphical representation of the interactions between different components of a system over time. To create a sequence diagram that accurately depicts the interactions within a system, it is crucial to follow a well-defined process. They are commonly used in software development to depict the flow of messages between objects and the order in which those messages are sent and received.

In this article, we will explore how to create a sequence diagram using a use case-driven approach.

A Step-by-Step Guide for Creating Sequence Diagrams

This article provides a step-by-step guide for creating sequence diagrams using a use case-driven approach. By following this process, you can create clear and comprehensive visualizations of the interactions within your system, helping to ensure that the system is designed to meet the needs of the users and that the interactions between components are well-defined and efficient.

The use case-driven approach focuses on identifying the key scenarios and interactions that a user will have with a system. This approach helps to ensure that the system is designed to meet the needs of the users and that the interactions between components are well-defined and efficient.

Step 1: Identify the use cases

The first step in creating a sequence diagram using a use case-driven approach is to identify the key use cases for the system. A use case is a description of a particular interaction between a user and the system. Some examples of use cases might include logging in, making a purchase, or updating a user profile.

Step 2: Create a use case diagram

Once you have identified the key use cases for the system, you can create a use case diagram to represent them visually. The use case diagram should show the different actors (i.e., users or external systems) that interact with the system, as well as the different use cases and their relationships.

Step 3: Develop the Use Case Description

For each use case in the use case diagram, develop a use case description with the flow of events section. The flow of events section should describe the steps that the user takes to interact with the system and the system’s responses to those steps.

Step 4: Develop Sequence Diagrams for Different Scenarios

Based on the flow of events in the use case description, develop the sequence diagrams for different scenarios: Normal, alternative and exceptions. The Normal scenario represents the typical path that a user takes to complete the use case. The Alternative scenarios represent any deviations from the Normal scenario that a user might take, and the Exception scenarios represent any errors or unexpected events that might occur during the use case.

The sequence diagram should show the interactions between the different objects over time, with each message represented as a vertical arrow. The order of the arrows represents the order in which the messages are sent and received.

The sequence diagram should also include any conditions or loops that are part of the interaction. For example, if a user enters an incorrect password when logging in, the system might display an error message and allow the user to try again.

Step 5: Refine and Revise

Once you have created the initial sequence diagram, you should review it carefully to ensure that all of the interactions are well-defined and efficient. You may need to revise the diagram or make changes to the system design based on your analysis.

Example – Mobile Banking App

The problem that the mobile banking application aims to solve is the inconvenience and time-consuming nature of traditional banking. With the mobile banking application, users can perform banking transactions and access their account information from anywhere, at any time, without having to physically visit a bank branch. Additionally, the mobile banking application provides users with a range of features and functionalities that are not available through traditional banking channels, such as depositing checks via mobile device, viewing special offers and promotions, and managing account alerts.

The aim of the mobile banking application is to provide users with a convenient and secure way to manage their finances on the go.

here are some candidate use cases for a mobile banking application:

• View Account Balance – Allows users to view their account balance(s) and transaction history.
• Transfer Funds – Allows users to transfer funds between their own accounts or to other accounts.
• Pay Bills – Allows users to pay bills online, such as utility bills, credit card bills, and loan payments.
• Deposit Checks – Allows users to deposit checks by taking a picture of the check with their mobile device.
• Locate ATMs – Allows users to find nearby ATMs and view their operating hours.
• Contact Support – Allows users to contact customer support for help with any issues they may encounter.
• View Offers – Allows users to view special offers or promotions from the bank.
• Manage Alerts – Allows users to manage account alerts, such as transaction notifications and balance alerts.

A use case description for the “Transfer Funds” use case in the mobile banking application:

Use Case Name: Transfer Funds

Actors: User

Summary: This use case allows the user to transfer funds between their own accounts or to other accounts.

Preconditions:

• The user must be logged in to the mobile banking application.
• The user must have at least one account set up in the application.

Basic Flow of Events:

• The user selects the “Transfer Funds” option from the main menu.
• The application presents the user with a list of their accounts and prompts them to select the account they want to transfer funds from.
• The user selects the account they want to transfer funds from.
• The application presents the user with a form to fill out with the recipient’s account information, including the account number and the name of the recipient.
• The user fills out the form and enters the amount they want to transfer.
• The application validates the recipient’s account information and the available balance in the user’s account.
• If the validation is successful, the application deducts the transfer amount from the user’s account and adds it to the recipient’s account.
• The application displays a confirmation message to the user with the details of the transfer.

Alternate Flows:

• 6a. If the recipient’s account information is invalid or the available balance in the user’s account is insufficient, the application displays an error message to the user and prompts them to correct the information or select a different account.
• 6b. If the user cancels the transaction before it is completed, the application returns to the main menu.

Postconditions:

• The funds have been successfully transferred from the user’s account to the recipient’s account.
• The user is presented with a confirmation message with the details of the transfer.

Here are the sequence diagrams for the normal, alternate, and exception flows of the “Transfer Funds” use case in the mobile banking application:

Normal Flow Sequence Diagram:

Alternate Flow Sequence Diagram (6a):

Alternate Flow Sequence Diagram (6b):

Now, lets elaborate only the normal flow sequence diagram into a more detailed MVC sequence diagram:

Using a use case-driven approach to create sequence diagrams helps ensure that the system is designed to meet the needs of the users and that the interactions between components are well-defined and efficient. Sequence diagrams are an essential tool in software design and development as they help to illustrate the interactions between objects or components within a system. A sequence diagram is a type of interaction diagram that depicts the flow of messages exchanged among objects or actors in a system. They are particularly useful in understanding and designing the behavior of a system in response to a specific use case. By developing a use case description with the flow of events section and then developing sequence diagrams for different scenarios, you can create a clear and comprehensive visualization of the system’s interactions.

Leave a Comment Cancel reply

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

Save my name, email, and website in this browser for the next time I comment.

• Visual Paradigm Online
• Request Help
• Customer Service
• Community Circle
• Demo Videos
• Visual Paradigm
• YouTube Channel
• Academic Partnership

404 Not found

You are using an outdated browser. Please upgrade your browser .

T4Tutorials.com

Activity diagram | scenario and case study base project examples.

Activity diagrams are behavioral diagrams.

Activity VS Task

An activity is work that is done with no specific purpose in mind or in some cases, activity can have a mini purpose.

The task is a big term as compared to activity and task is specifically an activity that is done with only having a particular purpose in mind.

What is Activity?

A project is divided into many interdependent activities to complete a task.

The sequence or the order of the activities is very important.

Activity Diagram Case Study 1

Suppose we want to develop a web-based social network with the following functionalities;

The user should signup for the system.

The user should log into the system and can send friend requests or block the user.

We need to convert this system into separate components;

Activity 1: Sign up

Activity 2:  log in

Activity 3: Send Friend request

Activity 4: block a user

Explicit requirements VS implicit requirements

Explicit requirements:.

• Clearly described by the customers

implicit requirements :

• Not Understood
• Not Clearly described r by the customers

Activity Diagram for module 1 of case study 1

Activity Diagram for module 2 of case study 1

Activity Diagram for module 1 of case study 2

The user can search books, viewbooks Without any fee but can download the Book only and only if he pays money. Provide the facility of managing the cart To the user, so that he can update his cart.

How many activity diagrams for 1 Project?

In most of the cases;

• 1 activity diagram for each separate module of your project.
• The activity of one module can also be drawn in another module if required.
• Don’t mix all activities of all modules of your big project in only one diagram.
• 1 diagram represents the flow of one selected activity from starting to end. Only helping activities can be drawn with the selected activity.

Purpose of Activity Diagram

• Draw the activity flow for a system
• Describe the sequence from one activity to another
• High-level understanding of the system’s functionalities
• Modeling business requirements
• Investigating business requirements as and when required

UML Diagrams MCQs Questions Answers

Related Posts:

• Activity Diagram of Karate Club Management System Project
• Activity Diagram of Daily Expense Tracker Android App Project
• Activity Diagram of Housing Society Management System
• Activity diagram MCQs
• Comparison of Use Case Diagram VS  Class diagram
• Incremental Model, advantages, examples, Case study