Open Letter to TOG #2
Dear TOG, I hope this letter finds you well. As shepherd of the ArchiMate standard, you are currently working on its next iteration. As I am not part of the ArchiMate Forum, I am going to send you a few … Continue reading →
Discussing ArchiMate
Open Letter to TOG #1
Dear TOG, I hope this letter finds you well. As the shepherd of the ArchiMate standard, you are currently working on its next iteration. As I am not part of the ArchiMate Forum, I am going to send you a … Continue reading →
What is wrong with this #ArchiMate picture?
A short one today. I have a view taken from a certain book. The view contains an error, can you spot it? And when you have spotted it, go to the ArchiMate 2.1 Specification and can you tell me what … Continue reading →
Reusable Infrastructure Modelling Patterns
A while back, I wrote the post Modelling Homogenous Landscapes in #ArchiMate (Classes and Instances), which was a first post on modelling detailed infrastructure landscapes. Assuming you’re with me that a modelling language is very useful for large complex situations, but doesn’t … Continue reading →
Used-By Redux
The direction of arrow of the Used-By relation is a constant source of entertainment and/or frustration, see for instance this (started by Sol Kahn, 37 comments) and this LinkedIn discussion (started by Michiel Perdeck, 40 comments). As the latter discussion shows, … Continue reading →
The #ArchiMate Wish List: Group
Did you ever wonder what a strange beast the Grouping Relation in the ArchiMate zoo of elements and relations is? According to the standard it is a ‘relation’. It is, however, one of the weirdest elements of ArchiMate. Officially it … Continue reading →
ArchiMate doesn’t make communication to management easier
Architects generally wrestle with the problem of communicating their complex world of dependencies to stakeholders. Those that created the ArchiMate language hoped that making a better language would enable clearer communication. While ArchiMate does enable more precise communication than your average … Continue reading →
Modelling Self-Service in #ArchiMate
I wrote a post on Chess and the Art of Enterprise Architecture about ways to look at self-service from an architectural perspective: “I, Robot” – there is no such thing as ‘Customer Self-Service’. In it, I argue that saying that … Continue reading →
Database Triggers in #ArchiMate — And a Wish
Recently, in a discussion in the ArchiMate LinkedIn Group, Tarun Godhwani started a discussion on modelling the triggers and tables of a database. Of course, one can wonder if it is useful to model these, but in case they are, the … Continue reading →
Modelling networking using the networking concepts of #ArchiMate
The rise of networking form the 1980’s onward may be considered the main driving force of the invention of enterprise architecture, itself a follow-up on what was until then known as system architecture. On the eve of the rise of … Continue reading →
Modelling Homogenous Landscapes in #ArchiMate (Classes and Instances)
This post is about two related things: modelling actual detailed architectures of large homogenous landscapes and the class versus instance issue in ArchiMate. Both are closely related. But before I start out, for those unacquainted with Object-Orientation, or Classes and … Continue reading →