Issue 15882: SysML primitive value types (sysml-rtf) Source: No Magic, Inc. (Mr. Nerijus Jankevicius, nerijus(at)nomagic.com) Nature: Uncategorized Issue Severity: Summary: 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. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: December 8, 2010: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== ted-NM: yes From: Nerijus Jankevicius Subject: SysML primitive value types Date: Wed, 8 Dec 2010 14:34:10 +0200 To: sysml-rtf@omg.org X-Mailer: Apple Mail (2.1082) X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id oB8CDhM0001143 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. What do you think? -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- Subject: RE: SysML primitive value types Date: Wed, 8 Dec 2010 09:03:18 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SysML primitive value types Thread-Index: AcuW1D/1pQC402WyQbyv+KNjDvVkNAAJVBHA From: "Pete Rivett" To: "Nerijus Jankevicius" , X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id oB8GgOmx007041 SysML should reuse UML directly - the whole UML4SysML approach was IMHO a mistake. BTW UML does not have a Real. Pete -----Original Message----- From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] Sent: Wednesday, December 08, 2010 4:34 AM To: sysml-rtf@omg.org Subject: SysML primitive value types 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. What do you think? -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- MagicDraw - UML made simple! X-Trusted-NM: yes Subject: Re: SysML primitive value types From: Nerijus Jankevicius Date: Wed, 8 Dec 2010 19:50:55 +0200 Cc: To: "Pete Rivett" X-Mailer: Apple Mail (2.1082) Pete, UML 2.4 has. -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- MagicDraw - UML made simple! On Dec 8, 2010, at 7:03 PM, Pete Rivett wrote: > SysML should reuse UML directly - the whole UML4SysML approach was IMHO > a mistake. > BTW UML does not have a Real. > > Pete > > -----Original Message----- > From: Nerijus Jankevicius [mailto:nerijus@nomagic.com] > Sent: Wednesday, December 08, 2010 4:34 AM > To: sysml-rtf@omg.org > Subject: SysML primitive value types > > 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. > > What do you think? > > -- > Nerijus Jankevicius > SysML Product Manager > OMG-Certified UML Professional > No Magic Europe > Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, > Kaunas > Phone: +370-37-324032 Fax: +370-37-320670 > e-mail: nerijus@magicdraw.com > WWW: http://www.magicdraw.com > -- > MagicDraw - UML made simple! > X-Trusted-NM: yes From: Nerijus Jankevicius Subject: Re: SysML primitive value types Date: Thu, 16 Dec 2010 00:26:18 +0200 To: Juergen Boldt X-Mailer: Apple Mail (2.1082) yes, for SysML 1.3 RTF Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- MagicDraw - UML made simple! On Dec 15, 2010, at 11:57 PM, Juergen Boldt wrote: issue? -Juergen At 07:34 AM 12/8/2010, you wrote: 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. What do you think? -- Nerijus Jankevicius SysML Product Manager OMG-Certified UML Professional No Magic Europe Savanoriu pr. 363, LT 49425 Kaunas, Lithuania P.O. box 2166, LT- 3000, Kaunas Phone: +370-37-324032 Fax: +370-37-320670 e-mail: nerijus@magicdraw.com WWW: http://www.magicdraw.com -- MagicDraw - UML made simple! MagicDraw - UML made simple!