Integration viewpoint

Goal : Providing insight into links between the application and the patterns used from the reference architecture. System integration. Obliged : Only in the case that a link between applications must be established and this does not fit in the previously mentioned application view. An integration view can be realized by copying the chosen integration pattern from the reference architecture and then providing the implementation in application components, interfaces, etc.

Diagram in standard mode

Integration Customer Interface (Application Interface)

Naming: {name of service} Customer For example: Relationship_SRV Customer


Details van Integration Customer Interface (Application Interface)

Integration Component (Application Component)

Component assigned to the integration function as middleware functionality.


Details van Integration Component (Application Component)

Integration Interface Source (Application Interface)

Refers to the interface within the integration layer that provides access to the source. This can be an IMH or ORCH. Naming: {name of the service} Source For example: Relationship_SRV Source


Details van Integration Interface Source (Application Interface)

ApplicationInterface

Naming Conventions Usage: Noun. For example: GUI, REST API, Web Service.


Details van ApplicationInterface

Integration Service (Application Service)

Integration Operation (Application Function)

DataObject

Naming Conventions Usage: Singular noun. For example: Search query, Search result Logical name. Avoid technical names such as file, database.


Details van DataObject

Application Component

Naming Conventions Usage: Noun (name of the package). For example: MsWord, Autonomy Federator


Details van Application Component

Technology Service

Naming Conventions Usage: Noun in the ing form. For example: Messaging, Broadcasting.


Details van Technology Service