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

Package diagram ​

How a bookshop's software is split into packages: sales at the centre, the catalog, payments and the shared types it builds on, fulfilment and reporting that depend on it, and wholesale that merges it, in one package diagram. The page below opens on it, Bookshop packages, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. Open packages drawn as boxes holding their elements, each name in a tab at the top left (fulfilment, sales, payments, catalog, shared)
  2. A qualified name for an element whose own package the view does not show (couriers::Courier inside fulfilment)
  3. A closed package, a folder with an empty tab and its name in the body (reporting, whose contents are not shown)
  4. A note (a comment with a folded corner) linked by a dashed line to a package (wholesale)
  5. A dependency with a label (fulfilment ships orders from sales)
  6. Dependencies with a stereotype as their label (reporting <<use>> sales, sales <<use>> payments)
  7. A package merge, dashed with an open arrowhead and <<merge>> (wholesale merges sales)
  8. A package with a stereotype in its tab (<<subsystem>> sales)
  9. Classifiers drawn by name and keyword: classes, <<entity>> Order, <<enumeration>> OrderStatus, <<interface>> Payable, <<dataType>> Money, <<primitive>> Isbn
  10. A public package import, dashed with an open arrowhead and <<import>> (sales imports catalog, catalog imports shared)
  11. A profile application to a profile drawn as a closed folder, <<apply>> and <<profile>> (sales applies BookshopConventions)
  12. A package nested in another, a box inside a box (card inside payments)
  13. A private package import, drawn <<access>> (payments accesses shared)

In another setting ​

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

Bookshop packages, laid out right

Laid out right (direction left at its default) instead of down: the same packages, classifiers and lines, the dependents on the left.

Edit this page on GitHub
Pager
Previous pageObject
Next pageComposite structure