ArchiMate Modeling and Views
From model to view
A view is a selection of a model presented for a stakeholder's concern. ArchiMate does not prescribe a fixed view catalogue, but the exam expects you to know common viewpoints and what they show. The Basic Viewpoint shows a single-layer, single-aspect slice. Layered viewpoints (e.g., Application Usage) show cross-layer Serving relationships. Motivation viewpoints show goals and requirements.
Notation literacy
You should be able to read the standard shapes: rectangles for structure and behaviour, rounded shapes for services, and the relationship line styles (solid for structural, dashed for dependency/serving). Composition uses a filled diamond at the whole end; Aggregation an open diamond. Realization uses a dashed line with a hollow triangle. Serving uses a dashed line with an open arrowhead.
Common modelling traps
- Mixing abstraction levels in one view - a view should serve one concern.
- Using a Business Actor where a Business Role belongs - actors are concrete; roles are the responsibilities they take on.
- Modelling a data flow as a control flow - ArchiMate uses Triggering and Flow relationships; know which is which.
Worked example
To show how a customer order is handled end to end, build an Application Usage viewpoint: Business Process → (Serving) → Application Service → (Realization) → Application Component → (Assignment) → Node. Each arrow is a distinct relationship type; getting the arrow types right is what earns marks.
Rule of thumb
Choose the viewpoint by asking who is the audience and what is their concern? Then include only elements that answer that concern.