socket line notation

[PeterM]

O n Page 263 of applying UML and Patterns  by Larman he describes a new interface realization called socket line nottion.

In class relationships (Toolbox) there is a relationship that looks exactly like this notation (tooltip = Assembly) but when I try and use it to connect two classes or a class and interface the resulting association is nothing like what the toolbox icon looks like.

How can one get this apear to as per the book?  :-/

[Geert Bellekens]

I'm guessing the socket line notation is the other side of the lollipop.
In that case you can use the "exposed interface" tool on the composite or component toolbox. Drop that on a class, select "required" and the approriate interface.

But... the required interface is actually nothing more then another way to show a dependency to an interface. This is in no way a realization. If you wish to show a realization then you could use the "provided interface" (small lollipop) or a regular realization of an interface, and then change the appearance of the interface into "lollipop" (right click, Advanced/Use Circle Notation)
The difference between the provided interface and the realization is that with a provided interface you do not specify exaclty who or what is realizing the interface. It could be that only a part of the element is realizing the interface. It merely states that the interface is available from this element.
 The realization on the other hand clearly states which element is realizing the interface.

Geert

[PeterM]

Using the exposed interface on a class and then making it provided I get tyhe lollipop notation. If I use another on related class and make it required I get the socket nottion. I get something similar to what Craig Larsman has on Page 263 of his book. It is not the same however as I cannot connect the two.

To quote him

Lollipop notation indicates that Clock3 implements  and provides the Timer interface to clients.
Socket line notation. Window3 has a dependancy on the Timer interface when it collbaorates  with a clock3 object.

I could e-mail someone a copy of the image I scanned in which would make it clearer.

[Geert Bellekens]

You are on the right track. The only thing missing is a visual link between the socket and the lollipop.
Now this is something that is not supported very well by EA.
If you really which to show the connection between the required and proviced interface I would use a regular dependence between the required and the proviced interface. It may not look as nice as the assembly connector, but at least I have a hard reference to the interface used by both parts.

Geert

[PeterM]

Maybe in the next version they will address this as it is part of the UML 2.0 standard.

In the mean time I can live with it.