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

C4 diagram ​

The online bookshop in C4, one model zoomed to every level: its containers first, inside the bookshop's boundary, then the same model as a system context, a landscape, the Shop API's components, placing an order step by step, and the production deployment. The page below opens on it, Bookshop: containers, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. People in C4's person shape, with their description (Shopper, Shop staff)
  2. The subject's boundary, a dashed box titled Bookshop [Software System], holding its containers
  3. Containers with C4's three lines: the name, [Container: technology] and the description
  4. Container shapes chosen by shape: a phone (Mobile app), a browser (Storefront), a terminal (Stock import), a robot (Order worker), a folder (Cover images), a cylinder (Database), a pipe (Order queue)
  5. A container in the default box (Shop API)
  6. Relationships drawn solid with an open arrow, labelled description [technology]
  7. A relationship with no technology, its description alone (Load price lists with)
  8. A label cut with an ellipsis at 280 px (Reads the catalogue and places orders through [JSO...])
  9. A view that draws only the relationships its edges lists (the email to the shopper and the worker's database write are left out)
  10. An implied relationship, dashed: Shop API to Email service, standing for Accounts and sign-in's password reset emails
  11. External software systems in grey outside the boundary (Payment provider, Email service, Courier)
  12. A note linked by a dashed line to a container (Order worker)

In another setting ​

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

Bookshop: system context

A system context view (c4.context): the bookshop as one box among its people and external systems; the box opens the containers.

The bookshop's systems: landscape

A system landscape view (c4.landscape): every system of the business side by side, Bookkeeping included, with no system as the subject.

Shop API: components

A component view (c4.component): inside the Shop API's boundary, its five components and what they talk to; an implied line becomes the real one, Accounts and sign-in to the Email service.

Placing an order

A dynamic view (c4.dynamic): placing an order as ten numbered steps between the containers, the view's edges in time order.

Bookshop: production deployment

A deployment view (c4.deployment): deployment nodes nested as boxes, holding the container instances that run in production.

Edit this page on GitHub
Pager
Previous pageParametric
Next pageEntity-relationship