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

Requirement diagram ​

What an online bookshop must do: its ordering requirements broken down by containment, a payments package, a requirement copied from a regulation, and the blocks that satisfy and the test cases that verify them, in one req frame. The page below opens on it, What the shop must do, live: pan, zoom, select and go into the cards that stack.

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

What it shows ​

In the order you find them in the picture:

  1. The req frame with its pentagon header, the view's subject a package: req [Package] Online bookshop [What the shop must do]
  2. Requirements as classifiers, <<requirement>> over the name and an id and text compartment (SHOP-1 Online ordering)
  3. Containment, a line with a crosshair at the owner's end, two levels deep (Online ordering holds Search, Checkout and Refunds; Search holds Search speed)
  4. All five requirement kinds over the name: <<functionalRequirement>>, <<performanceRequirement>>, <<interfaceRequirement>>, <<physicalRequirement>>, <<designConstraint>>
  5. The risk and verifyMethod rows of an extended requirement (Search: risk = low, verifyMethod = demonstration)
  6. A long text wrapped over several rows
  7. <<copy>> from a requirement to the regulation whose text it repeats (Refunds to Distance selling refunds)
  8. <<satisfy>> from a block to a requirement (Warehouse satisfies Parcel size, Storefront satisfies Checkout)
  9. <<refine>> from a block to a requirement (Search index refines Search)
  10. <<deriveReqt>> from a derived requirement to its source (Short checkout from Checkout)
  11. <<trace>> between two requirements (Gateway interface to Checkout)
  12. A package drawn as a box holding requirements and a block (Payments)
  13. A text cut to 4 rows then "+6 more" (No stored card numbers, present rows)
  14. <<verify>> from a test case to a requirement, <<testCase>> over its name (Search load test, Checkout walk-through)
  15. A <<problem>> note and a <<rationale>> note, each linked to its requirement by a dashed line
Edit this page on GitHub
Pager
Previous pageInformation flow
Next pageBlock definition