This blog paper describes a method of defining documentation structures in the ArchiMate® notation and goes on to use a ‘driving view’ to generate output from the Archi® enterprise architecture modelling tool.
The ArchiMate notation allows for a large combination of concepts and relationships to be able to express what we need for full Enterprise Architecture modelling. However, a lot of organisations don’t initially need all this and it is sometime useful to semi-restrict what is expected. This paper defines a way of achieving this using the excellent Archi® modelling tool and its jArchi scripting language.
For a long time I have wanted to be able to get data out of the excellent Archi tool into a place where I can perform meaningful queries on it. Queries such as how are items connected, which are the most connected and so on? This blog describes the journey I went through, what I discovered and how I achieved what I wanted, and more.
How using ArchiMate can help understand a Strategy. The is an updated version of the post I made in March 2017. I've simplified some of the concepts.
I found this excellent youtube by Westpac Banking which clearly explains the Blockchain concept.
This post describes how it is possible to quickly build a solution to a real business problem, in order to see it is a viable strategic course of action. It was done to bring clarity as to what an enterprise solution might look like and how it might work, in order to stimulate stakeholder engagement and help strategic thinking: “Hacking a Strategy”.
This video from Gerben Wierda is a great introduction as to why you need an EA. It doesn't fully cover the non technical aspects such as strategy and business, but it's 3 minutes 44 seconds well spent.