Skip to content
umlimator
Main Navigation GuideAPIExamples
Changelog
npm
Releases

Appearance

Sidebar Navigation

Examples

All examples

Maps

Map

UML structure

Class

Object

Package

Composite structure

Component

Deployment

Profile

UML behaviour

Use case

Activity

State machine

Sequence

Communication

Interaction overview

Timing

Information flow

SysML

Requirement

Block definition

Internal block

Parametric

Architecture, data and process

C4

Entity-relationship

Data flow

Flowchart

BPMN

Mindmap

Cloud architecture

AWS

Google Cloud

Azure

Atlas

The Umlimator Atlas

The Bookshop Atlas

Activity diagram ​

A bookshop fulfilling an order, in nested lanes for the order desk and the warehouse beside the email service: taking the order, checking stock and restocking, then paying, packing and telling the customer in parallel before the parcel ships. The page below opens on it, Fulfilling a bookshop order, live: pan, zoom, select and go into the cards that stack.

Open full screen (Activity)Conformance (Activity)PDF (Activity)Model (Activity)

What it shows ​

In the order you find them in the picture:

  1. Lanes nested in a lane: Bookshop holding Order desk and Warehouse, beside Email service
  2. An initial node, a filled circle
  3. Actions as rounded boxes, long names wrapped (Take the next order from the queue)
  4. A data store, <<datastore>> Stock levels, read by an object flow with a name (levels)
  5. An object node (Order) with an object flow in and out
  6. A decision with its question inside the diamond (All books in stock?) and guards on its exits ([yes], [else])
  7. A note linked to the decision by a dashed line
  8. A send signal action, a convex pentagon (Restock request), and an accept event action, a concave one (Books delivered)
  9. A merge, a diamond two flows enter (books ready)
  10. A fork, a bar sending three flows into three lanes
  11. A call behaviour action with the rake at its bottom right (Take payment), opening the activity it calls
  12. A join, a bar where payment and packing meet
  13. A flow final, a circle with an X (after the email)
  14. An activity final, a ring round a filled circle

In another setting ​

The same example, where a setting cannot share the picture above:

The same activity, laid out right

Laid out right (direction right) instead of down: the lanes become bands across the page, their names turned, the same nodes and flows.

Take payment, the activity the call opens

The activity the call behaviour action Take payment opens (Enter or a double-click on it): its own view, with a retry loop back through a merge and a named flow paid [yes].

Edit this page on GitHub
Pager
Previous pageUse case
Next pageState machine