UML Profiles and same name stereotypes on different metaclasses

[Guillaume]

Hi,

I want to use let's say "MyType" stereotype on a number of elements e.g. a MyType SysML block and a MyType Part.
When I export the UML Profile, the resulting XML file is missing the parts' stereotypes definitions. It seems like EA doesn't like stereotype duplicates.

As a workaround I can create separate UML Profiles to embed in my MDG, but I was wondering if this is a known issue.

[Geert Bellekens]

Have you tried specializing both SysML stereotypes from your MyType stereotype?

IIRC that should work.

Geet

[Guillaume]

Hi Geert,

Sounds like a good idea except that I don't want the parts to have the tagged values set on the blocks.

[Geert Bellekens]

So you really want two different stereotypes with the same name?

In that case, I don't think that is possible (nor a good idea)

Geert

[qwerty]

A stereotype always belongs to a profile. The FQN is always unique. The non-FQ name might be ambiguous.

q.

[Paolo F Cantoni]

A stereotype always belongs to a profile. The FQN is always unique. The non-FQ name might be ambiguous.

q.

We ensure there is NO ambiguity.

Manage Complexity,
   .   .   Reduce Ambiguity,
   .   .   .   .   Eliminate Inconsistency! ^TM

Paolo

[Guillaume]

Thanks for the clarifications.
Consider a Hardware block, I wanted to have my SysML Block with a "Hardware" stereotype, and when I get the part's equivalent in the IBD, I would have liked to see this part with the "Hardware" stereotype as well.
As it currently stands, I have to differentiate the parts stereotype e.g. "Hardware part".

It's not a big issue and I'm keeping this approach based on your comments.