Framework 7: The Zachman Framework

The Zachman framework is a model used for mapping a holistic view of an enterprise via a number of stakeholder views. Whilst it isn’t possible(or even useful) to do this framework justice here, its status as the mother and father of all enterprise architecture frameworks demands that, at the very least, a marker to it ought to precede discussion of any other enterprise architecture frameworks.

From the Wikipedia Page: The Zachman “Framework” is a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) that takes into account both whom the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed.

The Zachman Framework summarizes a collection of perspectives involved in enterprise architecture. These perspectives are represented in a two-dimensional matrix that defines along the rows the type of stakeholders and with the columns the aspects of the architecture. The framework does not define a methodology for an architecture. Rather, the matrix is a template that must be filled in by the goals/rules, processes, material, roles, locations, and events specifically required by the organization. Further modeling by mapping between columns in the framework identifies gaps in the documented state of the organization.

Current Zachman Framework (Source: Wikimedia Commons)

It’s clear that filling out an entire Zachman framework for anything but the most trivial of enterprises is a highly demanding task. However, as the Wikipedia page notes, each organisation should probably only focus in detail on the bits that are important to them: “An automaker, whose business goals may necessitate an inventory and process-driven focus, could find it beneficial to focus their documentation efforts on What and How columns. Whereas a travel agent company, whose business is more concerned with people and event-timing, could find it beneficial to focus their documentation efforts on Who and When columns. However, there is no escaping the Why column’s importance as it provides the business drivers for all the other columns.”

Much more detail is available on the official site: http://www.zachman.com/about-the-zachman-framework

FA Rating

Completeness of vision: this framework aims, above all, to be a complete representation of an enterprise.

Ability to execute: There are three levels of certification available to help use (and train others to use) the model correctly. Aspects of enterprise architecture work tend to abstract bits, out of the model to provide useful chunks to work on rather than trying to eat the whole thing at once, eg SABSA security architecture.

Overall rating: Visionary