Need help for correct ball and socket representation in component diagram

[Richard Freggi]

Hello I have version 13.10 and I have a question about interface representation in component diagrams.  I think the correct UML 2.5 procedure (for example this works in Eclipse Papyrus UML modeler) is
- Draw component 1 and component 2
- Draw interface 1 and interface 2, right click - use circle notation
- Add <<Realize>> dependency from component 1 to interface 1
- Add <<Use>> dependency from component 2 to interface 2.  Interface 2 should be displayed as a socket (open semicircle), showing it's a required interface
- Add dependency between interface 2 and interface 1.  Done

However, well there is no <<Use>> dependency in the toolbox (you can find it in the dependency properties menu under Stereotypes) and the ball does not turn into a socket when connected via a <<use>> dependency. 

Is Sparx inconsistent with UML standard?  Or am I doing something wrong.

p.s. I know about the Exposed interface - right click and choose provided or required and the assembly connector, but these seem like a bit of a kludge (convenient at times, but still not a UML 2.5 compliant interface).  For example I can add attributes to the Expose interface; I can't differentiate between provided and required interfaces in assembly connector, and other issues.

Couldn't find anything useful in the documentation.  If anyone has ideas please share thanks!

[qwerty]

There are distinct Provided- and Requiredinterface elements (ball/socket) which you have to use.

q.

[RoyC]

Qwerty, I think those are the Provided and Required Interface modes of the Exposed Interface element that Richard appears to have already discarded.

[qwerty]

I was referring to

the ball does not turn into a socket

which does not make sense.

q.

[Richard Freggi]

Hello - quoting myself below: the more immediate question is, does Sparx EA deviate from the UML 2.5 standard for interfaces?  Or did I miss something

Anyone knows?  Simon M?  Thanks!

Hello I have version 13.10 and I have a question about interface representation in component diagrams.  I think the correct UML 2.5 procedure (for example this works in Eclipse Papyrus UML modeler) is
- Draw component 1 and component 2
- Draw interface 1 and interface 2, right click - use circle notation
- Add <<Realize>> dependency from component 1 to interface 1
- Add <<Use>> dependency from component 2 to interface 2.  Interface 2 should be displayed as a socket (open semicircle), showing it's a required interface
- Add dependency between interface 2 and interface 1.  Done

However, well there is no <<Use>> dependency in the toolbox (you can find it in the dependency properties menu under Stereotypes) and the ball does not turn into a socket when connected via a <<use>> dependency. 

Is Sparx inconsistent with UML standard?  Or am I doing something wrong.

p.s. I know about the Exposed interface - right click and choose provided or required and the assembly connector, but these seem like a bit of a kludge (convenient at times, but still not a UML 2.5 compliant interface).  For example I can add attributes to the Expose interface; I can't differentiate between provided and required interfaces in assembly connector, and other issues.

Couldn't find anything useful in the documentation.  If anyone has ideas please share thanks!