Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind TIP TOOL SysMLv1.x keywords Satisfy Verify AbstractRequirement::/satisfiedBy AbstractRequirement::/verifiedBy Keywords MagicDraw implied relationships MagicDraw SysML Cameo Systems Modeler Relates to Composite (a.k.a. "compound") Requirements Related notes [CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties Related notes (backlinks) [TIP]{SUGGESTED} SysML: Webel recommends use of an additional custom «requirementGroup» stereotype for compound Requirements that serve as owning Namespaces and are subject to the satisfaction policy that all child requirements must be satisfied. Related snippets (extracts) [SysML-1.6] The default interpretation of a compound requirement, unless stated differently by the compound requirement itself, is that all its subrequirements shall be satisfied for the compound requirement to be satisfied. [SysML-1.6] A composite requirement can contain subrequirements in terms of a requirements hierarchy, specified using the UML namespace containment mechanism. This relationship enables a complex requirement to be decomposed into its containing child requirements. [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 [SysML-1.6] Compound requirements can be created by using the nesting capability of the class definition mechanism. Visit also Visit also (backlinks) Flags
