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

Component diagram ​

The bookshop's software as components: the Shop API holding its Basket and Checkout, the Storefront that calls it, sign-in from the accounts package, the outside payment provider, the order worker and the jar the API ships in. The page below opens on it, The bookshop's components, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. A package drawn as a box holding a component and a class (accounts)
  2. Components as rectangles with UML's component icon at the top right
  3. A class realizing a component: dashed, a hollow triangle at the component (SessionStore to Accounts and sign-in)
  4. An interface drawn as a rectangle with <<interface>> and its operation (SignIn)
  5. A provided interface as a rectangle: dashed, a hollow triangle (Accounts and sign-in provides SignIn)
  6. A required interface as a rectangle: dashed, an open arrowhead and <<use>> (Shop API uses SignIn)
  7. A dependency with a stereotype: <<call>> from Order worker to Shop API
  8. An artifact with <<artifact>> and UML's document icon (shop-api.jar)
  9. A manifestation: dashed, an open arrowhead, <<manifest>> (shop-api.jar to Shop API)
  10. A note linked to the artifact by a dashed line
  11. A component holding components, drawn as a box with its name and icon in the header (Shop API holding Basket and Checkout)
  12. Ports as small squares on their owners' borders, each named beside it
  13. A delegation inward: a solid line with an open arrowhead from Shop API's orders port to Basket's
  14. An assembly connector joining two parts directly (Basket and Checkout)
  15. A delegation outward, from Checkout's payments port to Shop API's
  16. An assembly connector between the ports of two components (Shop API's payments to Payment provider's charges)
  17. A typed port, named name : Type (charges : Charging)
  18. A provided interface as a ball on a plain stem, from a port (Orders, provided at Shop API's orders port)
  19. A required interface as a socket, a half circle round the ball (Storefront requires Orders)
  20. A component with a stereotype: <<web app>> over Storefront

In another setting ​

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

The same components, laid out down

Laid out down (direction down) instead of right: the same components, ports, interfaces and lines.

Edit this page on GitHub
Pager
Previous pageComposite structure
Next pageDeployment