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

Class diagram ​

A bookshop's sales domain: who orders, what an order holds, how it is paid for, and the shared types the classes use, in one class diagram. The page below opens on it, A bookshop's sales domain, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. A note (a comment with a folded corner) linked to Order by a dashed line
  2. Packages drawn as boxes holding their classes, their names in tabs: sales, payments with card nested inside it, shared
  3. A package-qualified name: catalog::Book, whose package the view does not show
  4. A class with a stereotype: <<entity>> over Order
  5. Attributes with all four visibilities: + public, - private, # protected, ~ package
  6. A derived attribute (/total), a default (status = draft) and a multiplicity on a member (name: String [0..1])
  7. A static attribute and a static operation, underlined (placed, find)
  8. Operations with parameters, a return type, and parameter directions (in by, out was)
  9. A class cut to 3 rows then "+2 more" (Customer, present rows)
  10. A compartment collapsed (Book's operations, present collapsed)
  11. An association with a label, role names, multiplicities and a navigable end (Customer places orders 0..*)
  12. An association navigable at both ends (Customer wishes for Book: readers *, wishlist *)
  13. Composition, a filled diamond (Order owns its lines 1..*)
  14. Aggregation, a hollow diamond (Order and its payments 0..*)
  15. An enumeration with its literals (OrderStatus)
  16. An interface and an interface realization, dashed with a hollow triangle (Order realizes Payable)
  17. An abstract class and an abstract operation, in italics (Payment, settle())
  18. Generalization, a hollow triangle at the general class, two subclasses sharing it (CardPayment, GiftCardPayment)
  19. A usage, dashed with an open arrowhead and <<use>> (CardPayment uses CardGateway)
  20. A dependency with the <<use>> stereotype (Payable on Money)
  21. A dependency with a label (Book keyed by Isbn)
  22. A data type (<<dataType>> Money) and a primitive type (<<primitive>> Isbn)

In another setting ​

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

The same domain, laid out right

Laid out right (direction left at its default) instead of down: the same classes, lines and presentation options; the main view runs down, so that generalizations put the general class above.

Edit this page on GitHub
Pager
Previous pageMap
Next pageObject