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

Communication diagram ​

A shopper checks out and the card is accepted: the storefront, the shop's API, the payment provider and the card network pass the order along their links, a receipt is created and the basket deleted. The page below opens on it, Checkout, the card accepted, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. A lifeline with <<actor>> over its head (shopper : Shopper)
  2. Lifeline heads name : Type (storefront : Storefront, api : ShopApi)
  3. Connectors as plain lines with no arrows, each carrying its messages as a stack the line runs through
  4. Messages numbered by nesting, 1, 1.1, 1.1.2, down to 1.1.2.1.1
  5. Calls with a small filled arrow toward the receiver (checkout(), charge(total))
  6. A message with a stereotype after its number (1.1: <<secure>> place(order))
  7. An async message with an open arrow (orderPlaced)
  8. Replies with a dashed open arrow (paid, result, confirmation page)
  9. A self connector drawn as a loop, carrying a message to the lifeline itself (validate(order))
  10. A create message, <<create>> before its text (new(order) to receipt)
  11. A delete message with a filled arrow, <<destroy>> before its text (clear() to basket)
  12. Two messages one way and a reply the other way on one link (storefront to api)
  13. A connector with no message, a single line (api to stock)

In another setting ​

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

The same checkout, laid out right

Laid out right (direction right) instead of down: the same lifelines, links and numbered messages.

Edit this page on GitHub
Pager
Previous pageSequence
Next pageInteraction overview