Application Integrations Modelling With ArchiMate

Several alternative approaches of modeling data switching between applications are shown in the examples (1 to 10) below.

These alternative modelling approaches illustrate the situation as follows:

  • “Application A” owns a “Data Object A-1”, which is requested by “Application B”.
  • Data flows from “Application A” to “Application B”.
  • “Application A” realizes a service “Application Service A-1” that is used by “Application B”. Accordingly, “Application Interface A-1” is the concrete structural implementation of the “Application Service A-1”.
  • Practically, “Application B” requests the “Application A” and gets the “Data Object A-1” as a response – via the “Application Service A-1”, which behavior is exposed with the “Application Interface A-1”.
Application Integration View.


There are plenty of alternative ways to model application integration with ArchiMate, some of which are shown above. In practice, it is necessary to agree which modeling patterns to use in an organization. This is important to keep the overall enterprise modeling repository consistent and coherent. Concerning application integrations modelling, I’d suggest to adapt and utilize approaches 1, 3 and 10 of those illustrated here (above). Those are the most informative and practical approaches (a.k.a “patterns”), as they are relatively simple and intuitively understandable…