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

State machine diagram ​

One bookshop order's life, from placed to delivered, cancelled or erased: the payment result chosen at a choice, picking and payment run side by side in two regions, a hold resumed by history, delivery with its problems, and the refund. The page below opens on it, An order's life, live: pan, zoom, select and go into the cards that stack.

Open full screen (State machine)Conformance (State machine)PDF (State machine)Model (State machine)

What it shows ​

In the order you find them in the picture:

  1. An initial pseudostate, a filled circle
  2. A state with entry, do and exit rows and an internal transition (Placed)
  3. A transition labelled with its trigger only (payment result)
  4. A choice, a diamond, its exits guarded: [card authorised], [paid by gift card] and [else] / email the shopper
  5. A fork, a bar, splitting into states in two regions (after [paid by gift card])
  6. A composite state with two orthogonal regions, each named, a dashed divider between them (Fulfilling: Parcel and Payment)
  7. A transition ending on a composite state's border ([card authorised] into Fulfilling)
  8. An initial pseudostate inside each region
  9. A transition leaving a composite state from its border (hold requested, cancel requested / refund the payment)
  10. A deep history H* in the Parcel region, re-entered from On hold (hold lifted)
  11. A note linked to the deep history by a dashed line
  12. A self-transition with a trigger, a guard and an effect: capture failed [attempts < 3] / count the attempt
  13. A join, a bar, merging the two regions, then a transition with an effect only (/ hand the parcel to the carrier)
  14. A composite state holding its substates with no regions (In delivery)
  15. A shallow history H, re-entered when a problem is resolved
  16. A state with its activities collapsed (Out for delivery, present collapsed)
  17. A final state, a ring round a filled circle (parcel signed for / email the receipt)
  18. A closed composite state with UML's decomposition mark, its substates not shown (Under enquiry)
  19. A junction, a small filled circle, merging two transitions (refused at the door, parcel lost)
  20. A state's compartment cut to two rows then "+2 more" (Cancelled, present rows)
  21. A terminate pseudostate, an X (after 30 days / erase the shopper's details)
Edit this page on GitHub
Pager
Previous pageActivity
Next pageSequence