-
Key: SYSML17-251
-
Status: closed
-
Source: Airbus Group ( Mr. Yves Bernard)
-
Summary:
There is no clear statement saying how the expression that specifies the constraint is managed, even if we can imagine that the intent was to use the ownedRule for that purpose it's not formally stated.
Assuming ownedRule is used, it's not specified either how to deal with ConstraintBlocks that would have more than one ownedRule (since the current specification only consider "one" constraint only)
-
Reported: SysML 1.6 — Thu, 5 Sep 2019 14:35 GMT
-
Disposition: Duplicate or Merged — SysML 1.7
-
Disposition Summary:
Merge with SYSML17-252
The resolution to issue SYSML17-252 implies resolving this one first. For that reason its is convenient to merge them and to provide a common resolution that is specified as a resolution proposal for SYSML17-252
-
Updated: Thu, 22 Dec 2022 13:45 GMT
SYSML17 — Syntactical clarification for ConstraintBlock
- Key: SYSML17-251
- OMG Task Force: SysML 1.7 RTF