Agile & Architecture
Confronted with the problems of Waterfall approaches, organisations are all…
Gerben Wierda
The ArchiMate 3.0 Relations Table…
…has serious, and many, errors. According to my personal analysis, around 150 valid relations are missing, and potentially more than 2000 relations that are in that table shouldn’t be, if the text of the standard is to be believed. Here … Continue reading →
Agile & Architecture
Confronted with the problems of Waterfall approaches, organisations are all jumping on the Agile bandwagon. This is often a very good thing. Big Up-Front Design (BUFD) has many drawbacks in volatile environments and much of what happens in IT happens … Continue reading →
Another Milestone
It has been almost a month ago that it happened (but I had other things one my mind), but it did happen. This blog passed the 300,000 views mark and also the 100,000 viewers mark. Thank you all for reading, … Continue reading →
Who’s in Charge? (Layers? What Layers! — 2)
ArchiMate 3, at first glance, looks like a very orthodox IT-oriented enterprise architecture modeling langage. It can show how the business is supported (‘service-oriented’) by applications which are supported (‘service-oriented’) by infrastructure. This has been the Core of ArchiMate’s view … Continue reading →
What is wrong with this picture?
Time for another — this time very short — educational quiz post. Look at the following diagram. Is this OK?
ArchiMate 3.0 metamodel PDF
I’ve created a PDF that you can print two sided (and laminate if you like) to have easy access to the ArchiMate 3 metamodel.On the front it contains the Core meta-model. It is depicted in the Mastering ArchiMate colour scheme (this … Continue reading →
An AchiMate 3 Map (Layers? What Layers! — 1)
ArchiMate 3 is setup with 5-6 layers (Strategy, Business, Application, Technology/Physical, Implementation) and 4 aspects: (Passive and Active) Structure, Behaviour and Motivation. Quoting the standard: This looks daunting until you realise that not everything that is called a ‘layer’ is … Continue reading →
Follow-up to “Is ArchiMate Open?”
A (concluding) piece about the licensing issues surrounding ArchiMate has been published over on Chess and the Art of Enterprise Architecture. Published there, because it is not so much about ArchiMate modelling or the language, but about legal issues and … Continue reading →
ArchiMate 3: What do the license changes mean?
With the release of ArchiMate 3, The Open Group has changed the text of the license as well as their explanation. What has changed, and what does it mean? (Note, as this is not about modelling with ArchiMate but about … Continue reading →
ArchiMate 3.0: The Good, The Bad, and The Ugly
On June 14, the 3.0 version of the ArchiMate standard was unveiled during the Enterprise Architecture Conference Europe 2016. Time for a review. I’ve divided it up in The Good, The Bad, and The Ugly, with The Good standing for changes … Continue reading →
Process Modelling in ArchiMate in BiZZdesign Architect
A short while ago I wrote about using ArchiMate to model processes instead of the (agreed, vastly superiour) BPMN language. What I did was change the visuals on ArchiMate elements to support this and I also did a few things … Continue reading →