Components exposing (provided/required) interfaces

[Rob7795]

I'm having trouble working out the best way to model an existing system with components that expose interfaces, either provided or required. This issue is the traceability back to the original interface element....

I have an interface interface1, and 2 components component1 and component2.

I have created an exposed interface on component1: when prompted, I select interface1 from the list - the provided (lollipop) is annotated with "interface1". I do the same (but opposite) for the required (socket) interface on component2.

Then, I create a dependency from the required interface to the provided interface:



My problem is that if I then open up the properties of the interface1 (as the original element specification, not the provided/required interface) I get no references to either of the components in the "links" tab. If I change the name of the original interface in the project explorer, the annotations on the diagram change along with it - so there must be a relationship there somewhere.  In the end, it means the relationship matrix doesn't show the associations that I'd expect.

Can anyone shed some light on what I'm doing wrong?

Cheers, Rob.

[Paolo F Cantoni]

"Links tab" refers to arcs that specifically connect vertexes (sorry for using those terms but if I don't any other term can get confused with what's going on within EA).

Anyway,  The relationship between the interface and the components - although it exists and is tracked within EA - is not rendered as an arc.  It's typically represented by an internal pointer in the origin item.  The relationship between an instance and it's classifier is the same, as is the nesting within the browser.

I've recently posted elsewhere on the need to have these relationships (at least rendered) as arcs - so that they might appear in such places.

HTH,
Paolo