Actors and User Goals
Declare actors for people, organizations, or external systems. Write each use case as a goal the actor wants to accomplish, such as Place Order or Approve Refund, instead of naming screens or implementation details.
Create a PlantUML use case diagram online, connect actors to system capabilities, preview the result, and export PNG or SVG.
Start with the Use Case Diagram template, edit the PlantUML source, and preview the result live.
Use this focused use case diagram tool for quick previews and exports. Open the full editor for AI generation, syntax repair, sharing, and saved projects.
Model actors, use cases, system boundaries, associations, includes, extensions, and generalization in an editable PlantUML workspace with live preview and PNG or SVG export.
Start from valid PlantUML source designed for a practical use case diagram.
See the rendered diagram update as you edit the PlantUML source.
Learn the syntax and modeling choices used for requirements discovery, product scoping, stakeholder workshops, access analysis, and system boundary documentation.
Download a shareable PNG or scalable SVG from the same source.
Create and preview PlantUML without installing Java, Graphviz, or an IDE extension.
Move to the full editor for AI generation, repair, sharing, and saved projects.
Use the built-in template to create a use case diagram for requirements discovery, product scoping, stakeholder workshops, access analysis, and system boundary documentation.
Start with the built-in Use Case Diagram template.
Name each external actor by role rather than by person.
Place user goals inside a system boundary.
Connect actors and add include or extend relationships only when they clarify shared behavior.
Preview and export the use case diagram as PNG or SVG.
Learn the core syntax and modeling decisions behind a useful use case diagram, then apply them directly in the online editor above.
Declare actors for people, organizations, or external systems. Write each use case as a goal the actor wants to accomplish, such as Place Order or Approve Refund, instead of naming screens or implementation details.
Group use cases inside a rectangle named after the system or product. Actors normally remain outside the boundary, making it clear which responsibilities belong to the system and which belong to its environment.
Use <<include>> when one use case always reuses another behavior. Use <<extend>> for conditional or optional behavior. Avoid adding these relationships when a direct actor-to-goal link already communicates enough.
(Checkout) ..> (Authenticate User) : <<include>>
(Apply Coupon) ..> (Checkout) : <<extend>>A use case diagram provides a high-level map of actors and goals. User stories and acceptance criteria describe the detailed behavior behind those goals. Use the diagram for scope and navigation, then link to detailed requirements.
The editable example demonstrates a practical use case diagram. Change the source, check the live preview, and export the version you need.
@startuml
left to right direction
actor Customer
actor Admin
rectangle "Order System" {
usecase "Place Order"
usecase "Track Order"
usecase "Manage Orders"
}
Customer --> "Place Order"
Customer --> "Track Order"
Admin --> "Manage Orders"
@endumlUse these related tools when you need a different export format or a full PlantUML editing workflow.
Browse the complete OnUML matrix of online PlantUML tools and converters.
View all PlantUML toolsUse the general editor when you want to switch freely between diagram types.
Open the general editorCreate and export a focused sequence diagram with a built-in template.
Create a sequence diagramPlantUML keeps use case diagrams in reviewable text, making them easier to update, version, reuse, and export as the design changes.
Open directly into a Use Case Diagram template instead of adapting an unrelated example.
Store the diagram as readable text that works well in documentation and version control.
Check structure, labels, and relationships before exporting the rendered diagram.
It is a browser-based editor that starts with a Use Case Diagram template and lets you edit PlantUML source, preview the rendered diagram, and export PNG or SVG without local setup.
Use it to model actors, use cases, system boundaries, associations, includes, extensions, and generalization. Common uses include requirements discovery, product scoping, stakeholder workshops, access analysis, and system boundary documentation.
Place related use cases inside a rectangle block named after the system. Keep external actors outside the block and connect them to the goals they use.
Include represents behavior that is always reused by another use case. Extend represents optional or conditional behavior added to a base use case.
Yes. Preview the diagram, then download PNG for slides and quick sharing or SVG for scalable documentation and web use.
No. The online tool uses a server-backed preview, so you can edit and render the diagram directly in the browser.
Open the full OnUML editor for AI generation, syntax repair, sharing, saved projects, and multi-format diagram workflows.