Element types and stereotypes issue

[Lars]

Hi!

I've been using a profildefinition to apply a "Function" stereotype to elements of type Activity. The profile simply defines a set of attributes which should apply for the element as such.

It's all been working fine! But now all the sudden i recognize that a number of the elements, that previously have been configured as type Activity and with stereotype Function, now lists in the properties dialog as Function (type) with Function (stereotype).

This issue is especially obvious when using the Relationship matrix, since all the concerned elements no longer appear in the list when I choose Activity-elements. Logically, when i swithc to Function-elements the rest of them appear...

I've been trying VB-scripts to list the type of element for all concerned elements, and from the result I could see that all elements are listed with type Activity.

This is really confusing! Any thoughts?

Lars

[qwerty]

I guess you should report a bug. A colleague noticed that the Device element from the toolbox appears as Node but with metatype Device. In the diagram it is shown as <<device>> node but in the browser as node. Somehow EA does some internal special treatment which leads to confusion. Probably in your case the Function is similarly.

q.

[Eve]

Did you happen to set the _metatype attribute on your stereotype definition?

The behavior you are describing is exactly what that attribute is designed to do.

Please see http://www.sparxsystems.com/enterprise_architect_user_guide/9.3/standard_uml_models/defining_a_stereotype_as_a_met.html

[Lars]

Hi!

Not from what I know, but that could be one solution (at least for me).

Using the _metatype attribute I can make all my Activities appear as Functions in the relationship matrix. That's possibly even better than before, since what I'm actually trying to model is system functions and not activities.

Great many thanks!