Reply To: Why Aren't Interfaces Tied To Components?

homepage Forums BridgePoint/xtUML Usage and Training Why Aren't Interfaces Tied To Components? Reply To: Why Aren't Interfaces Tied To Components?

Lee Riemenschneider

I don’t understand why a port interface on a component can’t be formalized to an interface defined within the component. Domain functions should be tightly coupled to the domain.

If the same component port interface was reused as a EE, like the Time EE, then you’d want to be able to formalize the port to some test interface (which could also be managed with the component). This is where I see the linkage between these concepts.

From the analyst perspective, reusing an interface might introduce domain pollution, as you are addressing the services from the other domain’s perspective rather than your own domain’s perspective.

In the system build case, the bridge calls and the domain function might not align, and you’d need an interface with external functionality to map between the two component ports. I haven’t looked at this case too closely from the new component view. I guess I need to run through some more use cases.