Provided Interface versus Interface?

[swe]

Are Interface and ProvidedInterface different concepts? I noticed that when inserting an embedded element in a port (adding a provided/required interface) I get a selection menu to select an existing interface. However, it seems that I can create another interface with the same name, and there are no conflicts.

Also, when editing the shapes in shape editor, if I change the appearance of the interface (box notation) the provided interface notation does not change. EA Architect treats these two distinctly, can someone clarify?

[Geert Bellekens]

Interface and Provided Interface are indeed treated by EA as separate items.
The "Provided Interface" only indicates that a component exposes a certain interface, without the need to specify that interface itself.

Whereas the interface is the "real" interface.

In a complete model each Provided Interface actually links to a "real" interface, but I can image circumstances where you don't need or want to specify the "real" interface.
In those cases you can get by with creating only a Provided Interface.

Geert

PS. You almost never get conflicts when using the same name for different elements, even when they exist in the same namespace.

[Uwe Krüger]

What exactly does it mean, when you say:

"In a complete model each Provided Interface actually links to a "real" interface, "

is there any actual link? I can select a "real interface" when defining an exposed interfaced, then an interface with the same name is made inside the component. But then how do I get back to the "real interface"? I do not see any link, should I? So its only by name? But that can be changed, especially if I don't see, where the interface is used.

Regards
Uwe

[qwerty]

This is done by drawing a generalization to the real interface. Try Advaced/Parent in the context of a req/prov interface.

q.

[Uwe Krüger]

Thank you very much, this is what I was looking for and couldn't see right in front of my nose!