Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

For the overall requirement to then be satisfied, all such composite ... requirements must be satisfied.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
SysMLv2: Cameo: LIMITATION: Does not list requirement usages (subrequirements) that are owned under the assert constraints compartment.
Requirements Examples: HSUVRequirements.sysml
Requirements Examples: RequirementDerivationExample.sysml
Requirements Examples: VehicleRequirementDerivation.sysml
Source
OMG Systems Modeling Language TM (SysML®) Version 2.0 formal/2025-09-03 (Sep 2025)
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
Keywords
A requirement definition or usage may also reference another requirement usage as a required constraint.
Full quote
For the overall requirement to then be satisfied, all such composite ... requirements must be satisfied.
Next snippet
Webel: Would read better as 'all such composed ... requirements must be satisfied'
For an explanation visit also:
SysML2.0: Inconsistent use of the term 'composite' used to describe BOTH elements that own usages of the corresponding kind AND for usages with isComposite=true (as opposed to referential usages with isComposite=true). Suggest use instead 'composed'.
This snippet is a variant form (for embedding on this site) of:
SysML2.0: 'For the overall requirement to then be satisfied, all such composite or referenced requirements must be satisfied.'
Related snippets
A composite requirement usage nested in a requirement definition or usage is a subrequirement of the containing requirement definition or usage.
A requirement definition or usage may be decomposed into nested requirement usages, which may themselves be further decomposed.
Since a requirement usage is a kind of constraint usage, any nested composite requirement usage is automatically considered to be a required constraint of the containing requirement definition or usage.
For the overall requirement to then be satisfied, all such composite or referenced requirements must be satisfied.
Related snippets (backlinks)
Visit also
Visit also (backlinks)