0735 Solution Ports and Wires¶

Solution components need well-defined interfaces. These may be APIs or other types of request and information exchange mechanisms such as eventing.

SolutionPort entity¶

The interfaces for a solution component are defined using a SolutionPort entity. Each port represents the interface for a particular type of consumer. The port may offer multiple technology mechanisms (APIs, events, ...) to the consumer. However, if these mechanisms are used for different purposes, they are better represented as different ports.

SolutionComponentPort relationship¶

The SolutionComponentPort relationship links a solution component to one of its ports.

SolutionLinkingWire relationship¶

The SolutionLinkingWire is a multi-link relationship that shows the linkage between solution components, optionally via their ports, to other elements in the architecture.

• The iscQualifiedNames attribute allows linkage to the information supply chains that identify critical data flows for the organization.
• The label and description attributes help to explain how/why the lineage flow progresses.
• The oneWay attribute indicates that information flow is in one direction.
• The integrationStyle attribute indicates the type of technology used to implement the linkage.
• The frequency attribute indicates how often the data flows.
• The protocol attribute indicates the type of protocol used to implement the linkage.
• The dataExchanged attribute describes the type of data exchanged.

SolutionPortDelegation relationship¶

Solution components can be decomposed into smaller solution components. The SolutionPortDelegation relationship shows which ports in the parent solution components map to the ports of the solution components it is decomposed into.

Example¶

The diagram below shows a set of linked solution components and their linkage to the assets that implement them.

Raise an issue or comment below