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

Profile diagram ​

The bookshop's modelling conventions as a profile: stereotypes for entities, owners, columns and modules with their tag definitions, a second Audit profile, and the sales package that applies both, its classes showing the tags they carry. The page below opens on it, The bookshop's modelling conventions, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. A package drawn as a box holding classes (sales), a closed package inside it with a stereotype over its name (<<module>> payments)
  2. A class with two stereotypes over its name, one from another profile qualified by it (<<aggregateRoot>>, <<Audit::record>> on Order)
  3. A tag compartment per stereotype, headed <<name>>, each row tag = value, inherited tags included (retainDays, table, boundedContext)
  4. A required stereotype the tool supplies, with its tags (<<owned>> team = checkout, on Order and OrderLine)
  5. Attributes that apply a stereotype, listed with it in front and their tags in braces, a long row cut with an ellipsis (<<column>> placedAt)
  6. A profile application: dashed, an open arrowhead at the profile, <<apply>> (sales to BookshopConventions, sales to Audit)
  7. Profiles drawn as boxes titled <<profile>> (BookshopConventions, Audit)
  8. Metaclass references with <<metaclass>> and no compartment (Class, Property, Package)
  9. Stereotypes with <<stereotype>> and their tag definitions as attribute rows (team: String [0..1], indexed: Boolean = false)
  10. An extension marked required: a solid line, a filled triangle at the metaclass, {required} as its label (owned to Class)
  11. Plain extensions to three different metaclasses (record to Class, column to Property, module to Package)
  12. An abstract stereotype, its name in italics (record)
  13. Generalizations between stereotypes, two deep (aggregateRoot to entity to record)
  14. An enumeration owned by the profile, the type of a tag (ColumnKind, typing column's kind)
  15. A note with a dashed link to the abstract stereotype
  16. Two profiles defining one stereotype name (record), told apart by the qualified name Audit::record

In another setting ​

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

The same conventions, laid out right

Laid out right (direction right) instead of down: the same profiles, stereotypes and applying package.

Edit this page on GitHub
Pager
Previous pageDeployment
Next pageUse case