Derived requirements and the DeriveReqt relationship - compartment styles

Apart from using a callout into a Note as shown in the previous slide, the MagicDraw SysML Plugin and Magic Cyber-Systems Engineer ^® (Cameo Systems Modeler^®) tools offer two additional ways to show information about derived requirement relationships directly on Requirement symbols:

Click on the image to view it full size

The upper example shows tagged value style.

The lower example shows element property compartment style.

Sometime, rather than deriving a Requirement from another, we wish instead to Refine a Requirement with another kind of model element, as shown next .

Up next

Refining requirements

Notes

[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] A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement.

[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] SysML has added some notational extensions to represent stereotype properties in compartments as well as notes.

Visit also

Visit also (backlinks)

Related slides (includes other tutorials)