Show stereotypes of interfaces

[gweih]

I am new to EA and I just get started. I hope that this is an easy question to answer:
Within a component diagram I need to explcitly show the interfaces which the components expose. I also want to show the stereotypes of the interfaces in the diagram. How do I make the stereotypes visible? They only appear in the Project Browser, but not in the diagram. I figured out for all other elements (components, associations, etc.) how to show stereotypes but did not succeed for interfaces.
Any suggestions?  Thanks!

[thomaskilian]

Have you checked the first 3 diagram properties? If they are set, please tell us which elements you use and what you expect.

[gweih]

Hi,
I set the following component diagram options:
Use Stereotype Icons: off
Show Element Stereotypes: On
Show Feature Stereotypes: On

In the Project Browser I see the name of the interface in the format <<stereotype>> Interface.
I would like to see the same in the diagram. Is this possible?

[thomaskilian]

As I told the first three should be on. If you tell EA to not use stereotypes it will do as requested.

[Eve]

I think you'll also need to 'Use rectangle notation' (you'll find that in the context menu for the interface when on a diagram) for the interface.

[gweih]

Hi, selecting the first option (Use Stereotype Icons) does not help. After all, I don't want a specific stereotype icon. I like the ball/socket notation.
All I want is to show a lollipop and next to it
"<<socket>> IP_Socket"
instead of simply
"IP_Socket".
The project browser shows the interface this way.

Thanks

[thomaskilian]

Hmm. I guess this is double action: showing the icon and the <<stereotype>>. I haven't seen that notation. Only either/or. The project browser doesn't need to comply to any UML diagram conventions.

[gweih]

Maybe I am not thinking UML enough. How would one differentiate different types of interfaces: function call, socket, shared memory or whatever? I have a legacy diagram that I want to transform to UML. This diagram works with different colors. I definitely want to capture all the information that's in there.

[thomaskilian]

You can use colors in EA diagrams as well.

[gweih]

OK, but then again we have some kind of custom notation. Isn't this what UML is intended to overcome?
Apparently, we have the case of multiple stereotypes here. When the ball-and-socket notation is used then this replaces one stereotype: <<interface>>. Is it assumed that there can only be the <<interface>> stereotype and hence it does not make sense to show both lollipop and stereotype?

[thomaskilian]

Actually I don't know why EA puts in a stereotype <<interface>> as its already a metaclass of type interface. If you use the circle notation an choose a meaningfull stereotype (like e.g. <<test>>) then you'll see the stereotype on the diagram.

[Eve]

The stereotype <<interface>> is actually a keyword as all interfaces drawn in rectangle notation should show it to distinguish the element from a class.  It doesn't need to be shown with the interface in circle notation.

[gweih]

That is understood. I have a component called IP_Stack. It exposes a socket interface. Hence, I would like to show a lollipop with <<socket>> stereotype. That's all.

[Jan ´Bary´ Glas]

Is this, what you want?

(Just presentation work-around: write the stereotype in the name field.)

[gweih]

This is exactly what I need. I guess this workaround is what I have to go for.
Thanks a lot!