Composite (a.k.a. "compound") 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 SysML Requirement Diagram
An entire specification can be decomposed into children requirements, which can be further decomposed into their children to define the requirements hierarchy. Source OMG Systems Modeling Language (SysML) 1.6
A composite requirement may state that the system shall do A and B and C, which can be decomposed into the child requirements that the system shall do A, the system shall do B, and the system shall do C Source OMG Systems Modeling Language (SysML) 1.6
Figure 4-3: SysML Package Structure 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: 04 Language and Architecture Slide kind SysML Package Diagram
SysML-1.6: Figure D.3: Would 'HSUV Interfaces' be better higher up directly under 'HSUV Model' (instead of under 'HSUV Structure')?
The containment (cross hair) relationship, for purposes of this example, refers to the practice of decomposing a complex requirement into simpler, single requirements. Source OMG Systems Modeling Language (SysML) 1.6
