Figure 16-3: Links between requirements and design

This trail version of this figure shows some additional callout information, as well as showing some additional element properties in the Requirement symbol compartments.

It also show some additional Satisfy relationships from part properties to Reservoir

Up next

Figure 16.4: Requirement satisfaction in an internal block diagram

Notes

[NAMING, TOOL] MagicDraw/Cameo: By implementation the name of some Stereotype attributes and operations is UpperCase instead of lowerCase like in the UML and SysML specs

[ISSUE] SysML-1.6: in 'Figure 16-3: Links between requirements and design' on block BrakeSystem the part 'r:BrakeLine' should probably be 'r:RearBrake'

[DISPLAY, QUESTION, STYLE, TOOL] MagicDraw/Cameo: How disable icons in requirement relationship compartments and tagged values compartment on Requirement symbol?

Snippets (quotes/extracts)

[SysML-1.6] The diagram in Figure 16-3 shows derived requirements and refers to the design elements that satisfy them. The rationale is also shown as a basis for the design solution.

[SysML-1.6] A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement.

[SysML-1.6] For example, a system requirement may be derived from a business need, or lower-level requirements may be derived from a system requirement.

[SysML-1.6] As with other dependencies, the arrow direction points from the derived (client) requirement to the (supplier) requirement from which it is derived.

[SysML-1.6] DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement.

[SysML-1.6] DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement.

[SysML-1.6] A Satisfy relationship is a dependency between a requirement and a model element that fulfills the requirement.

[SysML-1.6] As with other dependencies, the arrow direction points from the satisfying (client) model element to the (supplier) requirement that is satisfied.

[SysML-1.6] Satisfy::getSatisfies (in ref : NamedElement) : AbstractRequirement [0..*]

[SysML-1.6] DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement.

[SysML-1.6] Satisfy::1_supplier_is_requirement The supplier shall be an element stereotyped by any subtype of «AbstractRequirement».

Visit also

Visit also (backlinks)

Related slides (includes other tutorials)

Related slides (backlinks, includes other tutorials)

A most basic Requirement with a 'name', an 'id', and 'text'

A basic Requirement is an AbstractRequirement

Derived requirements and the DeriveReqt relationship

Derived requirements and the DeriveReqt relationship - compartment styles

Refining requirements

Satisfying Requirements and the Satisfy relationship

Requirements and the Trace relationship - metamodel

Trace used for model element elicitation - callout style

Trace used for model element elicitation - tagged value and element property styles

TestCase and Verify metamodel

TestCase and Verify example - callout style

Composite (a.k.a. "compound") Requirements

The Copy relationship

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)

MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)

Flags