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!

A requirement verification usage is a subrequirement of the objective that is indicated by prefixing a requirement usage declaration with the keyword verify.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
34. Verification: Verification Case Definition Example.sysml
SysMLv2: Cameo 2026xHF2: ISSUE: Does not seem to automatically bind by default the subject of a verification case to its objective or the subject of the objective to its requirement verification usages
SysMLv2: Cameo 2026xHF2: TIP: A requirement verification usage of the objective of a verification cases lists under the require constraints compartment
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
In addition to assumed and required constraint usages allowed in any requirement usage ... the objective of a verification case may also have requirement verification usages, which indicate the requirements to be verified by the verification case.
Full quote
A requirement verification usage is a subrequirement of the objective that is indicated by prefixing a requirement usage declaration with the keyword verify.
Next snippet
As for an assumed or required constraint, the keyword verify can be used rather than verify requirement to declare a verified requirement using reference subsetting.
Related snippets
The result of a verification case is a verdict that can have the values pass, fail, inconclusive, or error.
In simple cases, the PassIf calculation definition from the VerificationCases library model ... can be used to obtain a pass or fail verdict based on a Boolean value.
Related snippets (backlinks)
In any case, since the requirement verification usage itself is a subrequirement, it is automatically considered a required constraint of its containing objective.
In addition, its subject is bound by default to the subject of the objective, which is itself bound to the subject of the verification case.
Visit also
Visit also (backlinks)