Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

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

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
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.
SysML-1.6: Refers to both 'composite requirements' and 'compound requirements' (clearly as identical concepts)
Composite (a.k.a. "compound") Requirements
MagicDraw/Cameo does not explictly support tracking of satisfaction and verification of composite/compound requirements, but the "implied relations" facility can help.
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
Namespace
Element::owner
containment
SysML keywords
Requirement
SysML Requirements Diagram
composite (compound) requirement
Keywords
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.
Full quote
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
Next snippet
An entire specification can be decomposed into children requirements, which can be further decomposed into their children to define the requirements hierarchy.
SysML-1.6: Refers to both 'composite requirements' and 'compound requirements' (clearly as identical concepts)
Related snippets
A requirement specifies a capability or condition that must (or should) be satisfied. A requirement may specify a function that a system must perform or a performance condition a system must achieve.
A requirement specifies a capability or condition that must (or should) be satisfied.
A requirement may specify a function that a system must perform or a performance condition that a system must satisfy.
SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements.
The requirements diagram described in this clause can depict the requirements in graphical, tabular, or tree structure format. A requirement can also appear on other diagrams to show its relationship to other modeling elements.
Several requirements relationships are specified that enable the modeler to relate requirements to other requirements as well as to other model elements.
Compound requirements can be created by using the nesting capability of the class definition mechanism.
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.
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.
Related snippets (backlinks)
Visit also
Visit also (backlinks)