Extending <<Trace>>:stereotype ISSUE

[Hermes]

Hi all,

I've tried to extend <<Trace>> metaclass, creating a new stereotype (call it <<MyTrace>>) but I've found a problem:
links created with this new stereotype will be referenced as <<Trace,MyTrace>> (in the StereotypeEx EA attribute, Class: EA.Connector)

and simply referenced as <<Trace>> in the Stereotype attribute.

Why this happens?

Why if I extend other elements such as <<dependency>> then the Stereotype value will be <<MyStereotype>> (as I'd like to be) instead of <<Dependency>> as it works for <<trace>>?

Can I extend <<Trace>> metaclass obtaining a stereotype referenced as <<MyStereotype>>?

I'm a bit confused  

Thankyou all

/D

[KP]

A trace relationship is actually a Dependency with the «trace» stereotype. If you extend the trace relationship, you will end up with a Dependency with two stereotypes. One of the problems with this in EA is that synchronizing tagged values only works on the primary stereotype, so won't work with your new stereotype. So my advice: consider whether you would be better off just extending Dependency.

[Hermes]

Thankyou KP for your advice

I think I will see if I can write my Sync function.. of course, if I can't do that with a reasonable amount of time, I'll follow your suggestion.

(This because I'm writing a TRACEability addin, and <<trace>> stereotype comes handy )

/D