-
Key: SYSML21-300
-
Status: open
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
The constraint checkRequirementUsageSubrequirementSpecialization requires that a composite RequirementUsage whose ownedType is a RequirementDefinition or RequirementUsage specialize RequirementCheck::subrequirements. However, RequirementCheck::subrequirements subsets RequirementCheck::constraints, which is the set of required constraints of the requirement. So it doesn't make sense for a RequirementUsage to specialize subrequirements if it is owned as an assumed constraint.
-
Reported: SysML 2.0b2 — Sat, 28 Jun 2025 20:31 GMT
-
Updated: Sat, 20 Sep 2025 06:51 GMT
SYSML21 — Constraint checkRequirementUsageSubrequirementSpecialization needs to exclude assumed requirements
- Key: SYSML21-300
- OMG Task Force: Systems Modeling Language (SysML) 2.1 RTF