Legacy Issue Number: 15882
Source: Dassault Systemes ( Nerijus Jankevicius)
We have issues with SysML primitive value types - Real, Integer, Boolean, String etc.
The problem is that these types are not inherited from corresponding UML primitive types - Real, Integer, Boolean, String.
That means, UML tool can't understand, what kind of ValueSpecification should be created for values of properties typed by these value types.
Should it be LiteralString or LiteralInteger or OpaqueExpression?
Constraints can't check if slot values are compatible with property types, as it is not clear what kind of value specification it should be also.
There are issues in parametrics solving also, as values must be compatible with property types.
I think, SysML primitives must be directly inherited from UML primitives - Real subtype of UML Real, String subtype of UML String etc.
Reported: SysML 1.4 — Wed, 8 Dec 2010 05:00 GMT
Disposition: Resolved — SysML 1.7
Specialize SysML primitive values types from UML primitive value types
The SysML primitive values types have no relationship to the UML primitive value types and there is also no relationship to the Literal metaclasses. Therefore, it is not possible to define values for properties typed by a SysML primitive value type.
A solution is to inherit the SysML primitive value types from the appropriate UML primitive value types.
Updated: Thu, 22 Dec 2022 13:45 GMT
- 20190318_142807.jpg 1.09 MB (image/jpeg)