Tag: use case diagram example

use case diagram example,

I’ll describe a use case diagram example for an ATM (Automated Teller Machine) system, as it’s a familiar concept for many:

System:

ATM

Actors:

  1. Bank Customer
  2. Bank System

Use Cases:

  1. Withdraw Cash: The customer can withdraw money from their account.
  2. Deposit Money: The customer can deposit money into their account.
  3. Check Balance: The customer can view the current balance in their account.
  4. Change PIN: The customer can change their ATM PIN.
  5. Print Mini Statement: The customer can print a mini statement for their recent transactions.
  6. Transfer Money: The customer can transfer money to another account.
  7. Notify on Withdrawal: The Bank System notifies the customer after a successful withdrawal.

Diagram Description:

  • Actors Representation:
    • The Bank Customer would be represented as a stick figure on the left side.
    • The Bank System would be another stick figure, representing systems or services that interact with the ATM but aren’t directly controlled by it.
  • Use Cases Representation:
    • Each use case, such as “Withdraw Cash” or “Deposit Money,” would be represented as ellipses inside a rectangle. The rectangle represents the boundary of the ATM system.
  • Associations:
    • Lines would be drawn from the Bank Customer actor to each use case they can perform, such as “Withdraw Cash,” “Deposit Money,” “Check Balance,” “Change PIN,” “Print Mini Statement,” and “Transfer Money.”
    • A line would be drawn from the Withdraw Cash use case to the Notify on Withdrawal use case to indicate that once money is withdrawn, a notification is sent.
  • Include/Extend:
    • If, for instance, every time a “Withdraw Cash” operation is done, a “Check Balance” operation is automatically triggered, an “Include” relationship can be shown from “Withdraw Cash” to “Check Balance.”
    • If “Transfer Money” has an optional step for adding a note or memo to the transfer, an “Extend” relationship could be drawn from “Transfer Money” to a use case named “Add Transfer Note.”

This is a basic overview of what the use case diagram for an ATM system might look like. In a real-world scenario, there could be additional complexities, more actors, and more use cases, depending on the depth and detail of the system being modeled.

5 Steps To Creating An Effective UseCase Diagram

UseCase diagrams show how different parts of a system interact. They’re used in software development to describe how users will interact with a program.

5 Steps To Creating An Effective UseCase Diagram
5 Steps To Creating An Effective UseCase Diagram

How to create UseCase Diagram effectively.

Start with the end result.

You should start by thinking about the end result. What do you want to happen after the user completes the process? This is where you’ll need to define the inputs and outputs of each part of the process.

Identify the actors involved.

Once you’ve identified the inputs and outputs, you need to identify who will perform those actions. Who will take care of the inputs and who will handle the outputs?

Draw the flowchart.

Use a flow chart to show how each user interacts with the system. This will help you determine where the bottlenecks might occur.

Add detail as needed.

You should add details to the process as needed. If there are multiple steps involved, make sure to list them out. Also, consider adding more than one path through the process.

Review the UseCase diagram.

Once you’ve completed the process, review the diagram again. Are there any gaps in the flow? Do you need to add additional steps?

  1. Define the Problem

The first step to creating an effective UseCase diagram is defining the problem. What do you want to achieve? What are the goals of your project? How does your product solve the problem? What problems does it address? What are the user stories? What are the user journeys? Once you have defined the problem, you should be able to identify the stakeholders involved in the solution. Who are they? Why are they important? What are their roles? What are their concerns? What are their motivations? You should also know what the end goal is for each stakeholder.

  1. Identify Stakeholders

Once you have identified the problem and its stakeholders, you need to determine who else is affected by the problem. These people may not be directly involved in the problem, but could still be affected by it. For example, if you are working on a web application, you might consider the users of the website. If you are developing a mobile app, you might consider the people using the app. In addition, you should consider any external parties that might be affected by the problem. For example, if your product is a software system, you might consider the IT department at your company.

  1. Determine Roles

After identifying the stakeholders, you need to define their roles in relation to the problem. Each role should have a clear purpose and function. For example, a user story describes a person’s interaction with the system. A user journey describes how a user uses the system. A persona is a representation of a typical user. A user type represents a group of users. A user profile is a description of a specific user.

  1. Understand Motivations

You now need to understand the motivations of the stakeholders. Why do they care about the problem? Why do they want to solve it? What are their concerns regarding the current situation? What are their expectations? What are their fears? What are their hopes?

  1. Create User Stories

Now that you have identified the problem, stakeholders, and their roles, you can start writing user stories. A user story is a short sentence describing a single interaction between a user and the system. For example, “As a user I want to create a new account”.

These are the important points to create a UseCase diagram.

You can review the below articles also.

  1. What is Agile User Story Acceptance Criteria ?
  2. User Story Examples and User Stories
error

Enjoy this blog? Please spread the word :)