ArchiMate
Introduction to ArchiMATE
ArchiMate is a modelling language standardised by The Open Group, specifically developed for the abstract and straightforward description of enterprise architectures. At its core, ArchiMate defines three layers that cover various aspects of enterprise architecture:- Business Layer
- Application Layer
- Technology Layer
Fig. 1: The ArchiMate Layers
Motivation Layer
Strategy Layer
Business Layer
Application Layer
Technology Layer
Physical Layer
Implementation & Migration Layer
The language elements in ArchiMate are categorised into three groups: Active Structures, Passive Structures, and Behaviour. Each layer contains model elements to describe these categories, and Enterprise Architect (EA) conveniently lists these elements in the toolbox for ease of use.
For example, to describe the statement “John reads a book”:
- John represents the active structure (in this case, a business actor element from the business layer).
-
Reads represents the behaviour (a business process element that describes how John reads).
-
Book represents the passive structure (a business object element).
Fig. 2: ArchiMate Toolbox
Fig. 3: The ‘active-behaviour-passive’ pattern
The segmentation of the ArchiMate model elements into Active-Behaviour-Passive runs through all ArchiMate levels, with the exception of the Motivation and Implementation levels. However, each level has a different focus, so different statements can be made with the Active-Behaviour-Passive pattern in each level, but the structure of the statement always follows the same pattern.
Reuse & creation views
In a tool like EA, model data is separated from its graphical representation, allowing easy reuse across multiple diagrams. When model data is updated, all associated diagrams are automatically updated, making it easy to maintain consistency.
Standardised language
ArchiMate provides a standardised language with elements and relationships that create a knowledge graph, which EA can process in various ways.
Linking standards
EA allows for linking elements from different modelling languages, for example, linking ArchiMate Business Process elements with BPMN Business Process elements for more detailed descriptions. Additionally, UML classes and components can be used to refine ArchiMate DataObjects and ApplicationComponents when stakeholders require more details.
By linking relevant information across models for different stakeholders, EA becomes a powerful tool for enterprise architecture, offering a flexible and comprehensive modelling environment.
Motivation layer: Describes the motivations, drivers, and goals behind a company’s decisions and activities.
Strategy layer: Models the strategic aspects of the company, including goals, principles, and motivations.
Business Layer: Focuses on organisational structures, processes, and roles. This layer links the operational business to strategic goals.
Business processes, organisational structures, business objects and the relationships between them are modelled in this layer. The aim is to connect and understand the operational business with the company’s strategic goals and business requirements in order to communicate them better.
Application layer: Describes the applications that support and automate business processes, including internal and external applications.
The application layer can include both internal and external applications and their interactions.
Application architectures, application components, data objects and interfaces between applications are modelled in this layer. The aim is to understand the IT systems and create links to the business layer in order to describe which applications support the organisation’s business.
The connection between the business layer and the application layer helps to answer the following questions:
- Which business process or business service is provided by which applications (applications)?
- Which business services can no longer be offered if a particular application is no longer available?
- Which business data is stored in which data objects?
- Which application uses which (personal) data? (GDPR)
- In which database application is the data required in the business stored?
- and much more
Fig. 4: The “Motivation Layer” Toolbox
Fig. 5: The “Business Layer” Toolbox
Fig 6: The “Application Layer” Toolbox
Technology layer: Defines the technological infrastructure that supports the applications, including hardware, software, and networks.
This includes hardware, software, networks, databases and other technical resources. Technology architectures, infrastructure components, data objects and the relationships between them are modelled in this layer.
The aim is to understand the technological environment that supports the applications to ensure that it is reliable, secure and scalable.
The connections between the technology level and the application level help to answer the following questions:
- Which application is running on which physical device (technology layer)?
- Which applications are affected if a server fails?
- It is possible to automatically deduce how the failure of a technology component affects the business (business layer).
- Which business services will no longer function if a server fails?
- and much more
Physical layer: Models the physical infrastructure, such as servers, workstations, and other hardware components.
The physical components such as hardware, networks and devices that are required for the operation of IT systems and applications are modelled here. The physical layer includes elements such as servers, workstations, storage devices, network components and other physical units that form the basis for the provision of IT services. By modelling the physical layer, companies can better plan, manage and optimise their IT infrastructure to ensure the performance, security and availability of their systems.
In terms of presentation, the two layers differ in the detailed elements that they model. For example, concepts such as infrastructure services and system software can be modelled in the technology layer, while hardware components such as servers and storage devices are modelled in the physical layer.
Fig. 7: The “Technology Layer” Toolbox
Fig. 8: The “Implementation Layer” Toolbox
Concepts such as infrastructure services and system software are modelled, while hardware components such as servers and storage devices are modelled in the physical layer.
Implementation and migration layer: Describes the implementation of changes in enterprise architecture, including system developments, new technologies, and migration projects.
Together, these seven levels form a comprehensive model of the enterprise architecture and make it possible to understand and visualise the relationship between business processes, applications and technology infrastructure. They provide a framework for analysing, planning and communicating changes in the enterprise architecture.
However, in order to create an enterprise architecture, it is not necessary to fill all seven levels with information! ArchiMate merely provides a framework and suitable language elements to map and link the required information with the symbols defined in ArchiMate and to offer standardised semantics. With Enterprise Architect’s ability to integrate other modelling languages according to defined rules via the ArchiMate boundary, you have the option of creating your enterprise architecture with all modelling languages used in practice.
The requirements depend on the stakeholders and the questions to be answered by the model. This requires a suitable modelling approach. There are best practices for this, which can be customised according to your purposes.
motivation-viewpoint
strategy-viewpoint
business-process-cooperation-viewpoint
application-cooperation-viewpoint
capability-map-viewpoint
organization-viewpoint
information-structure-viewpoint
requirements-realization-viewpoint
principles-viewpoint
outcome-realization-viewpoint
service-realization-viewpoint
archimate-cross-layer-relationships
FAQs on ArchiMate
Why is Archimate the best EAM modelling language?
ArchiMate is an addition to the popular TOGAF (The Open Group Architecture Framework), which together with the Architecture Development Method (ADM) offers a process model for the development of technical architectures. Both are constantly being expanded by The Open Group and are widely used in the EAM sector.
ArchiMate has been undergoing further development for years and now offers a large community with extensive experience in its use. With 60 concepts and 11 relations, it covers the most diverse levels of an organisation and can be supplemented with additional frameworks if required. Thanks to its flexibility and expansion options, ArchiMate has secured itself a leading position in the field of EAM modelling.
What are the challenges with the EAM modelling language ArchiMate?
ArchiMate is a widely used EAM modelling language (Enterprise Architecture Management). It supports companies and organisations in linking IT and corporate strategy. Although the language offers many advantages, some challenges should also be taken into account:
- Complexity: ArchiMate is a complex modelling language and has many concepts, relationships and notations. This makes learning and using the language time-consuming. Inexperienced users are easily overwhelmed by the multitude of elements, which can impair communication in EAM projects.
- Maintenance effort: Complex Archimate EAM models pose major challenges in terms of consistency and accuracy. The large number of interlinked elements requires a great deal of attention during maintenance.
How can I improve my ArchiMate skills?
As the ArchiMate modelling language is highly complex, professional training helps you to quickly benefit from the advantages of ArchiMate. You will also learn that, in addition to the language (ArchiMate), you need a tool (e.g. Enterprise Architect), a method and as much experience as possible (best practice) for successful modelling.
Our Academy for Professional Modelling by SparxSystems Central Europe offers a basic training course on ArchiMate with Enterprise Architect. All information about the training can be found here.
In a suitable training course, you will first learn the ArchiMate symbols and their meaning and will thus be able to interpret each diagram correctly. In the next step, you will learn which concepts and constructs are appropriate in which situations. In this way, you can develop enterprise architectures to describe the structure, behaviour and composition of a company or organisation.
Ultimately, you will find answers to the following questions:
- What is enterprise architecture?
- Why should I use Archimate?
- The language concepts of Archimate?
- How do I structure my model when I use Archimate?
- Which questions can be answered with Archimate viewpoints?
- How do I model an enterprise architecture with Archimate?
For which topics and industries is ArchiMate particularly suitable?
The ArchiMate language is widely used in industries such as information technology, telecommunications, finance and administration. It focuses on the description of business, applications and technologies with predefined language elements at a higher level of abstraction.
