Requirements view

Edit online

The requirements view manages and traces the requirements, creates, and updates requirements with simplified workflows to set their properties, structure and relations with other elements.

Consider the following sample of a requirements view. This diagram includes two requirements: min milk level and min coffee bean level. These requirements are satisfied by the part coffee machine, represented by the satisfy edges.

The min milk level requirement has a requirement ID: <2.1>. It includes the following parameters:
Subject
coffee machine subj is bound to the part coffee machine.
Actor
machine user is bound to consumer.
Stakeholder
owner is bound to vending machine owner.
The following are the additional elements associated with this requirement:
  • An assume constraint coffee with milk defined to be { coffee machine subj.selectedCoffeeType === coffeeWithMilk }
  • An assume constraint machine is on, which references the constraint coffee machine is on, visualized by the «assume» edge.
  • A frame concern frames machineIsNotFaulty, which references the concern machineIsNotFaulty, visualized by the «frame» edge.

The property "Description" has the label "Requirement doc" for the following elements:
  • RequirementUsage
  • RequirementDefinition
  • SatisfyRequirementUsage
  • ConcernDefinition
  • ConcernUsage

Consider the following format: <actor> = <bound-element>. To create a binding between the parameter and the element, type the name of a resolvable element, after a "=" sign. To clear the binding remove the = <bound element> from the textual notation.