ArchiMate Modeling in Practice Overview

We are continuing our series on ArchiMate: from theory to practice! We introduced the series back in October and over the last few months we ran the first part which we called “The ArchiMate Files”. In this first part we covered some theoretic underpinnings of the ArchiMate standard, and in this second series we will cover practical aspects of modeling with ArchiMate. This is illustrated in the updated diagram below:

TOGAF 9 Poster #44 – TOGAF and ArchiMate

TOGAF and ArchiMate are two standards managed by The Open Group and are adopted by more than 80% of the world’s leading enterprises. Our poster explains how these two can be used together to support your Enterprise Architecture work. Click here to view this resource.

Related posts:

  1. TOGAF Poster 18 – Deliverables, Artifacts and Building Blocks TOGAF uses a very specific language to describe the outputs…
  2. TOGAF Poster #43 – The Sandwich Diagram Knowing the seven parts of the TOGAF documentation is very…
  3. TOGAF Poster 17 – The Architecture Repository The Architecture Repository is where architects store work outputs. This…

The ArchiMate Files – 7. Language issues

This is the seventh posting in our series on using ArchiMate in practice. So far we have considered the mind of the architect as well as several ‘fundamentals’ in the language: the structure / behavior dichotomy, three layers, internal / external aspects of each domain, specialization, and the use of views & viewpoints. In this posting we will discuss some ‘philosophical’ and practical issues that you may run into when using ArchiMate.

New: The (Mastering) #ArchiMate FAQ

A short notice today: I’ve started a (Mastering) ArchiMate Frequently Asked Questions page on this site. Via the menu or the link just given.

Categories Uncategorized

The ArchiMate Files – 6. Views and viewpoints

In this series, we have discussed various aspects of the ArchiMate modeling language using a “first principles” approach. We have covered structure vs. behavior, the three layers, (with internal / external aspects), the use of specialization, and so on. A key issue that we have often discussed is the distinction between the (mental) model of the modeler (i.e. the architect) and the visualizations that he or she creates for stakeholders in the organization. In this posting we will elaborate on that aspect.