ArchiMate ( / ɑːr . K ɪ m eɪ t / AR -ki-Mayt ) is an open and independent enterprise architecture modeling language to supporting 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 the standard IEEE 1471 concepts . 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 ict enterprise modeling scope. [3]


ArchiMate offers a common language for describing the construction and operation of business processes , organizational structures, information flows , IT systems, and technical infrastructure. This is an architectural drawing of a building in which the building is constructed. This insight helps the various 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: [4] It Divides the enterprise architecture into a business, and technology implementation layer. In each layer, three aspects are considered: active elements that exhibit behavior (eg Process and Function), 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, which are used for modeling individual domains, for example, the UML for modeling software products., [5] and BPMN which is used for business process modeling.


ArchiMate is partly based on the 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, 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 , Dutch Tax and Customs Administration and the ABP . [6]

The development process lasted from July 2002 to December 2004, and took about 35 million years. The development was funded by Dutch government and ABN AMRO and the ABP Pension Fund. [7]

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

In June 2016, the Open Group released [11] version 3.0 of the ArchiMate Specification. [12] Version 3.0 adds [13] enhanced support for capability-oriented strategic modeling , new entities for physical resources (for modeling the ingredients, equipment and transport resources used in the physical world) and a general metamodel showing the entity types and the relationships Between them.

ArchiMate topics

ArchiMate is an integrated architectural approach that describes and visualizes the different business domains and their relationships. Using these integrated architectures, the impact of design choices and changes.


Organizations need to adapt increasingly fast and anticipate changing customer requirements and business goals. This need to influence the whole chain of activities of a business, from the organizational structure to the network infrastructure. How can you control the impact of these changes? Architecture may be the answer.

Architecture is a consistent set of principles, methods and models that are used in the design and realization of organizational structure, business processes, information systems, and infrastructure. However, it is difficult to judge the effects of proposed changes. Everyone speaks its own language, draws its own models, and uses its own techniques and tools. Communication and decision making across domains is seriously impaired.

ArchiMate provides this integration. ArchiMate is an architecture and visualization techniques that picture the domains and their relations. ArchiMate will provide the architect with tools that support and improve the architecture process.


View model of ArchiMate Architectural Framework.

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 we are concerned with the use of the concept of a particular language, In this context, we distinguish three main layers: [1] [7]

  • 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 a software application that supports applications in applications.
  • The Technology Layer deals “with the hardware and communication to the media infrastructure Application Layer. This layer offers infrastructural services needed to run applications Realized by computer and communications hardware and system software.”

Each of these layers can be further divided into sub-layers. For example, in the Business Layer, the primary business processes are: 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, modeling the external customers that make use of the services of the organization.

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 realization relations: elements in lower layers; Eg, a ‘data object’ (Application layer) may realize a ‘business object’; Or ‘artifact’ (Technology layer) may be applied to the application layer.

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, we distinguish the structural or static aspect and the behavioral or dynamic aspect. Behavioral concepts are given to structural concepts, to show who or what displays the behavior. In the example, role, interface and collaboration are assigned to business process, organizational service and business interaction, respectively.

Second, we make a distinction between an external view and an internal view on systems. When looking at the behavioural aspect, these views reflect the principles of service orientation in the previous section. The service concept represents a unit of essential functionality that a system exposes to its environment. For the external users, this external functionality, together with non-functional aspects. If required, this may be done in accordance with the. Services are accessible through interfaces, which constitute the external view on the structural aspect.

For the purposes of this paper, we present the results of the internal and external evaluation of the services and interfaces. For this realization, we make a distinction between behavior that is performed by an individual structural element (eg, actor, role component, etc.), or collective behavior.

In addition to active structural elements, we also recognize passive structural elements, ie, the objects on which behavior is performed. In the domain of information-intensive organizations, which is the main focus of our language, these are usually information objects in the business layer and data objects in the application layer, but they may also be used to represent physical objects.

Exchange File Format

ArchiMate 2.1 models. [14] This is an XML / XSD based file format, and is intended for exchange rather than a persistent file format. Tools Archi, BiZZdesign Architect and Corso System Architect. [15]

Software Tools

BiZZdesign Architect 4.3.1 screenshot, example.

The following applications support or have supported Archimate models:

  • ABACUS from Avolution (certified as an ArchiMate 2 Tool)
  • ADOIT from the BOC Group
  • Archi (ArchiMate 3.0 compliant, free and open-source )
  • ArchiMedes , architecture publishing platform (ArchiMate 2.1 compliant) [16]
  • ArchiMetric from Visual Paradigm [17]
  • ARIS ArchiMate Modeler by IDS Scheer [18]
  • BiZZdesign Enterprise Studio [18] (certified as an ArchiMate 2 Tool)
  • Corporate Modeler by Casewise [18]
  • Corso ArchiMate Plugin for IBM System Architect
  • Corso Agile EA (certified as an ArchiMate 2 Tool)
  • Dragon1 EA Method
  • Sparx Systems Enterprise Architect
  • Innovator by MID
  • IServer by Orbus Software (certified as an ArchiMate 2 Tool)
  • HOPEX from Mega International (Archimate 2.1, partial support in MEGA HOPEX V1R3)
  • Metis by Troux Technologies [18]
  • Modelio – open source edition – (certified as an ArchiMate 3 Tool) [4]
  • Modelio – commercial edition distributed by Modeliosoft (certified as an ArchiMate 3 Tool) [5]
  • PlantUML generates ArchiMate from Text [6]
  • QualiWare Lifecycle Manager by QualiWare
  • QPR EnterpriseArchitect (AchiMate 2 compliant)
  • Signavio Process Manager (ArchiMate 3.0 compliant)
  • UNICOM System Architect [18] (ArchiMate 3.0 compliant)

The Open Group has a list of the certified tools at. [19] ArchiMate 2 Tool certification requires support for the ArchiMate 2.1 Specification.


  1. ^ Jump up to:b What is ArchiMate? At from Accessed April 19, 2014
  2. Jump up^ ArchiMate Certificationat Accessed January 11, 2014.
  3. Jump up^ Pallab Saha (2008)Advances in Government Enterprise Architecture. p.39.
  4. Jump up^ The ArchiMate Framework, in:ArchiMate® 2.1. Accessed 06.2015.
  5. Jump up^ Zoran Stojanović et al. (2007). Service-oriented Software System Engineering. p.145-146.
  6. Jump up^ Telematica Instituut (2006) Annual Report 2005 . p.7. Accessed Jan 18, 2009.
  7. ^ Jump up to:b ArchiMate: Its Time Has Come? Enterprise Architecture Demystified. Posted by snair007 on August 3, 2008
  8. Jump up^ The ArchiMate Forum
  9. Jump up^ ArchiMate 1.0 Specification
  10. Jump up^ The Open Group (2012), ArchiMate 2.1 Specification
  11. Jump up^ Archimate Overview [1]
  12. Jump up^ ArchiMate v3.0 Specification [2] . Accessed June 27, 2016.
  13. Jump up^ What’s new in the ArchiMate 3.0? [3] . Accessed June 27, 2016.
  14. Jump up^ The Open Group Exchange File Format
  15. Jump up^ The Open Group Webinar about the Exchange File Format
  16. Jump up^ ArchiMedes
  17. Jump up^ ArchiMetric web site
  18. ^ Jump up to:e Glissman, Susanne, and Jorge Sanz. ” A comparative review of business architecture .” IBM Research Report, 2009.
  19. Jump up^

Leave a Comment

Your email address will not be published. Required fields are marked *