Information exchange with external organizations

Uit Via Nova Architectura Wiki
Ga naar: navigatie, zoeken
Figure 2 02 Most Important relationships between concepts.png ArchiMate Made Practical

Zie ook: ArchiMate in de praktijk

Question

How you model data exchange with external organizations on the application layer? At the application level, there is indeed application functionality that realizes these information exchanges. But should you also include the external application in the application landscape?

Solution

A first alternative is to model a flow relation directly from the native application to the external organization. Here the external application is not included.

Figure 5 25 Flowrelation between an application and external organisations.png

Figure 5 44: Flow relation between internal application and external organization

This prevents us from including external applications in the application landscape. For data exchanges with various external organizations it would increase the number of external applications in the application landscape, which could become cluttered as a result. See the example below:

Figure 5 26 Flowrelation between an application and external organisations using applications.png

Figure 5 45: Flow relation between its own application and the external organization application

A second alternative is to model an external application service. Then the data exchange between application services is modeled.

Figure 5 27 Flowrelation between an application and external organisations using services.png

Figure 5 46: : Flow relation between the application services of its own application and the external organization

If desired the flow relations between the application services can be replaced by a data-object; written by one application service, read by the other application service

Consequences

Not applicable.

Alternatives

Not applicable.

Relationships with other good practices

Here is a relationship with the good practice 'Interfaces between applications'