Viewpoints for process modeling

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


How do you model a process in ArchiMate? The ArchiMate book shows a number of viewpoints but which combination of viewpoints is required to model a process containing sequential steps?


The ArchiMate book shows two viewpoints for process modeling: the Business process collaboration viewpoint and the Business process viewpoint. The difference between these viewpoints is that in the Business collaboration viewpoint the relation between processes and the relation with the environment is visualized, while in the Business process viewpoint one business process is expressed. We concentrate here on the Business process viewpoint; the Business process collaboration viewpoint is analogous. When modeling a process in ArchiMate, the following aspects can be visualized: the parts of the process, their cohesion, the assignment of process parts to roles, actors of business parts and the support by applications. This can be realized in the following sequence:

  • Model the business process at a high level: Decompose the business process and make relationships by introducing business events and triggering relationships. One can add to that the way in which the process delivers business services to its environment.
  • Information-exchange: Model the information-exchange between processes by adding flow relationships between processes, or reading and writing of business objects.
  • Assignment to organization: Model the organizational part that executes the business process. This can be visualized by assignment relationships or by using swim lanes.
  • Support by applications: Model how applications support business processes. The application viewpoint can be used for this.

If required, a more generic distinction can be made between a ‘logical’ and ‘concrete’ or physical level of modeling. A logical model expresses the functional structure and logical cohesion of business processes. No detail about time, place, people or machines is given. An implementation model will closely resemble what you can see or want to realize in reality. It describes physical aspects like humans and machines, with concrete details assigned to tasks. If an organization wants to distinguish between different types of processes (like logical and physical) in ArchiMate, such distinction should be defined before starting modeling. The ArchiMate relationship used between ‘logical process’ and ‘physical process’ is composition.

A process can be specialized into process types. For example, the process ‘Request insurance’ can be specialized into the sub processes ‘Request travel insurance’ and ‘Request damage insurance’.


Not applicable.


Not applicable.

Relationships with other good practices

Refer to the good practices ‘Business service, business function and business process’ and ‘Constraining business process’.