Application Component Sequence Diagram View 2

This version (diagram below) shows how ArchiMate can be used to model the actions that internal elements of Application Components perform. Behavioral processes or functions, as well as structural sub-components, are examples of internal parts. Application Process-, Application Function-, and Application Component-elements are used to model them. These are only provided as alternatives.

EDIT THIS ARCHIMATE DIAGRAM

The actions in this sequence diagram (above) are as follows:

  1. The sub-process “X” of Application Component “A” sends a request message to Application B with the parameter “A.”

  2. The sub-process “B-1” of Application Component “B” gets the incoming request and then (synchronously) calls Application Component C, where Application Function “Y” accepts the request, does certain actions, and returns back.

  3. The other sub-process “B-2” of Application Component “B” sends a message with parameters to Application Component D and receives acknowledgement. Sub-component “D” of Application Component “D” does the processing.

  4. The answer message from Application Component B is received by Application Component “A.”As shown here, we can model quite complex integration cases with combination of these elements (Application Component, Application Process and Application Function and relations (Trigger, Flow). UML sequence diagram has its own specialized purpose in software design, but ArchiMate can be utilized in quite a many modelling purposes – also in application design.

One of the most significant aspects of the enterprise architecture is application integration (EA). That is why it is useful if we can describe how applications switch data and what interaction methods are employed in more detail. Here’s a link to the book “Enterprise Integration Patterns,” which is a fantastic place to start learning about integration patterns.

The same idea of leveraging ArchiMate dynamic relationships Trigger and Flow, which may be used to model both synchronous and asynchronous messaging patterns, is utilized in a sequence with the end-user included (figure below) (request-response and callback, also publish-subscribe etc.).

Last updated