70 lines
5.1 KiB
Markdown
70 lines
5.1 KiB
Markdown
---
|
||
title: "ArchiMate"
|
||
chunk: 3/3
|
||
source: "https://en.wikipedia.org/wiki/ArchiMate"
|
||
category: "reference"
|
||
tags: "science, encyclopedia"
|
||
date_saved: "2026-05-05T14:22:21.573663+00:00"
|
||
instance: "kb-cron"
|
||
---
|
||
|
||
Yellow for the business layer
|
||
Blue for the application layer
|
||
Green for the technology layer
|
||
The original ArchiMate description from 2004 used colors differently:
|
||
|
||
Blue for active elements
|
||
Yellow for behavioural elements
|
||
Green for passive elements
|
||
Over the years, ArchiMate has moved from the second style as customary to the first. The older second style can also still be found. E.g. the Mastering ArchiMate book uses a style based on this original pattern.
|
||
|
||
==== Letters ====
|
||
As another way to distinguish to which layer an element belongs, according to the full framework layers, there can also be a capital letter in the left top corner of the element that stands for the specific layer (M for motivation, B for business, etc.)
|
||
|
||
==== Element shape ====
|
||
The shape of elements helps to distinguish aspects. Structural elements have square corners, behavioral elements come with round corners. Diagonal corners indicate a motivational element.
|
||
|
||
== Viewpoints ==
|
||
The latest version of ArchiMate introduces views and viewpoints. They allow stakeholders to define specific conditions like concepts, analysis techniques, models, and visualizations – a viewpoint, from which the model should be perceived.
|
||
A view (or a view model) “is defined as a part of an architecture description that addresses a set of related concerns and is tailored for specific stakeholders”. In return, the stakeholders give their feedback which creates a bi-directional communication.
|
||
Ultimately, this allows the stakeholders/architects to communicate their ideas and concerns easily with others. Also by reducing the “view” by setting the right conditions and intentionally limiting the perspective, it is easier solve specific problems and also, for stakeholders from specific areas it makes the model easier to read.
|
||
|
||
== Benefits and pitfalls of ArchiMate ==
|
||
|
||
=== Benefits ===
|
||
Ensures consistency across all architecture models (business domains)
|
||
Allows the stakeholders to be involved in design, to assess all the requirements and it works well as a communication tool
|
||
Richness of the tool – core framework, motivation extension that enriches the core with reasons why and implementation and migration extension
|
||
It is regularly updated with quite broad base of certified users
|
||
3.0.1 version supports IOT features
|
||
It provides user with viewpoints
|
||
|
||
=== Pitfalls ===
|
||
Some of the concepts are more useful than others, and some of the motivational concepts have been found confusing and/or duplicative, according to finished research. Like other related content frameworks (e.g. the TOGAF content metamodel introduced in TOGAF 9), the framework covers a number of layers including both business and technology. The business layers can be harder to model because the concepts there are perhaps less tangible. However, this difficulty is not restricted just to ArchiMate, but some of the concepts at the business layer are also ill-defined
|
||
|
||
== Exchange file format ==
|
||
A standard model exchange file format has been developed for ArchiMate 2.1 and 3.0 models. This is an XML/XSD based file format, and is intended for exchange rather than a persistent file format.
|
||
|
||
== References ==
|
||
|
||
== Further reading ==
|
||
Marc Lankhorst (ed.) and the ArchiMate team (2004) ArchiMate Language Primer. Enschede: Novay.
|
||
Marc Lankhorst et al. (2005). Enterprise Architecture at Work - Modelling, Communication and Analysis. Berlin: Springer-Verlag.
|
||
Marc Lankhorst and Hans van Drunen (2007). Enterprise Architecture: Development and Modelling – Combining TOGAF and ArchiMate Archived 2014-12-20 at the Wayback Machine
|
||
The Open Group (2009), ArchiMate 1.0 Specification. ISBN 978-90-8753-502-5.
|
||
The Open Group (2009), ArchiMate 1.0 Specification - online.
|
||
Marc Lankhorst et al. (2009). Enterprise Architecture at Work - Modelling, Communication and Analysis 2nd edition. Berlin: Springer-Verlag.
|
||
The Open Group (2012), ArchiMate 2.1 Specification - online.
|
||
Marc Lankhorst et al. (2012). Enterprise Architecture at Work - Modelling, Communication and Analysis 3rd edition. Berlin: Springer-Verlag.
|
||
The Open Group (2019), ArchiMate 3.1 Specification - online.
|
||
Andrew Josey, Marc Lankhorst, Iver Band, Henk Jonkers, and Dick Quartel (2017). An Introduction to the ArchiMate® 3.0.1 Specification, White Paper from The Open Group.
|
||
The Open Group et al. (2016). ArchiMate 3 YouTube Playlist YouTube Playlist by The Open Group
|
||
Marc Lankhorst et al. (2017). Enterprise Architecture at Work - Modelling, Communication and Analysis 4th edition. Hardcover and Kindle. Berlin: Springer-Verlag.
|
||
Wierda, Gerben (2021). Mastering ArchiMate Edition 3.1: A serious introduction to the ArchiMate® enterprise architecture modeling language. Heerlen: R&A. ISBN 978-9083143415. Hardcover and PDF.
|
||
|
||
== External links ==
|
||
Media related to ArchiMate at Wikimedia Commons
|
||
ArchiMate (hosted on 'The Open Group' site)
|
||
Archived ArchiMate homepage.
|
||
Homepage for the ArchiMate Model Exchange File Format
|
||
The Open Group YouTube ArchiMate 3.0 Playlist |