Welcome to our blog. This is an archived post, most of our knowledge and advice remain valid but some material or links may be outdated. Click here to see our most recent posts.
This is the last posting in the Archimate series. In the series we covered the structure as well as some practical ways to use Archimate. In this last posting we will give a short summary of the ground covered, as well as direct you to resources where more information is to be found.
Blog series summary
In the introduction of this series we made the case for Archimate. Archimate fulfills the need for organizations for a way to describe the organization in a holistic way: in terms of the key components in all the domains of the organization, from business to technology, and how these components are related to each other. This view provides the insight organizations need to make decisions about necessary changes to the organization in order to stay (successful) in business.
In the subsequent postings we explained the framework and the concepts of the Archimate core. The Archimate layers cover components in the business, application and technology layer. Within the layers there are components that model behavior, components that execute behavior (structural aspect), and components that are created or used in behavior (passive aspect, usually information components).
Recently, Archimate 2.0 was published. This new version adds to the core two extensions: the motivation extension and the Implementation and migration extension. The motivation extension mainly addresses the “Why?” question. The concepts in this extension derive requirements for the architecture from stakeholder concerns, and how these requirements are resolved by the architecture. This allows for requirements traceability. The Implementation and migration extension allows for modeling a roadmap by defining states of the architecture: plateaus. This could for example be the current state and the future state. The work to be done to transition from the one state to the other can be modeled using projects and programs.
In order to optimize the use of Archimate in your organization, we recommend tailoring. We dedicated a posting to elaborate on how this can be done. Archimate allows for tailoring, after elimination of concepts that an organization doesn’t need, the framework stays consistent. The posting on viewpoints addresses an essential mechanism in Archimate: viewpoints. Viewpoints focus on a particular part of the architecture that is of interest for a stakeholder. The way how a viewpoint is presented to the stakeholder is based on how the information conveyed by the view is best understood by this stakeholder. That can be a diagram, but also a matrix, cartoon, text, or a movie clip. Whatever works best to get the message across!
In the previous posting we addressed some common situations and how to capture them in an Archimate model. This includes service oriented architectures, the visualization of an Enterprise Service Bus, and virtualization. Another topic we come across often is how to distinct between conceptual/logical models, and physical models.
Archimate tools: BiZZdesign Architect
Archimate is an open standard and can be implemented in tools by vendors. BiZZdesign offers BiZZdesign Architect and at the moment of writing it is the only tool certified for Archimate 2.0 by the Open Group. We call the tool “the native Archimate implementation”, because BiZZdesign has been closely involved in the development of the language and the extensions within the Open Group’s Archimate forum. Architect is a very comprehensive EA tool that supports intuitive and flexible modeling, analysis and the generating of Archimate viewpoints. The metamodel of the tool is Archimate by default, and the tool allows for tailoring, extending and customization of the metamodel by organizations to capture specific modeling needs. The tool also lets you allocate attributes to concepts such as documentation, metrics, cost, and life cycle information. This information can be used in (quantitative) analysis on the architecture. A repository stores the information and supports central maintenance of architectural components, reuse of architectural building blocks, import and export of data etc.
Getting started: recommended sources for more info
The goal of this blog series was to get readers familiar with Archimate so they can start using it in their own organizations. We hope you got very enthusiastic and found some practical starting points in our writings. Here we will guide you to sources you could use to use to quick start your Archimate modeling so that you can very quickly show the value that Archimate can bring to your organization!
BiZZdesign Academy offers a range of training programs in Archimate, including certification training for Archimate 2.0. For more information see www.bizzdesign.nl/academy