Aggregated enterprise architecture wisdom
Gerben Wierda I’m working on a few more serious things, but in the meantime I did not want to let this happen silently. The animation Why Enterprise Architecture (“Meet Michael”) is now (clearly, 2000 views more than the next one) the most … Continue reading →
Confronted with the problems of Waterfall approaches, organisations are all…
…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 →
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 →
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 →
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 →
Time for another — this time very short — educational quiz post. Look at the following diagram. Is this OK?
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 →
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 →
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 →
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 →
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 →