Metaframeworks in practice, Part 1: Extended-Zachman

What ontology-frameworks do we need, to make sense of the enterprise-architecture of a logistics-business? This is the first of five worked-examples of metaframeworks in practice – on how to hack and ‘smoosh-together’ existing frameworks to create appropriate tools to help

On metaframeworks in enterprise-architecture

How do we avoid the dreaded ‘framework-wars’ in enterprise-architecture and elsewhere? If there’s no ‘Single Unified Framework For Everything™’, how do we ‘smoosh frameworks together’ to get the best fit for each current context? The answer: metaframeworks. And, perhaps even more, the

Ideal Circumstances for EA Frameworks

Significant touchstones, at least for some people, some of the time, the series of hype cycle devices published annually by Gartner inform and guide industry behaviours, lead and shape the formulation of strategy. Three features of the current enterprise architecture hype cycle1 are noteworthy, or thought-provoking, or self-evident: Whole-of-Government enterprise architecture has been cancelled due […]

Heal the Eternal Disconnect Between Project Managers and Enterprise Architects!

Typical exchanges between project managers and enterprise architects have historically, anecdotally, and sterotypically been predictable, unconstructive, and unsatisfactory affairs that juggle and irritate tensions across dimensions such as: enterprise context vs project scope change-friendly capability delivery2 vs project delivery methodological and framework differences open/collaborative vs closed/secret The nature of these exchanges has led to the creation of an […]

The Open Group SOA Governance Framework Becomes an International Standard

The Open Group SOA Governance Framework is now an International Standard, having passed its six month ratification vote in ISO and IEC. According to Gartner, effective governance is a key success factor for Service-Oriented Architecture (SOA) solutions today and in the future. Continue reading

Architecture-by-definition is an anti-pattern. The goal of a…

Architecture-by-definition is an anti-pattern.

The goal of a definition is to remove noise. 

You add another layer of noise when your definitions are model-specific sub-definitions for commonly understood terms. For example: service, product, capability, or system.

Special definitions introduce an additional cognitive load that easily outweighs the benefits of a more sophisticated model.