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.
What it shows
In the order you find them in the picture:
- The req frame with its pentagon header, the view's subject a package: req [Package] Online bookshop [What the shop must do]
- Requirements as classifiers, <<requirement>> over the name and an id and text compartment (SHOP-1 Online ordering)
- 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)
- All five requirement kinds over the name: <<functionalRequirement>>, <<performanceRequirement>>, <<interfaceRequirement>>, <<physicalRequirement>>, <<designConstraint>>
- The risk and verifyMethod rows of an extended requirement (Search: risk = low, verifyMethod = demonstration)
- A long text wrapped over several rows
- <<copy>> from a requirement to the regulation whose text it repeats (Refunds to Distance selling refunds)
- <<satisfy>> from a block to a requirement (Warehouse satisfies Parcel size, Storefront satisfies Checkout)
- <<refine>> from a block to a requirement (Search index refines Search)
- <<deriveReqt>> from a derived requirement to its source (Short checkout from Checkout)
- <<trace>> between two requirements (Gateway interface to Checkout)
- A package drawn as a box holding requirements and a block (Payments)
- A text cut to 4 rows then "+6 more" (No stored card numbers,
presentrows) - <<verify>> from a test case to a requirement, <<testCase>> over its name (Search load test, Checkout walk-through)
- A <<problem>> note and a <<rationale>> note, each linked to its requirement by a dashed line