From HandWiki
Short description: Enterprise architecture modeling language
Insurance claim process depicted in ArchiMate. Archimate enables modelling in different layers.

ArchiMate (/ˈɑːrkɪmt/ AR-ki-mayt) is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains[1] in an unambiguous way.

ArchiMate is a technical standard from The Open Group and is based on concepts from the now superseded IEEE 1471 standard. It is supported by various tool vendors and consulting firms. ArchiMate is also a registered trademark of The Open Group. The Open Group has a certification program for ArchiMate users, software tools and courses.[2]

ArchiMate distinguishes itself from other languages such as Unified Modeling Language (UML) and Business Process Modeling and Notation (BPMN) by its enterprise modelling scope.[3]

Also, UML and BPMN are meant for a specific use and they are quite heavy – containing about 150 (UML) and 250 (BPMN) modeling concepts whereas ArchiMate works with just about 50 (in version 2.0). The goal of ArchiMate is to be ”as small as possible”, not to cover every edge scenario imaginable. To be easy to learn and apply, ArchiMate was intentionally restricted “to the concepts that suffice for modeling the proverbial 80% of practical cases".[4]


ArchiMate offers a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems, and technical infrastructure. This insight helps the different stakeholders to design, assess, and communicate the consequences of decisions and changes within and between these business domains.

The main concepts and relationships of the ArchiMate language can be seen as a framework, the so-called Archimate Framework:[5] It divides the enterprise architecture into a business, application and technology layer. In each layer, three aspects are considered: active elements, an internal structure and elements that define use or communicate information.

One of the objectives of the ArchiMate language is to define the relationships between concepts in different architecture domains. The concepts of this language therefore hold the middle between the detailed concepts, which are used for modeling individual domains (for example, the Unified Modeling Language (UML) for modeling software products),[6] and Business Process Model and Notation (BPMN), which is used for business process modeling.


ArchiMate is partly based on the now superseded IEEE 1471 standard. It was developed in the Netherlands by a project team from the Telematica Instituut in cooperation with several Dutch partners from government, industry and academia. Among the partners were Ordina (nl), Radboud Universiteit Nijmegen, the Leiden Institute for Advanced Computer Science (LIACS) and the Centrum Wiskunde & Informatica (CWI). Later, tests were performed in organizations such as ABN AMRO, the Dutch Tax and Customs Administration and the ABP.[7]

The development process lasted from July 2002 to December 2004, and took about 35 person years and approximately 4 million euros. The development was funded by the Dutch government (Dutch Tax and Customs Administration), and business partners, including ABN AMRO and the ABP Pension Fund.[8]

In 2008 the ownership and stewardship of ArchiMate was transferred to The Open Group. It is now managed by the ArchiMate Forum[9] within The Open Group. In February 2009 The Open Group published the ArchiMate 1.0 standard[10] as a formal technical standard. In January 2012 the ArchiMate 2.0 standard, and in 2013 the ArchiMate 2.1 standard[11] was released.

In June 2016, the Open Group released[12] version 3.0 of the ArchiMate Specification.[13] An update to Archimate 3.0.1 came out in August 2017.[14] Archimate 3.1 was published 5 November 2019.[15] The latest version of the ArchiMate Specification is version 3.2 released October 2022.[16]

Version 3.0 adds[17] enhanced support for capability-oriented strategic modelling, new entities representing physical resources (for modelling the ingredients, equipment and transport resources used in the physical world) and a generic metamodel showing the entity types and the relationships between them.

ArchiMate Framework

Core Framework

ArchiMate Core Framework.

The main concepts and elements of the ArchiMate language are being presented as ArchiMate Core Framework.[18] It consists of three layers and three aspects. This creates a matrix of combinations. Every layer has its Passive structure, Behavior and Active structure aspects.


ArchiMate has a layered and service-oriented look on architectural models. The higher layers make use of services that are provided by the lower layers. Although, at an abstract level, the concepts that are used within each layer are similar, we define more concrete concepts that are specific for a certain layer. In this context, we distinguish three main layers:[1][8][19]

  • The Business layer is about business processes, services, functions and events of business units. This layer "offers products and services to external customers, which are realized in the organization by business processes performed by business actors and roles".
  • The Application layer is about software applications that "support the components in the business with application services".
  • The Technology layer deals "with the hardware and communication infrastructure to support the Application Layer. This layer offers infrastructural services needed to run applications, realized by computer and communication hardware and system software".[4]

Each of these main layers can be further divided in sub-layers. For example, in the Business layer, the primary business processes realising the products of a company may make use of a layer of secondary (supporting) business processes; in the Application layer, the end-user applications may make use of generic services offered by supporting applications. On top of the Business layer, a separate Environment layer may be added, modelling the external customers that make use of the services of the organisation (although these may also be considered part of the Business layer).

