-
Key: SYSML16-345
-
Status: closed
-
Source: Airbus Group ( Mr. Yves Bernard)
-
Summary:
In the current SysML specification, every constraint defined as part of a stereotype is identified by a number.
However the ownedRule property is not ordered. So this numbering does not make sense. Using meaningful names for all those constraints - just like UML does - would be more appropriate.
-
Reported: SysML 1.5 — Thu, 7 Sep 2017 14:28 GMT
-
Disposition: Duplicate or Merged — SysML 1.6
-
Disposition Summary:
To be merged with the formalization of SysML constraints (
SYSML16-274)To be merged with the formalization of SysML constraint which includes adding them explicitly in the model of the SysML profile: a meaningful name will be proposed for each of those constraints.
-
Updated: Mon, 1 Apr 2019 18:17 GMT
SYSML16 — SysML stereotype constraints should be named rather than numbered
- Key: SYSML16-345
- OMG Task Force: SysML 1.6 RTF