-
Key: SYSML2-553
-
Status: open
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
In 8.3.20.9 RequirementUsage, the checkRequirementUsageObjectiveRedefinition constraint requires that "A RequirementUsage whose owningFeatureMembership is a ObjectiveMembership must redefine the objectiveRequirement of each CaseDefinition or CaseUsage that is specialized by the owningType of the RequirementUsage." However, the objectiveRequirement property of a CaseDefinition (see 8.3.21.2) or a CaseUsage (see 8.3.21.3) is derived to be only the owned objective of the case. This means that, if a case declares an owned objective, but specializes a case with an inherited objective, then checkRequirementUsageObjectiveRedefinition will actually not be satisfiable.
-
Reported: SysML 2.0b1 — Wed, 22 Nov 2023 04:58 GMT
-
Updated: Mon, 8 Apr 2024 18:20 GMT
SYSML2 — checkRequirementUsageObjectiveRedefinition is incorrect
- Key: SYSML2-553
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF