Archimate is a modeling language for IT architectures.

It was developed by Telin - The Telematics Institute in The Netherlands together with large companies and institutions like Capgemini, The Dutch Tax department, Getronics, Ordina, and several universities.

The Archimate language is mostly based on UML technologies. It is used to model architectures that span multiple domains. By using Archimate one can get a layered model of the business, with business- application and technology architectures in one picture. The main idea behind Archimate is that the impact of a disruption or a change in one architectural component will be reflected in other components, possibly on other layers. As an example, one can create what-if scenarios: What if we would phase out the mainframe? What components of our architecture would be affected?

The Archimate language relies heavily on a concept called Services. These services are not to be confused with the SOA services. Services in Archimate are mainly drawing techniques. The services are not necessarily implemented in software. 

Several tools are available for modeling architectures using Archimate. The best known tools are BiZZdesign Architect , ARIS ArchiMate Modeler and Casewise Corporate Modeler. There are also (free) Visio templates available if you want to gain some experience in using the Archimate symbols. Here is a quick reference of the symbols used.

Archimate's value is to create a high-level model of an enterprise architecture.

When architectures are modeled with Archimate, The next step would be to model in more detail. This should be done using techniques most suitable for the specific domain. For instance, on the application domain architectures are best modeled in more detail using UML. Technical (infrastructure) models are usually drawn using Visio.

The board of the ArchiMate Foundation and the board of The Open Group have expressed their intentions to adopt ArchiMate as an independent standard for enterprise architecture modelling and analysis under the aegis of The Open Group. This will probably make Archimate a more international standard.

This entry was posted on Friday 11 July 2008

Earlier articles

The cloud is as insecure as its configuration

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

The first computers

Open group ITAC /Open CA Certification

Sjaak Laan

Recommended links

Ruth Malan
Gaudi site
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


XML: RSS Feed 
XML: Atom Feed 


The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.


Copyright Sjaak Laan