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

BPMN diagram ​

A bookshop order from the shopper's basket to the courier: the shopper's, the payment provider's and the bookshop's pools, the bookshop's work split between sales and a warehouse of picking and dispatch, with the messages that pass between them. The page below opens on it, A bookshop order, from basket to shipment, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. Pools as bands, each name turned in a header strip: Shopper, Payment provider, Bookshop
  2. A black-box pool with no flow nodes (Payment provider)
  3. A none start event (Basket is ready) and a user task with the figure at its top left (Place order)
  4. A message intermediate throw event, a double ring with a filled envelope (Order sent)
  5. Message flows, dashed with an open circle at the source and a hollow triangle at the target, labelled (Order, Charge request, Payment result, Shipping notice); those to the black-box pool end on its border
  6. A message intermediate catch event, a double ring with an open envelope (Shipping notice received), then a none end event
  7. Lanes in the Bookshop pool: Sales, and Warehouse holding the nested lanes Dispatch and Picking
  8. A message start event (Order received)
  9. A data object, a page with a folded corner (Order), and data associations, dotted with an arrowhead at their target
  10. A service task with the gear (Take payment)
  11. An interrupting timer boundary event on the task's border (No answer in 2 minutes)
  12. A text annotation, an open bracket, joined by a dotted association with an arrowhead (direction one)
  13. An exclusive gateway, a diamond with an X and its name outside (Paid?), its sequence flows labelled yes and no
  14. A second exclusive gateway merging the no flow and the timeout
  15. A terminate end event, a thick ring round a filled circle (Order cancelled)
  16. A parallel gateway, a diamond with a +, forking to two tasks, and another joining them
  17. A collapsed sub-process with the + marker (Pick and pack), opening its own view
  18. A data store reference, a cylinder (Stock database), read and written by data associations
  19. A timer start event beginning a second flow in the same pool (Every morning at 8:00)
  20. A timer intermediate catch event (Courier's pickup at 16:00)
  21. A call activity, a task with a thick border (Hand parcel to courier)
  22. A non-interrupting message boundary event, its rings dashed (Shopper asks where it is)
  23. A none intermediate throw event, a double ring with no marker (Parcel dispatched)
  24. A group, a dashed and dotted rounded rectangle round its members (Dispatch)
  25. A message end event, a thick ring with a filled envelope (Shipping notice sent)

In another setting ​

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

Pick and pack, the collapsed sub-process opened

The collapsed sub-process Pick and pack opened (Enter or a double-click on it): its own view, the sub-process its subject, showing the flow it holds.

The same process, Pick and pack expanded

The same process with Pick and pack expanded in place: a view that lists what a sub-process holds draws it as a frame round its flow instead of collapsed with the + marker.

Edit this page on GitHub
Pager
Previous pageFlowchart
Next pageMindmap