Aggregated enterprise architecture wisdom
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 →
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 →
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 →
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 →
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 →
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 →