-
Key: SYSML21-12
-
Status: open
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
The constraint checkSatisfyRequirementUsageBindingConnector requires that "A SatisfyRequirementUsage must have exactly one ownedMember that is a BindingConnector between its subjectParameter and some Feature other than the subjectParameter." However, in the textual notation for a SatisfyRequirementUsage, a *by* is parsed as a FeatureValue binding from the owned subject of the SatisfyRequirementUsage to the *by* clause Expression (see 8.2.2.21.2 Requirement Usages). But the implied BindingConnector for a FeatureValue will then be owned by the subject parameter, not by the SatisfyRequirementUsage, so the checkSatisfyRequirementUsageBindingConnector constraint will be violated.
-
Reported: SysML 2.0b2 — Fri, 9 May 2025 22:07 GMT
-
Updated: Thu, 11 Sep 2025 22:36 GMT
SYSML21 — Constraint checkSatisfyRequirementUsageBindingConnector is not correct
- Key: SYSML21-12
- OMG Task Force: Systems Modeling Language (SysML) 2.1 RTF