ChatDiagram
Try for free
2 templates · Use case diagram

System Requirements Use Case Diagram Examples

Use case diagrams capture the functional requirements of a system from the user's perspective — who interacts with it (actors) and what they can do (use cases), without prescribing how.

Standard OMG UML 2.5.1 §18Engine schematex-usecaseExport SVG · PNG · PDF
2 templates
Use case diagram System Requirements
Online bookstore use case diagram (include + extend) — Use Case DiagramOnline bookstore use case diagram (include + extend) — Use Case DiagramSystem RequirementsUse template →ATM use case diagram (UML) — Use Case DiagramATM use case diagram (UML) — Use Case DiagramSystem RequirementsUse template →

Nothing close enough? Start from a blank use case diagram → Describe it in one paragraph.

How to

How to use an use case diagram template.

  1. 01Identify the actors

    Name the users, roles, or external systems that interact with the system — these become the stick-figure actors.

  2. 02List the use cases

    Describe each thing a user can do with the system — these become the ovals inside the system boundary.

  3. 03Draw the associations

    Connect each actor to the use cases they participate in — the AI draws the association lines.

  4. 04Add include and extend (optional)

    Describe use cases that always include another (<<include>>) or optionally extend one (<<extend>>) for more precise requirements modeling.

FAQ

Questions about use case diagram templates

What is a use case diagram?

A UML diagram that shows the functional requirements of a system from the user's perspective. Actors (people or external systems) interact with use cases (system functions) inside a system boundary.

What is the difference between <<include>> and <<extend>>?

<<include>> means a use case always invokes another (e.g., "Pay for Order" always includes "Validate Payment"). <<extend>> means a use case optionally adds behavior to another (e.g., "Apply Discount" extends "Complete Purchase" in some conditions).

When should I use a use case diagram vs a user story map?

Use case diagrams show what a system does from an external perspective — good for scope agreement and requirements documentation. User story maps show the user journey and prioritized backlog — good for sprint planning.