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

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
16:01: Requirements engineering in SysML
SysML keywords
Requirement
Satisfy
Block
Keywords
Slide kind
MagicDraw/Cameo: relationship dependency matrix
MagicDraw/Cameo: relationship matrix

This Satisfy Requirement Matrix for the Hybrid SUV sample problem has a restricted Row Scope and Column Scope, and shows only Column Element Type Block, and it only shows Requirement and Block elements that have Satisfy relations.

It has been combined with a mini-overview of the relevant Satisfy cases:

Click on the image to view it full size
There are six hits. The first two are obvious, direct hits shown with small solid arrows in the matrix cells:
  1. Block BrakeSystem has a direct Satisfy to Requirement Master Cylinder Efficacy.
  2. Subsystem Block PowerSubsystem has a direct Satisfy to Requirement Power.
But what about the other four, shown with small dashed arrows? Those are implied Satisfy relations:
MagicDraw/Cameo: The default 'Implied Satisfy' relation will claim a Requirement is satisfied by any direct composite aggregation parent Block or composite aggregation ancestor Block of a part property
  1. Block BrakeSystem has an implied Satisfy to Requirement LossOfFluid because it has a part m:MasterCylinder that directly satisfies LossOfFluid.
  2. Block BrakeSystem has an implied Satisfy to Requirement Reservoir because it has parts l1:BrakeLine and l2:BrakeLine that directly satisfy Reservoir.
  3. The system Block HybridSUV has an implied Satisfy to Requirement Power via PowerSubsystem, because it has a part p:PowerSubsystem.
  4. The domain Block AutomotiveDomain then has an implied Satisfy to Requirement Power via HybridSUV, because it has a part hsuv:HybridSUV.
We show next how to also include the part properties.
Up next
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)
Notes
[DISPLAY, FEATURE, TIP, WARNING] MagicDraw/Cameo: In a Dependency Matrix the mode 'Show Element = All' can lead to very large matrices (but it enables you to interactively create relationships for elements that don't yet have any).
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties
[CONVENTION, FEATURE, TIP, TOOL] MagicDraw/Cameo: The default 'Implied Satisfy' relation will claim a Requirement is satisfied by any direct composite aggregation parent Block or composite aggregation ancestor Block of a part property
[TIP, TOOL] MagicDraw/Cameo: Learn how to effectively use and customise the powerful table, matrix, and relation map diagrams and how to create custom queries, implied relations, and custom properties. It will open up a whole new world of enjoyable power modelling!
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has powerful relationship Dependency Matrix diagrams, and in many cases one can assign or remove relationships directly in the cells of the matrix just by clicking!
Snippets (quotes/extracts)
  [SysML-1.6] A Satisfy relationship is a dependency between a requirement and a model element that fulfills the requirement.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
Visit also
Visit also (backlinks)
SysML: MagicDraw/Cameo: Use query view tables, matrices, and maps, use them a lot! They help communicate well with other stakeholders. Learn how to use the Generic Table diagram type, custom relations, Simple Navigation & Metachain Navigation (expert)!
Nobody (informed) said that SysML (or even UML) modelling and MBSE is only about graphical modelling, notations, and diagrams! Information can be extracted in many different ways and presented in many different formats from the underlying model!