MagicDraw/Cameo does not explictly support tracking of satisfaction and verification of composite/compound requirements, but the "implied relations" facility can help.
TestCase and Verify example - callout style Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 16:01: Requirements engineering in SysML Slide kind SysML Block Definition Diagram (BDD)
A basic Requirement is an AbstractRequirement Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 16:01: Requirements engineering in SysML Slide kind UML Profile Diagram
The Burnish requirement is shown as having a Verify relationship to the BurnishTest test case using callout notation on the diagram, indicating that the Burnish requirement is verified by the BurnishTest test case. Source OMG Systems Modeling Language (SysML) 1.6
Figure 16-6: Linkage of a Test Case to a requirement (and Figure 16-7) 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 specification diagrams: 16 Requirements Slide kind hybrid diagram SysML Requirement Diagram SysML StateMachine Diagram
Figure 16-1: Abstract Syntax for Requirements Stereotypes 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 specification diagrams: 16 Requirements Slide kind UML Profile Diagram
