How does the API-economy differ from the SOA approach of the past? An ArchiMate answer.

These days, there is a lot of talk about the ‘API Economy’: a world filled with systems providing services to other systems using (above all RESTful) services. It would be easy to miss the fact that this isn’t new at…

The ArchiMate 3.0 Relations Table…

...has serious, and many, errors. According to my personal analysis, 152 valid relations are missing, and potentially 2941 relations that are in that table shouldn't be, if the text of the standard is to be believed or if we use some common sense.…

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…