In line with service orientation, the most important relation between layers is formed by use relations, which show how the higher layers make use of the services of lower layers. However, a second type of link is formed by realisation relations: elements in lower layers may realise comparable elements in higher layers; e.g., a ‘data object’ (Application layer) may realise a ‘business object’ (Business layer); or an ‘artifact’ (Technology layer) may realise either a ‘data object’ or an ‘application component’ (Application layer).


  • Passive structure is the set of entities on which actions are conducted. In the Business Layer the example would be information objects, in the Application Layer data objects and in the Technology Layer, they could include physical objects.
  • Behavior refers to the processes and functions performed by the actors. "Structural elements are assigned to behavioral elements, to show who or what displays the behavior".[19]
  • Active Structure is the set of entities that display some behavior, e.g. business actors, devices, or application components.

Full Framework

ArchiMate Full Framework

The Full ArchiMate framework is enriched by the Physical Layer, which was added to allow modeling of “physical equipment, materials, and distribution networks”[19] and was not present in the previous version.

The Implementation and Migration Layer adds elements that allow architects to model a state of transition, to mark parts of the architecture that are temporary for the purpose, as the name says, of implementation and migration.

Strategy Layer adds three elements: Resource, Capability and Course of Action. These elements help to incorporate strategic dimension to the ArchiMate language by allowing it to depict the usage of resources and capabilities in order to achieve some strategic goals.

Finally, there is a Motivation Aspect that allows different stakeholders to describe the motivation of specific actors or domains, which can be quite important when looking at one thing from several different angles. It adds several elements like stakeholder, value, driver, goal, meaning etc.

ArchiMate Language

The ArchiMate language is formed as a top-level and is hierarchical. On the top, there is a model. A model is a collection of concepts. A concept can be either an element or a relationship. An element can be either of behavior type, structure, motivation or a so-called Composite Element (which means that it does not fit just one aspect of the framework, but two or more).

The functionality of all concepts without a dependency on a specific layer is described by the Generic Metamodel. This layer-independent description of concepts is useful when trying to understand the mechanics of the Archimate language.



The generic elements are distributed into the same categories as the layers:[20]

  • Active structure elements
  • Behavior elements
  • Passive structure elements
  • Motivation elements

Active structure elements represent entities that are capable of performing behavior. Based on two levels of abstraction[19] that ArchiMate provides, it is possible to distinguish between internal active structure elements, which stand for active elements within the system - e. g., business actors - and external active structure elements which stand for elements that carry out the behavior outside the system - e. g., interfaces.

Behavior elements can be internal or external as well. An internal behavior element is one that stands for an activity carried out by an active structure element within the system. Archimate defines for instance Process and Function elements. External behavior is a service that the whole system provides to the environment.

Passive structure elements are objects that can be used by behavior elements (and thus active structure elements can perform behavior on them). They usually stand for information objects in the business layer and data objects in the application layer, but they may also be used to represent physical objects.

As described in the previous chapter, motivation elements are answering the question Why?, they are trying to give a context and explain the motives behind the architecture. They can be of an active structure, as a stakeholder and also of a passive structure - value, meaning, driver, etc.


ArchiMate sets several types of relationships that can connect different sets of source and target concepts. The classification of relationships[21] is following:

  • Structural relationships – create a static construction of concepts of the same or different types
  • Dependency relationships – define how elements can support other elements
  • Dynamic relationships – model behavioral dependencies
  • Other relationships

General structure of models within the different layers

Core concepts of the ArchiMate language (Lankhorst, 2013).

The general structure of models within the different layers is similar. The same types of concepts and relations are used, although their exact nature and granularity differ.

First, it is necessary to distinguish the structural or static aspect and the behavioural or dynamic aspect. Behavioural concepts are assigned to structural concepts, to show who or what displays the behaviour. For example, role, interface and collaboration are assigned to business process, organisational service and business interaction, respectively.

Second, there must be a distinction between an external view and an internal view on systems. When looking at the behavioral aspect, these views reflect the principles of service orientation. The service concept represents a unit of essential functionality that a system exposes to its environment. For the external users, only this external functionality, together with non-functional aspects such as the quality of service, costs etc., are relevant. Services are accessible through interfaces, which constitute the external view on the structural aspect.

Although for the external users only the external view is relevant, the design of organisations or systems and their internal operations and management also requires knowledge about the internal realisation of the services and interfaces. For this realisation, it is necessary to make a distinction between behavior that is performed by an individual structural element (e.g., actor, role component, etc.), or collective behavior (interaction) that is performed by a collaboration of multiple structural elements.


The ArchiMate language separates the concepts from their notation (contrary to the UML or BPMN). As there are different groups of stakeholders, they may need different notations. This might be confusing, but it is solved by the viewpoint mechanism.

Although ArchiMate doesn't stress the only one notation, it comes with one and it aims to those "used to existing technical modeling techniques such as ERD, UML, or BPMN, and therefore resembles them".[19]

Use of colors

Formally, color has no meaning in ArchiMate,[19] but many modelers use colors to distinguish between the different layers:

  • Yellow for the Business Layer
  • Blue for the Application Layer
  • Green for the Technology Layer

