Aggregated enterprise architecture wisdom
Sadly it is very easy today to deny social responsibility while appearing to do so. Architects are no exceptions so it is important to catch the signs of architects doing this, even if that may be yourself. The easiest denial in architects and the mildest form are architects that constantly appeal to higher authority such … Continue reading Denial of responsibility →
Just a quick note, this one, to document an item that came up somewhen during my recent travels. Several of the workshops had focussed on the SCORE frame, to help people map out themes that were relevant for strategy and…
One of the huge challenges of trying to make things simple in a complex context is that often it can make at first make things seem more complicated. For a while, anyway, until things settle down a bit, and the…
It has been a while ago but I’m happy to share some additional results of my PhD. I will present on the upcoming Conference on Business Informatics (CBI2016) a paper called “Enterprise Architects Should Play Different Roles”. The paper is … Continue reading →
In our previous blog, we outlined some of the most important changes in relationships in ArchiMate 3.0. But there is more… This blog will discuss changes relating to the Grouping and Junction concepts.
It seems like everyone wants to be an innovator nowadays. Being “digital” is in – never mind what it means, you’ve just got to be “digital”. Being innovative, however, is more than being buzzword-compliant. Being innovative, particularly in a digital sense, means solving problems (for customers, not yourself) in a new way with technology. […]
Quantum Universal Exchange Language Implicate order and explicate order are concepts coined by David Bohm to describe two different frameworks for understanding the same phenomenon or aspect of reality.He uses these notions to describe how the same phenomenon might look different, or might be characterized by different principal factors, in different contexts such as at different scales. Macro […]
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 →
In our previous blogs, we have mainly focused on the new layers and elements of the ArchiMate 3.0 language. Although these concepts are the first changes that catch the eye in ArchiMate 3.0, there are also several improvements in the use of relationshi…
Kind of a personal landmark, I guess: today I reach so-called ‘retirement-age’, where I’m supposedly meant to kick back, relax and walk away from all of the stresses of a lifetime of work. Hmm… no chance of that happening, is…
Unless you’re living under a rock, it’s a near certainty that you’ve seen at least one Downfall parody video (although I hadn’t realized just how long these had been around until I started working on this post…time flies!). There’s a reason why they’ve managed to hang on as a meme as long as they have. […]
Recently I met with an urban planner in relation to a planned digitisation project. He was highly critical on the lacking understanding and foresight of business, enterprise and solution architects in his domain. He even went as far as saying that he as trained and chartered architect could not see the fundamentals that made architects … Continue reading When architecture meets architecture →