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
This diagram enables more readable layout and economic usage of space: Business Roles that are assigned to certain process steps can be placed on background.
Note! Archi-tool (link) automatically proposes correct relations when using nesting. For example, in the diagram above, Archi suggests all the allowed relations, e.g. assignment when modeler is nesting a Process element into Business Role element. Archi tool guides to model what is allowed according to the ArchiMate specification (relationship table, link). As such, Archi tool encourages to correctness in modelling. As a result of this, analysis against the repository of elements can be done without any discontinuity, without any orphan elements. It is important that the repository is coherent.
These examples and many more can be found from here: link.
Another version of this “swimline” style shown below, which illustrates that also information (Business Objects) can be accessed from process steps.
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 (or productized services) as essential aspects that produce added 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.
The customer journey is divided into three typical phases as follows: 1) Pre-service period, 2) Service period and 3) Post-service period.