MDG Profile derived from sysml in V14

[PeterHeintz]

Hi,
I have a profile derived from SysML. Within that, I have derived stereotypes but also I use SysML toolboxes. Currently I refer within my MDG by “SysML1.4::” to the SysML version.

What do I have to do in EA V14?
“SysML1.4::” or SysML1.5::?

[Nizam]

Wow thats interesting,  I can see SysML 1.1 , 1.2, 1.3 and 1.5, just noticed 1.4 is missing, looks like we've to change to refer to either 1.3 or 1.5.

[Geert Bellekens]

Wow thats interesting,  I can see SysML 1.1 , 1.2, 1.3 and 1.5, just noticed 1.4 is missing, looks like we've to change to refer to either 1.3 or 1.5.

One of the Sparxians commented about this a while ago.
IIRC there were so little differences between 1.4 and 1.5 that they simply renamed it instead of having them as separate versions.
So version 1.4 is now version 1.5.

I'm not sure how or if you need to you upgrade from 1.4 to 1.5

Geert

[Nizam]

Thanks, Geert, I guess as an end user it must be fine, just some of my extended profiles use 1.4, I might have to rename/fix them. But That is a problem I've to tackle when (and if) the clients try to move to 14.

[PeterHeintz]

Yes, that Sparx answer was on my issue. However, 1.4 is still alive, you see it in the gui, when you have to create a sysml1.4 Block diagram within sysml1.5 MDG.
So I fear that sometimes I have to use 1.4 and sometimes 1.5.
Just one more inconsistency increase.

Hi Sparxians,
please give assistance.

[Eve]

The ID for the profile and technology are both still SysML1.4. This is what should be used when referencing the technology from another one or from code. (eg. A SysML stereotype would still be prefixed with "SysML1.4::".

SysML 1.5 is the name, and that's what should be displayed to users.

It looks like the metamodel views are currently saying that they belong to SysML1.4. They don't have an alias mechanism in place, it looks like they should.

[PeterHeintz]

Thank you Simon!