ArchiMate Language Fundamentals and Core Concepts
The layered core
ArchiMate separates concerns into layers: Business, Application, and Technology, bracketed by Strategy (above) and Physical and Implementation & Migration (below/beside). Each layer has active structure elements (who/what acts), behavior elements (what is done), and passive structure elements (what is acted upon). Learn the recurring triad: business actor/role/collaboration act through business services/processes/functions on business objects; application components expose application services and operate on data objects; nodes and devices host artifacts and system software.
Services, interfaces, and realization
A service is a unit of functionality exposed to its environment. Realization is the workhorse relationship: a process realizes a service, an application component realizes an application service, a node realizes a device. Assignment links active structure to behavior (a role is assigned to a process). Serving links a service to the element that uses it. Access connects behavior to passive structure, qualified by read/write/access.
Specializations that confuse candidates
Business service vs. business function vs. process: functions are internally oriented groupings, services are externally exposed. Business interaction is collective behavior of a collaboration. Application interface is the access point to a service. Meaning and value are motivational, not business objects.
Traps
- Using composition where aggregation is meant (composition = parts die with the whole).
- Forgetting that specialization is allowed between behavior elements, not only structure.
- Treating grouping as a semantic relationship - it is a container, not a dependency.
- Confusing flow (temporal/transfer between behavior) with triggering (causal sequence).
Rule of thumb
Name the layer first, then ask: is the element a who, a doing, or a what? That question resolves most element-classification items before you consider relationships.