In this guide

ACTORS, GOALS AND SYSTEMS

Use Case Diagram guide

Define external actors and system goals. Draw UML relationships, add specifications, and save or export a use case diagram.

Actors & goals → UML use case diagramOpen Use Case Diagram

Model actors and their goals

A use case diagram shows external actors and the goals a system supports. It describes responsibilities, not the order of API calls or database tables. Use Sequence Diagram for interactions over time and DB Diagram for relational tables.

Build your first use case diagram

  1. Choose Blank diagram or the Online shop template. Add an actor, a use case, and a system boundary from Library. Click to add, or drag a Library card onto the canvas.
  2. Drag use cases into the system boundary. Moving its header moves the contained elements together. Drag a use case outside to remove its membership. Deleting a boundary keeps its contents.
  3. Choose a relationship in Library, then click the first and destination elements, or drag between connection points. The arrow beside Connect opens a named endpoint chooser. Double-click an element to edit its text directly; Edit details opens all its fields.

Choose the right relationship

Choose the right relationship
RelationshipMeaning and direction
AssociationAn undirected solid line connects an actor to a use case they participate in.
IncludeA dashed open arrow points from the base use case to behavior it always includes.
ExtendA dashed open arrow points from optional additional behavior to the base use case being extended. Add a condition and an extension point when useful.
GeneralizationA solid line with a hollow triangle points from a specific actor or use case to its more general parent.
Note linkA dashed line attaches a note to an element without changing the model.
@startuml
left to right direction
actor Customer
rectangle Shop {
  usecase "Place order" as Order
  usecase "Process payment" as Payment
  usecase "Apply discount" as Discount
}
Customer -- Order
Order ..> Payment : <<include>>
Discount ..> Order : <<extend>>
@enduml
Checks are suggestions. Cycles, duplicate names and unconnected elements remain editable. Invalid endpoint combinations and duplicate relationships are explained before they can change the document.

Add useful detail without crowding the drawing

Drag a connection point onto another element to connect them. If the current relationship does not fit, choose a valid type in the dialog. Auto sides follow elements while dragging; choosing a side fixes that end.

Details supports names, descriptions, actor stereotypes, colors and system membership. Use cases can list extension points and an optional specification: goal, preconditions, main flow, alternative flows and postconditions. The complete text stays in JSON and cloud files; long canvas text is shortened for readability.

For relationships, drag an endpoint to reconnect it, move the bend grip to adjust its route, or drag a selected label. Double-click a label to edit it. Details lets you reverse direction, fix the top, bottom, left or right side, or reset the automatic route. Curved, rounded elbow and straight paths are presentation choices.

Arrange and navigate

Drag elements freely, resize notes and boundaries, or use Arrange for a readable starting layout. Shift-drag selects several elements. Focus selection changes the camera only when requested. Find searches element names, types and descriptions.

On phones and tablets, switch between Library, Diagram and Details. The canvas stays mounted so changing panels preserves the camera. Grid, minimap, connector style and camera are saved with the file. Read-only public viewers can inspect and export without modifying the original.

Save, share and export

Save signs in when needed and creates a separate Use Case Diagram cloud file. File opens its own saved-file list and sharing controls. Unsaved changes prompt before leaving. New diagrams remain in memory until saved or downloaded as JSON.

Download JSON for a complete editable copy. Import accepts exported Erd Go Use Case Diagram version 1 JSON, validates it before replacement, and supports Undo. PlantUML is a local text export, not an import format; its renderer chooses its own layout.

Export previews the entire diagram or current view as PNG, JPEG, WebP, SVG or PDF. SVG stays vector and PDF contains an image. Image generation is loaded only when requested and never sends the diagram to a rendering service.

Keyboard shortcuts

Keyboard shortcuts
ActionShortcut
SaveCtrl/Cmd+S
Undo / RedoCtrl/Cmd+Z / Shift+Z or Ctrl+Y
Copy / Paste / Duplicate selectionCtrl/Cmd+C / V / D
FindCtrl/Cmd+K
Move selected elementsArrow keys; Shift moves by 10 pixels
Delete selected elementsDelete or Backspace outside text fields
Cancel a dragEscape
Text fields keep their native editing shortcuts. Imports support up to 500 elements and 1,500 relationships. JSON is the full editable format.

Work with AI

Copy this guide and describe the actors, their goals, the system scope and optional behavior. Ask an AI to review the model before drawing it. Do not assume that an AI description, arbitrary JSON or PlantUML can be imported into the workspace.