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

Map ​

A bookshop's systems on one map: the people who use it, the apps they use, the API at its heart with what it calls, stores and hands on, the support desk, and what is new, planned and switched off. The page below opens on it, The bookshop's systems, live: pan, zoom, select and go into the cards that stack.

Open full screen (Map)The model guide (Map)PDF (Map)Model (Map)

What it shows ​

In the order you find them in the picture:

  1. The view's title and caption over the map
  2. A card drawn by its kind: person (Shoppers), user (Shop staff), terminal (Admin CLI), browser app (Storefront), phone (Shop app), folder (Pricing), hexagon (Fraud check), cylinder (Orders), pipe (Order queue), robot (Support agent), page with a folded corner (returns.md), box in perspective (Hosts), dashed external card (Card gateway)
  3. A card's own shape over its kind: Back office drawn as a window
  4. A card with its name only, the sub-line kept for the panel (Admin CLI, noSub)
  5. Logos on cards (Storefront React, Shop API FastAPI, Orders PostgreSQL)
  6. Badges on cards, plain and in a tone (public, on call, backed up)
  7. Change marks: a NEW card (Shop app), a PLANNED card dashed (Gift cards), a REMOVED card dashed and struck through (Reminder bot)
  8. A main-step card with verb chips and an edit mark (Shop API: checkout, refund)
  9. Line kinds in their colours: calls, feeds (charges, saves), triggers (checks), state (paid order, reads) and guard (if within 14 days)
  10. Line weights 1 to 3 drawn as widths (POST /orders 3, order 2)
  11. Steps in circles on the lines, numbers and a pill (1 to 6, and 3a)
  12. A line with a sub-label (POST /orders over JSON)
  13. Line styles over the kind: dashed (runs jobs), security (charges), async (paid order)
  14. Added lines green and flowing (on the go, redeem), a removed line rose and dashed (nudges), an edit mark on a line (saves)
  15. Boxes around cards, one nested in another (Data in Shop platform), with badges on their borders (EU, backed up nightly)
  16. Tinted boxes, dashed with the title in their tone (Data in green, Support in violet)
  17. A line ending on a box's border (Hosts runs Shop platform)
  18. One pin (layout): the Card gateway at column 6, row 0, so the charges line clears the Data box
  19. Two lenses in the page's Lenses menu: Who owns what (rings each card in its owner's tone) and Where the money goes (lights the feeds lines)

In another setting ​

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

An order, in run order

As a numbered view (render sequence): the cards and lines a checkout touches, numbered in run order instead of the hand-set steps, with no boxes.

Edit this page on GitHub
Pager
Previous pageAll examples
Next pageClass