Reusable Infrastructure Modelling Patterns (2)

In the previous post, Reusable Infrastructure Modelling Patterns, I discussed the creation of reusable patterns to more effectively model large homogenous parts of the infrastructure landscape, or in other words: if you have 1000 identical RHEL servers, dbmodelling the structure of each of these individually is not what you would like. The post contained a quiz with two questions. The answers and my proposed reusable pattern solution is given in this post. Warning: like the previous post this is not ‘beginner ArchiMate’. So if you’re new to the language, don’t get scared away by this complex story. Continue reading

Posted in Using ArchiMate | Leave a comment

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 add that much value to simple diagrams, we can delve deeper into modelling large infrastructural landscapes in enough detail so that useful analysis is possible. Continue reading

Posted in Discussing ArchiMate, Using ArchiMate | 11 Comments

Two appearances: Gartner EA Summit (UK) and MBT Conference (NL)

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 Dutch) at the MBT Congres 2015 on May 21st 2015 in Houten NL.

Posted in Uncategorized | Leave a comment

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, the frustration with the direction of ArchiMate’s Used-By may remain, it is not always a passing problem for someone new to ArchiMate. Maybe the following helps in the discussions about Used-By. Continue reading

Posted in Discussing ArchiMate, Using ArchiMate | 7 Comments

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 is a relation, but it looks like an element. Somehow, it stands for a relation between all the elements grouped, but modelling-wise, it does not relate to any other part of a model. It’s a bit reminiscent of the phrase ‘the sound of clapping with one hand’. Continue reading

Posted in Discussing ArchiMate | 2 Comments

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 set of lines and boxes in a presentation, the precision does not make things by definition clearer.

Continue reading

Posted in Discussing ArchiMate, Using ArchiMate | 8 Comments

About analysis of ArchiMate models

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 model large (detailed) landscapes. Such models have an essential advantage when they are modelled not just graphically, but in a real ArchiMate modelling environment: it opens the Business-IT landscape for useful analysis. But, to be practically able to do analysis, there are limits to our freedom of modelling. Continue reading

Posted in Using ArchiMate | 4 Comments