Figure D.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy

Gallery
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Section
Section: SysML-1.6: HSUV sample
SysML keywords
HSUV sample problem
Requirement
DeriveReqt
Rationale
Probem
Refine
Keywords
Slide kind
SysML Requirement Diagram
Click on the image to view it full size
In the spec figure the StateMachine that refines the PowerSourceManagement block is called HSUV Operational States, in this trail it is verbosely named after the figure: Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”
Up next
Figure D.13 - Acceleration Requirement Relationships
Notes
[NAMING, POLICY]{SUGGESTED} Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools)
[CAPABILITY, TOOL] In MagicDraw/Cameo one can "call-out" many element properties (and metamodel properties) into a Note using the Edit Compartments context menu item
[CAPABILITY, TOOL] In MagicDraw/Cameo one can display many element properties (and metamodel properties) directly in compartments on most element symbols
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.12 shows a set of requirements derived from the lowest tier requirements in the HSUV specification.
  [SysML-1.6] Derived requirements, for the purpose of this example, express the concepts of requirements in the HSUVSpecification in a manner that specifically relates them to the HSUV system.
  [SysML-1.6] Various other model elements may be necessary to help develop a derived requirement, and these model element may be related by a «refinedBy» relationship.
  [SysML-1.6] Note how PowerSourceManagement is “RefinedBy” the HSUVOperationalStates model (Figure D.8).
  [SysML-1.6] Note also that rationale can be attached to the «deriveReqt» relationship. In this case, rationale is provided by a referenced document “Hybrid Design Guidance.”
  [SysML-1.6] The Refine stereotype specializes UML4SysML Refine and DirectedRelationshipPropertyPath to enable refinements to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets.
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)
The SysML Problem and Rationale extensions of Comment
A custom Comment extension with tagged values metadata