Solved: Can't add property to profile

[Hermelin]

Hi,

I have a MDG profile where I try to add the Mataclass Property. When I do it shows up for a split second and then changes to the metaclass Part. What to do?

Thank you for your help!

Edit after confirmation from Sparx: The bug appears in EA 10.1009 in combination with SysML 1.3 MDG. A workaround is to disable SysML 1.3 and enable SysML 1.2 or 1.1.

[KP]

There are four ways to represent a UML Property in EA: part, attribute, port or association end. Try extending whichever representation you want to see.

(I guess from your other thread that you are using an old version of EA. More recent versions of EA allow you to extend Property.)

[Hermelin]

Thank you for your reply, but let me rephrase my question.

I'm creating an MDG that implements the MODAF metamodel (M3). M3 uses <metaclass> Property to extend several stereotypes.  Thus, I need to add the Metaclass Property to my profile so I can extend it to relevant stereotypes.

As usual, I add a new metaclass by draging Metaclass from the Profile toolbox. I choose Property from the Core Elements. But, instead of a Property metaclass I get the Part metaclass. I find this an rather unexpected behavior. I have found no other metaclass that behaves this way.

(Using EA 10. Build 1009)

[qwerty]

For me I see Property twice in the list  :-? But both produce a Property meta class.

q.

[Hermelin]

I also have had two Property in the list , both producing Part. Nowdays  though I only have one Property. Might have changed after I tried a repair of EA.

[qwerty]

There seems to be something strange. I just upgraded to the latest build. Still two Property entries.

Can't you manually change the properties of the meta class?

And you should report a bug...

q.

[Hermelin]

Thank you for the help.

I have filed a bug report. THe issue appears on two seperate installations (Build 1009 & Build 1008), but not on my colleague's installation. My Build 1008 installation is barebone, except the addin EA Navigator, so I can't fathom, if it's my fault, what I have done with the installations.  I have tried to unistall EA, remove all traces with regedit. And then do a clean installation. But still no Property for me.


q: Well, I wouldn't really know what to change manually, except the name... So that is possible? I reckoned EA did some background magic, depending on the chosen metaclass...

[qwerty]

The only thing they do is creating a class with a name, a stereotype and a couple of attributes. You can do that manually as well if you know the parameters.

q.

[Hermelin]

I see. Thank you for the help q!

I decided to do it manually, so I created a model with the metaclass Property on a colleague's computer to be able to see how it was defined.  

I then imported that via XMI to my model. Lo and behold, the Property elements that I previously created, which got named Part, suddenly changed name to Property.

Though, I still can't create (from the toolbox) a metaclass myself that get the right name.

[qwerty]

Honestly, that rather looks like an add-in running wild. Try to turn them off.

q.

[Hermelin]

Sparx have confirmed it as a bug that appears when using the SysML 1.3 MDG.  A workaround is to use an older version of SysML.

Thanks for the input!