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 on the enterprise since the beginning. Physical processes and materials have been added to ‘infrastructure’ (which has been renamed to ‘technology’) but even with that we still are in effect talking about a classic BAT-stack (Business–Application—Technology).
From ArchiMate 3 on, however, this strict layering has been loosened in an important way. Continue reading
Time for another — this time very short — educational quiz post. Look at the following diagram (in the Mastering ArchiMate colour scheme). 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. 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:
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 questions about ‘openness’. Just mentioning it here for those that are interested in such matters.
The previous article was Is ArchiMate Open? Not Really.
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 I like (even if I might also have critical remarks later on), The Bad standing for fundamental issues I have with the language or the direction it is going, and The Ugly for a list of small issues, inconsistencies, etc.
It’s taken me a while, but, hey, it’s over 6000 words and there is a reward at the end (don’t peek!). Warning: this article is meant for enterprise architecture modelling / ArchiMate geeks, and the insatiably curious.
Enjoy. Continue reading
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 that are not (strictly) ArchiMate 2.1 compliant. But it is practical if your demands do not require the power of a real process modelling language such as BPMN. Continue reading