The original ArchiMate description from 2004[22] 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.[23] The older second style can also still be found. E.g. the book Mastering ArchiMate[24] uses a style based on this original pattern.


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.)[19]

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.[19]


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”.[25] 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



  • 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



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.[28][29][30][31] 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,[32] but some of the concepts at the business layer are also ill-defined [33]

Exchange file format

A standard model exchange file format has been developed for ArchiMate 2.1 and 3.0 models.[34] This is an XML/XSD based file format, and is intended for exchange rather than a persistent file format.


  1. 1.0 1.1 What is ArchiMate? at from Accessed April 19, 2014
  2. ArchiMate Certification at Accessed January 11, 2014.
  3. Pallab Saha (2008) Advances in Government Enterprise Architecture. p.39.
  4. 4.0 4.1 "ArchiMate 3.1 Specification". 
  5. The ArchiMate Framework, in: ArchiMate® 2.1. Accessed 06.2015.
  6. Zoran Stojanović et al. (2007). Service-oriented Software System Engineering. p.145-146.
  7. Telematica Instituut (2006) Annual Report 2005. p.7. Accessed 18 jan 2009.
  8. 8.0 8.1 ArchiMate : Its Time Has Come? Enterprise Architecture Demystified. Posted by snair007 on August 3, 2008
  9. "The Open Group ArchiMate Forum Landing Page - The Open Group". 25 October 2019. 
  10. "ArchiMate 1.0 Specification". 
  11. The Open Group (2012), ArchiMate 2.1 Specification
  12. "The ArchiMate® Enterprise Architecture Modeling Language - The Open Group". 
  13. ArchiMate v3.0 Specification Accessed 27 June 2016.
  14. "Archimate Overview". 12 October 2018. 
  15. "ArchiMate 3.1 Specification". 5 November 2019. 
  16. "ArchiMate 3.2 Specification". 19 October 2022. 
  17. "What is New in ArchiMate® 3.0.1? - The Open Group". 
  18. "ArchiMate 3.1 Specification Chapter 2". 
  19. 19.0 19.1 19.2 19.3 19.4 19.5 19.6 19.7 "ArchiMate 3.1 Specification Chapter 3". 
  20. "ArchiMate 3.1 Specification Chapter 4". 
  21. "ArchiMate 3.1 Specification Chapter 5". 
  22. Concepts for Architectural Description, ArchiMate Deliverable 2.2.1 v4.1 (Telematica Instituut, 2004, no longer available on the web)
  23. See for instance both schemes used in TOG's ArchiMate 2.1 description:
  24. Wierda, Gerben (2021). Mastering ArchiMate Edition 3.1: A serious introduction to the ArchiMate® enterprise architecture modeling language. R&A. ISBN 978-9083143415. 
  25. "ArchiMate 3.1 Specification Chapter 14". 
  26. Oord, Erwin (20 May 2014). "Three common limitations of ArchiMate and how to deal with them". 
  27. "Understanding the benefits of Archimate". 
  28. Azevedo, Carlos L.B.; Almeida, Joao Paulo A.; van Sinderen, Marten; Quartel, Dick; Guizzardi, Giancarlo (August 2011). "An Ontology-Based Semantics for the Motivation Extension to ArchiMate". 2011 IEEE 15th International Enterprise Distributed Object Computing Conference. IEEE. pp. 25–34. doi:10.1109/edoc.2011.29. ISBN 978-1-4577-0362-1. 
  29. Engelsman, Wilco; Wieringa, Roel (2014), Understandability of Goal Concepts by Requirements Engineering Experts, Lecture Notes in Computer Science, 8823, Springer International Publishing, pp. 97–106, doi:10.1007/978-3-319-12256-4_10, ISBN 9783319122557, 
  30. Engelsman, Wilco; Wieringa, Roel (2012), "Goal-Oriented Requirements Engineering and Enterprise Architecture: Two Case Studies and Some Lessons Learned", Requirements Engineering: Foundation for Software Quality, Lecture Notes in Computer Science (Springer Berlin Heidelberg) 7195: pp. 306–320, doi:10.1007/978-3-642-28714-5_27, ISBN 9783642287138, 
  31. Engelsman, Wilco; Wieringa, Roel (2014), "Understandability of Goal-Oriented Requirements Engineering Concepts for Enterprise Architects", Advanced Information Systems Engineering, Lecture Notes in Computer Science (Springer International Publishing) 8484: pp. 105–119, doi:10.1007/978-3-319-07881-6_8, ISBN 9783319078809, 
  32. "On Archimate 3.0". 
  33. Nardi, Julio Cesar; de Almeida Falbo, Ricardo; Almeida, Joao Paulo A. (September 2014). "An Ontological Analysis of Service Modeling at ArchiMate's Business Layer". 2014 IEEE 18th International Enterprise Distributed Object Computing Conference. IEEE. pp. 92–100. doi:10.1109/edoc.2014.22. ISBN 978-1-4799-5470-4. 
  34. "ArchiMate® Model Exchange File Format for the ArchiMate 3.0 Modeling Language". 

Further reading

External links