This post is a basic aide-memoire for me to remember the characteristics of the Archimate Application Layer model elements. For a detailed description refer to the main Archimate 3.0 documentation.
The model elements are divided into 3 categories:
- Active Structure
- Passive Structure
- Behaviour
Active Structure
Element | Description | Notes | Notation |
Component | Encapsulation of application functionality aligned to implementation structure Modular and replaceable Encapsulates behaviour and data Exposes services and makes them available through interfaces | A self-contained unit Independently deployable, re-usable, and replaceable Performs one or more application functions Functionality is only accessible through application interfaces |  |
Collaboration | An aggregate of two or more application components that work together to perform collective application behaviour | Specifies which components cooperate to perform some task A logical or temporary collaboration of application components Does not exist as a separate entity |  |
Interface | A point of access where application services are made available | How the functionality of a component can be accessed Exposes application services The same interface may expose multiple services |  |
Behaviour
Element | Description | Notes | Notation |
Function | Automated behaviour performed by a component | Describes internal behaviour of a component Functions are exposed externally through one or more services May access data objects |  |
Interaction | A unit of collective application behaviour performed by two or more application components | Collective behaviour performed by components that participate in a collaboration |  |
Process | A sequence of application behaviours that achieves a specific outcome | The internal behaviour performed by a component to realize a set of services May realize application services May access data objects A component may perform the process |  |
Event | Denotes a state change | Does not have a duration May be internal or external May have a time attribute |  |
Service | An explicitly defined exposed application behaviour | Functionality is exposed through interfaces Realised by one or more functions Provides a useful unit of behaviour |  |
Passive Structure
Element | Description | Notes | Notation |
Data | Data structured for automated processing | A self-contained piece of information Clear business meaning |  |