Aggregated enterprise architecture wisdom
Gerben Wierda 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 →
There are not many images in the Chess and the Art of Enterprise Architecture book. But the type of paper and the size of the book make some of them only borderline readable. Some people have reported trouble reading them, especially … Continue reading →
As soon as you, as an enterprise architect, want to address the problem of the complex Business-IT landscape, and you actually acknowledge in a discussion that Enterprise Architecture has come into existence because of the complexity of modern IT-laden landscapes, … Continue reading →
Short update. For those who would like to discuss Enterprise Architecture with me in person: I will be presenting at the Gartner EA Summit London 2015 on May 20th 2015 in London UK and I will be giving the closing keynote (in … Continue reading →
Short update. For those who would like to discuss Enterprise Architecture with me in person: I will be presenting at the Gartner EA Summit London 2015 on May 20th 2015 in London UK and I will be giving the closing … Continue reading →
Large, complex landscapes are a pain. With hundreds of servers, hundreds of applications, thousands of users (and thus usage patterns) and a constant flux of small and large changes, few organisations are really in full control of what they actually … Continue reading →
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 →
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 →
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 →
A while back, I wrote in the blog post ArchiMate is overrated (and underrated) that using ArchiMate doesn’t really have that much added value for communicating simple, high-level views to stakeholders (users, management), but its structure does bring advantages that enables us to … Continue reading →
Recently, I had a conversation with someone about how to do enterprise architecture. I prepared that conversation by trying to condense my basic argument for the`enterprise chess‘ approach to the absolute minimum. I started out with the question: “Suppose we don’t … Continue reading →
Short post today: my new column on the Enterprise Architecture Professional Journal, titled “The (Forgotten) Other Half of SOA” has been published. A somewhat technical subject: service oriented architectures and performance issues. With a few ArchiMate views added to the … Continue reading →