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.
What it shows
In the order you find them in the picture:
- Lifelines as lanes,
name : Typeon the left and their states in a column (worker : OrderWorker, payments : CardGateway, mailer : Mailer) - State lifelines as step lines, level in a state's row, upright at each change
- A call message with a filled arrowhead from the sender's level to the receiver's (charge(total))
- Its reply, dashed with an open arrowhead (paid)
- A time constraint, a tick with its label (
{<= 1000 ms}) - An asynchronous message with an open arrowhead and a stereotype (<<signal>> receipt)
- A duration constraint spanning two lanes, its extension lines reaching both (
{<= 800 ms}) - A duration constraint within one lane (
{<= 300 ms}) - A general value lifeline,
presentasvalues: the order's status in a band whose edges cross at each change (placed, paying, paid, packing) - A time ruler in milliseconds under the last lane, major and minor ticks