In this post:
Pronounced “AR-ki-mayt”, the modeling language’s name comes from a compounding of “architecture” and “animate.” The name conveys its aim to provide a way to visualize an organization’s EA.
Unlike other modeling languages such as Unified Modeling Language (UML) and Business Process Modeling Notation (BPMN), ArchiMate is designed to be narrow in its scope. The idea being that this makes the standard easier to learn and apply.
It’s narrow scope and ease of understanding could well be the driving force behind ArchiMate’s adoption within the enterprise architecture space.
Additionally, ArchiMate is often seen as a source of great background knowledge for enterprise architecture learning resources for anyone working towards becoming an enterprise architect.
Some of the key benefits of ArchiMate are:
With ArchiMate, users have a common language through which they can discuss an organization’s business processes, organizational structures, systems and infrastructure.
By establishing a recognized standard to describe, analyze and map out an organization’s EA, organizations can limit the misunderstandings and ambiguity.
Such standardization is an important factor in ensuring consistency between departments, projects and even enterprise architects themselves.
It means that stakeholders can more easily acknowledge, understand and mitigate the consequences of making changes to an organization’s systems or structure.
Parallels can be found in construction, where enterprise architecture’s nomenclature is derived. As with enterprise architecture, architects in the construction space build and label diagrams based on pre-established frameworks.
This means that the project can be reviewed by different stakeholders, and the diagrams can be untethered from any one architect.
As well as insulating the project from stalling should the/an architect leave, the approach speeds up time-to-markets by making communication more efficient.
With ArchiMate, organizations can use visual notations as a representation of their EA over time, by using “layers” and “aspects.”
Layers are broken down into business (yellow), application (blue) and technology (green), and in each layer, three aspects are noted.
The framework is populated with “concepts,” which act as visual indications of the nature of elements.
The following is an example of an ArchiMate Core Metamodel, demonstrating how concepts are structured across aspects and layers:
As with The Open Group’s Architecture Framework (TOGAF), a certification program is available for ArchiMate users.
The certification program helps maintain the standard and instills organizations with greater confidence in the enterprise architects they employ or contract.
Due to ArchiMate’s recognition within the EA discipline, ArchiMate certified architects are in greater demand and can command better salaries.
The Open Group have a number of resources that address how you can obtain an ArchiMate accreditation.
Although ArchiMate helps standardize the language we use to describe an organization’s enterprise architecture, it’s just one piece of the puzzle.
The benefits of implementing an enterprise architecture management suite (EAMS) go beyond just the benefits of using the ArchiMate modeling language.
With an EAMS, organizations can introduce more structure into the way they manage EA. Frameworks and common modeling languages help introduce efficiency, enable agility and improve collaboration.
Some enterprise architecture tools come with an array of collaborative features that make ad-hoc collaboration such as sharing PDFs look primitive in comparison.
For a more complete understanding of enterprise architecture, including its implementation and its benefits, get the erwin Expert’s Guide to Enterprise Architecture.