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

Sequence diagram ​

A bookshop's checkout: the shopper, the storefront, the api, a stock hold it creates and later deletes, the stock, the card gateway and the warehouse, their messages in time order with every frame the type draws. The page below opens on it, A bookshop's checkout, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. Lifelines left to right, each head name : Type over a dashed stem (api : ShopApi)
  2. An actor lifeline, <<actor>> over its head (shopper : Customer)
  3. A synchronous call, solid with a filled arrowhead (checkout(), place(order))
  4. A break frame with its guard (basket is empty) holding an asynchronous message
  5. An asynchronous message, solid with an open arrowhead (showError, orderPlaced, release)
  6. A self-call drawn as a loop back to its own lifeline (validate(order))
  7. Activation bars derived from the messages, a nested bar set to the right of its parent (api during validate)
  8. A create message, dashed and open, the created lifeline's head lowered to it (new(order) to hold : StockHold)
  9. A loop frame (for each order line) with a call and its reply inside
  10. A reply, dashed with an open arrowhead, back to the caller (reserved, paid, declined, result)
  11. An alt frame with two operands, their guards and a dashed divider (payment accepted, else)
  12. A par frame nested in an operand, its two operands running at once (tell the shopper, tell the warehouse)
  13. An opt frame nested in the par (shopper is still on the page), three frames deep
  14. An interaction use, a ref box over the lifelines it covers (Send receipt email, over storefront and api)
  15. A message with a stereotype, <<amqp>> before its label (pickList(order) to the warehouse)
  16. A delete message, the receiver's stem ending in a cross (close() to hold)
Edit this page on GitHub
Pager
Previous pageState machine
Next pageCommunication