> [!tldr] Comparing various opinions on the most useful "subset" of Archimate
Since the point of [[Archimate]] is **communication**, it seems appropriate to recognize the more esoteric concepts. You would be pretty okay for most audiences sticking with the "main" elements of ArchiMate. Depending on your sources, you get a slightly different take on what those are.
> [!tip] The real tip is:
All ArchiMate Concepts can be useful. All can be confusing.
What what's best but make sure it's understood by the audience.
# Full ArchiMate
This is the palette from [[Archi]]:
![[Screenshot 2026-03-23 at 1.49.54 PM.png]]
| **Layer** | **Number of Constructs** |
| -------------- | :----------------------: |
| Relationships | 11 |
| Strategy | 4 |
| Business | 13 |
| Application | 9 |
| Technology | 13 |
| Physical | 4 |
| Motivation | 10 |
| Implementaiton | 5 |
| **Total** | **69** |
> [!warning] That's a lot.
> So there's roughly ~70 constructs you can use in various ways to say different things.
So let's do a cross section of people's opinion of
# Reduced Summary Table
The sources agree[^1] on:
- Role
- Process
- Function
- Service
- Business Actor
- Business Object
- Application Component
- Data Object
- Technology Node
The point of this note was to make this table.
| Domain | Concept | Inclusion List |
| -------------- | --------------------- | --------------------- |
| Strategy | Resource | 🧑🍳 |
| Strategy | Capability | 🧑🍳2️⃣ |
| Strategy | Value Stream | |
| Strategy | Course of Action | 🧑🍳 |
| Business | Actor | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Business | Role | 👍🧑🍳1️⃣2️⃣3️⃣ |
| Business | Collaboration | |
| Business | Interface | 🧑🍳 |
| Business | Process | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Business | Function | 👍🧑🍳🧑🏫2️⃣3️⃣ |
| Business | Interaction | 👍 |
| Business | Event | 👍🧑🍳2️⃣ |
| Business | Service | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Business | Object | 👍🧑🍳🧑🏫1️⃣2️⃣ |
| Business | Contract | |
| Business | Representation | 🧑🍳 |
| Business | Product | 🧑🍳 |
| Application | Component | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Application | Collaboration | |
| Application | Interface | 🧑🍳2️⃣ |
| Application | Function | 👍🧑🍳🧑🏫 |
| Application | Interaction | 👍 |
| Application | Process | 👍🧑🍳🧑🏫 |
| Application | Event | 👍🧑🍳 |
| Application | Service | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Application | Data Object | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Technology | Node | 👍🧑🍳1️⃣2️⃣3️⃣ |
| Technology | Device | 🧑🍳🧑🏫2️⃣ |
| Technology | System Software | 🧑🍳🧑🏫1️⃣2️⃣ |
| Technology | Collaboration | |
| Technology | Interface | 🧑🍳 |
| Technology | Path | |
| Technology | Communication Network | 🧑🍳 |
| Technology | Function | 👍🧑🏫 |
| Technology | Process | 👍🧑🏫 |
| Technology | Interaction | 👍 |
| Technology | Event | 👍🧑🍳 |
| Technology | Service | 👍🧑🍳🧑🏫1️⃣2️⃣3️⃣ |
| Technology | Artifact | 👍🧑🍳🧑🏫3️⃣ |
| Physical | Equipment | |
| Physical | Facility | |
| Physical | Distribution Network | |
| Physical | Material | |
| Motivation | Stakeholder | 👍🧑🍳2️⃣ |
| Motivation | Driver | 👍🧑🍳2️⃣ |
| Motivation | Assessment | 🧑🍳 |
| Motivation | Goal | 👍🧑🍳2️⃣ |
| Motivation | Outcome | 🧑🍳2️⃣ |
| Motivation | Principle | 🧑🍳 |
| Motivation | Requirement | 👍🧑🍳2️⃣ |
| Motivation | Constraint | 🧑🍳 |
| Motivation | Meaning | |
| Motivation | Value | 🧑🍳 |
| Implementation | Work Package | 👍2️⃣ |
| Implementation | Deliverable | 👍2️⃣ |
| Implementation | Implementation Event | |
| Implementation | Plateau | 👍 |
| Implementation | Gap | |
Inclusion list legend:
👍 = [[#My Take]]
🧑🍳 = [[#ArchiMate Cookbook]]
🧑🏫 = [[#ArchiMate 101]]
1️⃣ = [[#Gemini]]
2️⃣ = [[#ChatGPT]]
3️⃣ = [[#Claude]]
## My Take
Behavior - keep all
Business - actor & role & object
App - component & object
Technology - node & artifact
Physical - probably just drop
Implementation - work package, deliverable, plateau?
Motivation - stakeholder, driver, goal, requirement
Strategy - ... probably just drop & use prose to describe stuff... or keep all of it.
## ArchiMate Cookbook
The [[Archimate Cookbook]] suggests a limited set:
![[Screenshot 2026-03-23 at 1.59.11 PM.png]]
| **Layer** | **Number of Constructs** | Removed |
| -------------- | :----------------------: | ---------------------------------------------------- |
| Relationships | 9 | (not sure actually) |
| Strategy | 3 | Value Stream |
| Business | 10 | Collaboration, interaction, contract |
| Application | 7 | Collaboration, interaction |
| Technology | 8 | Collaboration, interaction, path, function, process, |
| Physical | 0 | All physical elements |
| Motivation | 9 | Meaning |
| Implementaiton | 0 | All implementation elements |
| **Total** | **46** | |
Fewer, but still a lot.
## ArchiMate 101
ArchiMate 101 (from [[#Source]]) is similar-ish to the ArchiMate Cookbook in terms of its purpose. It doesn't outright say "this is the most useful subset" - but it does limits introductions to:
- Services, Functions, and Processes
| Layer | Active Structure | Passive Structure |
| ----------- | ----------------------- | ----------------- |
| Business | Actor | Object |
| Application | Component | Object |
| Technology | Device, System Software | Artifact |
## Gemini
- [ ] Clean up
- **Business Process:** Represents the core behavioral steps and workflows that deliver specific business outcomes.
- **Business Actor / Business Role:** Denotes the organizational entities, departments, or named responsibilities that execute processes.
- **Business Service:** Defines the outward-facing value or capability exposed by business behavior to internal or external users.
- **Business Object:** Captures the key conceptual information or artifacts manipulated during a process (e.g., _Invoice_, _Customer Profile_). [[1](https://architectureinmotion.com.au/archimate-elements/), [2](https://www.youtube.com/watch?v=Ga8G3k3Q1N4&t=473)]
Core Application Layer Concepts
- **Application Component:** Represents software modules, packaged systems, or microservices that automate business functionality.
- **Application Service:** Exposes automated behavior and capabilities provided by an application component.
- **Data Object:** Models structured electronic data entities corresponding to application data and databases. [[1](https://www.leanix.net/en/wiki/ea/what-is-archimate), [2](https://www.youtube.com/watch?v=b49nj0AV5xU&t=554), [3](https://www.researchgate.net/figure/Automatic-weights-to-ArchiMate-elements_tbl1_300207754), [4](https://www.youtube.com/watch?v=Ga8G3k3Q1N4&t=473)]
Core Technology Layer Concepts
- **Node:** Represents physical or virtual computational hardware and execution environments.
- **System Software / Technology Service:** Captures infrastructure software (like operating systems or databases) and underlying hosting services. [[1](https://blog.visual-paradigm.com/comprehensive-guide-to-archimate-diagrams/)]
Most Used Relationships
- **Serving (Dependency):** Links services or components to the behaviors/processes they support (e.g., an Application Service _serves_ a Business Process).
- **Realization:** Connects a concrete component or service to the abstract definition it fulfills.
- **Triggering / Flow:** Establishes temporal sequencing between business processes or data movement between elements. [[1](https://www.leanix.net/en/wiki/ea/what-is-archimate)]
## ChatGPT
| | | |
|---|---|---|
|Tier|ArchiMate concept|What people actually use it for|
|Very high|Application Component|Systems/applications: Salesforce, SAP, Billing System|
|Business Process|End-to-end business behavior: Hire Employee, Fulfill Order| |
|Business Actor|Organizations, departments, external parties| |
|Business Role|Who is responsible for what| |
|Capability|What the enterprise must be able to do| |
|Business Service|Business-facing outcomes/services| |
|High|Application Service|What an application provides to other things|
|Business Function|Stable functional grouping of behavior| |
|Data Object|Application-level data| |
|Business Object|Conceptual/business information| |
|Goal|Desired outcome| |
|Stakeholder|Who cares about the architecture| |
|Driver|Why change is happening| |
|Work Package|Project/initiative/change effort| |
|Medium|Node|Hosting/runtime environment|
|Technology Service|Infrastructure/platform service| |
|System Software|DBMS, OS, runtime, middleware| |
|Device|Actual hardware| |
|Application Interface|API/interface when the interface itself matters| |
|Business Event|Important triggering occurrence| |
|Outcome|Result produced by a change or capability| |
|Requirement|Architecture requirement| |
|Deliverable|Output of a project/work package| |
It went on to say:
Structure
- Person / Actor
- Organization
- Role
- Application
- Technology
- Data / Information Object
Behavior
- Capability
- Process
- Service
Intent
- Stakeholder
- Driver
- Goal
- Requirement
Change
- Initiative / Work Package
- Outcome
## Claude
Business Layer
• Business Services — by far the most commonly used concept; these bridge business and IT and make the value exchange explicit
• Business Functions — used for capability modeling and decomposition
• Business Processes — essential for understanding workflow and orchestration
• Business Roles/Actors — necessary for ownership and accountability but often underutilized
Application Layer
• Application Components — fundamental building block; most rationalization work revolves around these
• Application Services — the realized business services; critical for understanding application-to-business mapping
• Data Objects — often the real constraint when decomposing applications
Technology Layer
• Nodes (servers, infrastructure) — practical necessity for capacity and deployment planning
• Artifacts (binaries, databases) — underused but valuable for tracking what actually runs where
• Technology Services — bridge the platform to application layer
Most Critical Relationships
• Realization (application → business) — the core mapping for showing delivery
• Aggregation/Composition — for hierarchy and decomposition
• Flow — for process and data movement
• Association — unfortunately overused as a catch-all
****
# More
## Source
- self
- https://archimate-community.pages.opengroup.org/workgroups/archimate-101/
- [[Archimate Cookbook]]
[^1]: at least 5 of the 6