ArchiMate is suitable for most of the Enterprise Architecture (EA) related modelling purposes, excluding process modelling and data modelling. Those can be modelled better with BPMN and UML, as they are more specialized in those specific purposes. However, ArchiMate can be utilized for process modelling at high level, specially if there is a need for linking process steps with specific application layer elements such as application services. Here are couple of examples how ArchiMate can be used for process modelling.
Business Process View
This business process view provides a “high-level structure and composition of a business process (or several processes), the services that are offered, the assigned roles of actors, and the information used by the business process” [ArchiMate 2.1 specification]. This process diagram contains “Junction” -elements to model “fork” and “join” in the process flow.
Business Process View With Roles As “Swimlanes” of a Process – A Layered Approach
These examples and many more can be found from here: link.
Customer Journey View
This customer-centric viewpoint is focusing on customer experience. This “service design” related approach is concentrating the “outside-in” development of the service that is to be designed. This highlights the services and products as essential aspects that produce value to customer(s) – and indirectly to the organization itself. A customer journey path can be used to visualization of a customer value stream, which spans over several application services and applications. In addition, this view combines both “outside-in” and “inside-out” approaches into single one overall view.