Architecture Corner: We are special – Seven Deadly Sins of IT

Episode 6 of this season of Architecture Corner is out (I made a guest appearance in episode 1, “Good at Innovation”). In this installment, the CIO is a glutton for new data center capacity. Chris the CEO (Casimir Artmann) and John the CIO (Greger Wikstrand) are convinced that “we are special”. Can Ann the CFO […]

PICNIC

User error has many synonyms such as layer 8 error or error 18 indicating that the problem is 18 inches away from the computer. I personally still prefer PICNIC (Problem In Chair, Not In Computer), as it is the easiest to remember. For me user error is a fact of life and as architects we … Continue reading PICNIC

The bucket-list – a keyword-schema

I’ll admit it: there’s an awful lot of stuff on this website of mine. And there are so many tools and suchlike here that it can be difficult to find one’s way around, or to work out which tools to

The bucket-list – changing direction

I’ve given up on enterprise-architecture. Why? Several reasons, really. The main one is that, even now, enterprise-architecture still isn’t enterprise architecture – and there are still massive vested-interests against its ever being so. Its literal meaning should be ‘the architecture of the enterprise‘;

At IASA Ireland 2017

I’ve spent the past week in Ireland, first in Dublin at the IASA Ireland 2017 conference (co-hosted by ICS, the Irish Computer Society), and also at a follow-on event organised by Gar Mac Críosta. Paddy Baxter‘s theme for the conference

The Present and Future of the ArchiMate® Language – Part 2

Welcome to the second in a series of blog posts on The Present and Future of the ArchiMate® Language. With the release of the ArchiMate 3.0 Specification last year, we now have a complete enterprise description language that has been adopted by architects worldwide in a wide range of organizations. It is now time for The Open Group ArchiMate Forum to reach out to users and better understand how the language is being used and how it should evolve. Therefore, the following post, like all others in this series, reflects the views of its authors, and will benefit from comments and discussion. You may refine, expand upon, or even disagree with elements of the post. Regardless, you will be shaping the future of the ArchiMate language.

So please, enjoy and engage!