The non-normative extended requirements 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
Webel has suggested that SysMLv2 should support verification of each individual claim of more than one Element helping to Satisfy a Requirement.
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!
The Verify relationship is shown on Figure 16-7 using callout notation anchored to the diagram frame, which indicates that the BurnishTest test case verifies the Burnish requirement. Source OMG Systems Modeling Language (SysML) 1.6
Figure 17-1 [Figure 16-7] is a state machine diagram of the BurnishTest test case, which expresses the textual sequence and criteria of the Burnish requirement in state machine form. Source OMG Systems Modeling Language (SysML) 1.6
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
TestCase::1_return_verdictkind The type of return parameter of the stereotyped model element shall be VerdictKind. (note this is consistent with the UML Testing Profile). Source OMG Systems Modeling Language (SysML) 1.6
A test case is a method for verifying a requirement is satisfied. Source OMG Systems Modeling Language (SysML) 1.6