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

Timing diagram ​

One bookshop order being paid for, millisecond by millisecond: the order worker, the card gateway and the mailer stepping through their states, the order's status as values, the messages between them and the limits on how long it may take. The page below opens on it, Paying for one bookshop order, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. Lifelines as lanes, name : Type on the left and their states in a column (worker : OrderWorker, payments : CardGateway, mailer : Mailer)
  2. State lifelines as step lines, level in a state's row, upright at each change
  3. A call message with a filled arrowhead from the sender's level to the receiver's (charge(total))
  4. Its reply, dashed with an open arrowhead (paid)
  5. A time constraint, a tick with its label ({<= 1000 ms})
  6. An asynchronous message with an open arrowhead and a stereotype (<<signal>> receipt)
  7. A duration constraint spanning two lanes, its extension lines reaching both ({<= 800 ms})
  8. A duration constraint within one lane ({<= 300 ms})
  9. A general value lifeline, present as values: the order's status in a band whose edges cross at each change (placed, paying, paid, packing)
  10. A time ruler in milliseconds under the last lane, major and minor ticks
Edit this page on GitHub
Pager
Previous pageInteraction overview
Next pageInformation flow