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…

What is wrong with this picture?

Time for another — this time very short — educational quiz post. Look at the following diagram (in the Mastering ArchiMate colour scheme). Is this OK? [Completed post (from this point on) revealed on 21/Sep/2016] First, let's look at why this…

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…

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…

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…