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
The example in Figure 16-6 is taken from the automotive safety domain, and shows a Burnish requirement contained in the NHTSASafetyRequirements requirement. Note that the text of the Burnish requirement indicates a specific sequence of steps and transitio Source OMG Systems Modeling Language (SysML) 1.6
Figure 16-5 illustrates the use of the Copy dependency to allow a single requirement to be reused in several requirements hierarchies. The master tag provides a textual reference to the reused requirement. Source OMG Systems Modeling Language (SysML) 1.6
The diagram in Figure 16-3 shows derived requirements and refers to the design elements that satisfy them. The rationale is also shown as a basis for the design solution. Source OMG Systems Modeling Language (SysML) 1.6
The diagram in Figure 16-2 shows an example of a compound requirement decomposed into multiple subrequirements. Source OMG Systems Modeling Language (SysML) 1.6
The allocation table can also be shown using a sparse matrix style as in the following example shown in Figure 15-9. Source OMG Systems Modeling Language (SysML) 1.6
The table shown in Figure D.40 is provided as a specific example of how the «allocate» dependency may be depicted in tabular form, consistent with the automotive example above. Source OMG Systems Modeling Language (SysML) 1.6
The need also arises, when adding detail to a structural model, to allocate a connector (at a more abstract level) to a part (at a more concrete level). Source OMG Systems Modeling Language (SysML) 1.6
