This blog is about actionable enterprise architecture, and is written by jeff kennedy, who currently serves as the Enterprise Architecture Manager within the IT Strategy, Policy, & Planning division of a large university in New Zealand.
My background is in enterprise application integration, and my enterprise architecture practice is mainly at the upper layers of the architecture stack: business, data, application, modelling, code… so there won’t be much here about the lower layers of the stack (networking, infrastructure, etc).
The approach for actionable architecture tends to be lighterweight in terms of traditional enterprise architecture frameworks, and aims to establish sustainable contemporary best-practice patterns using techniques and processes that have been referred to as “semi-structured non-hierarchical socially-networked deterritorialised pragmatic optimism”. This has been influenced by approaches such as the Burton Group reference architecture, which sets out:
- principles, which give rise to
- technical positions, which give rise to
- solution templates
All of this certainly doesn’t mean there is any disdain here for traditional frameworks such as Zachman and TOGAF, but it does herald a new approach to how those frameworks are interpreted, populated, and relied upon for actionable enterprise architecture to guide decision-making and lead to the embedding of flexible, repeatable, reusable, and sensible patterns throughout the architecture stack.