A function describes internal behavior performed by an active structure element that is required to produce a set of products, services or results at a Layer. It is performed by a single active structure element.

Processes describe a flow of activities. Functions group activities according to their required skills, knowledge, and resources. A process forms a string of functions.

A function may be triggered by, or trigger, any other behavior element (event, process, function, or interaction).

A function may access passive structure elements at the layer. A function may realize one or more services and may use (internal) services (at multiple layers). Active structure elements at the same layer may be assigned to a function.

The name of a function should preferably be a verb ending with "-ing"; e.g., "claims processing".

Category: Layer and Behaviour aspect

Examples: Financial Handling, Claims Processing, Asset Management, Maintaining Customer Relations, and see the examples at each layer

Typical Relationships:

  • Flow - function, role
  • Triggering - event, function
  • Access - passive structure element
  • Realisation - service
  • Assignment - active structure element

Source: Generalization of Business Function, Application Function and Technology Function as defined in the ArchiMate Framework.


Alongside the breadcrumbs for this item which shows its "ancestry" in concept space, the Child items tab lists its descendants, and the Siblings items tab the concepts that exist under the item's "parent item".