In this case we'll assert that every VolumeControl of this home entertainment system meets the requirement, so we won't also specify that the volumeControl:VolumeControl part of block SoundSystem also satisfies the Requirement.

We'll see later how we can then enforce a satisfaction policy rules such as:

'If a part property is typed by a block that satisfies the requirement, by default the part property also satisfies the requirement'

'If a block has a part that directly satisfies a requirement, the block also indirectly satisfies the requirement'

SysML does not specify many rules for Satisfaction because:

The OMG SysML language deliberately does not aim to restrict users and tools to one strict systems engineering methodology; it provides flexible capabilities and options for use by many model-based systems engineering methodologies and tools.

However, you get some nice tool help for such rules:

Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties

We'll explore implied satisfaction in more detail a bit later when we see how use the Satisfy Requirement Matrix system in the tool, but next we look quickly at the Trace relationship.

Up next

Requirements and the Trace relationship - metamodel

Notes

[COMPLICATION] In SysML more than one NamedElement can help Satisfy a single Requirement (which presents challenges for verifying satisfaction of Requirements). This is a conceptual challenge for requirements engineering in general, not just SysML!

[NAMING, POLICY]{STRONG} Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names)

[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties

[ASSERTION, TIP] The OMG SysML language deliberately does not aim to restrict users and tools to one strict systems engineering methodology; it provides flexible capabilities and options for use by many model-based systems engineering methodologies and tools.

Snippets (quotes/extracts)

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

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

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

Related slides (includes other tutorials)