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

Composite structure diagram ​

Inside a bookshop's OrderService: the parts it is built from, the ports it talks through, the connectors that join them, and the publish-subscribe collaboration its parts play roles in, in one composite structure diagram. The page below opens on it, Inside the bookshop's OrderService, live: pan, zoom, select and go into the cards that stack.

Open full screen (Composite structure)Conformance (Composite structure)PDF (Composite structure)Model (Composite structure)

What it shows ​

In the order you find them in the picture:

  1. The subject, OrderService, as a box with its name in the top left
  2. Ports on the subject's border, each pinned to a side with present side: api on the left, payments on the right
  3. Parts as rectangles name : Type [multiplicity]: checkout : CheckoutFlow [1], pricing : PriceCalculator [1], orders : OrderRepository [1]
  4. Parts of other multiplicities: mailers : Mailer [1..*] and listeners : OrderListener [0..*]
  5. A shared part, drawn dashed (listeners)
  6. Parts showing their types' ports: checkout's requests, quotes and charges, pricing's quotes
  7. A connector from the subject's port in to a port on a part (api to checkout's requests)
  8. A connector between ports of two parts (checkout's quotes to pricing's quotes)
  9. A connector from a part's port out to the subject's port (checkout's charges to payments)
  10. Connectors between parts with no ports (checkout to orders, orders to mailers, checkout to listeners)
  11. A collaboration use, a dashed ellipse orderEvents : PublishSubscribe
  12. Role bindings, dashed with no ends, each labelled with its role (publisher, subscriber)
  13. An open collaboration, a dashed ellipse with its name over a dashed line, holding its roles and the connector between them (PublishSubscribe)
  14. A note linked to a port by a dashed line (on payments)

In another setting ​

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

The same structure, laid out down

Laid out down (direction down) instead of right, the payments port on the bottom side: the same parts, ports, connectors and collaboration.

PublishSubscribe as the subject

PublishSubscribe as the view's subject instead of OrderService: a collaboration as the subject, its roles drawn as its parts. A view has one subject, so the two cannot share a picture.

Edit this page on GitHub
Pager
Previous pagePackage
Next pageComponent