Deconvoluting EAThere is much confusion in the Enterprise Architecture space over some of the most fundamental words in the English language: what, how, where, who, when, why. I’m afraid to say there’s some very loopy thinking out there. Zachman anticipated all this and brilliantly provided six generic models for the 6 question words. Here they are roughly as follows (and possibly needing to be adjusted slightly in his new 3.0): What: thing-relationship-thing How: input-process-output Where: site-link-site Who: role-workproduct-role When: event-cycle-event (moment-state-moment) Why: ends-means-ends For me, it’s hard to argue that these are not what each question is about from an architectural point of view. The only thing missing is how you relate instances of the 12 elements to comprehensively configure an enterprise at any given point in time. (Zachman calls these “integration relationships”. They’ve always been there, but only on the schematic in 3.0.) IMO, the best, most dynamic (agile) way to support the ‘integration relationships’ is business rules. What could possibly be better?
Tags: business agility, Business Rules, integration relationships, Interrogatives, Zachman Architecture Framework
The Zachman Framework is an Enterprise Architecture framework for ensriperte architecture, which provides a formal and highly structured way of viewing and defining an ensriperte. It consists of a two dimensional classification matrix based on the intersection of six communication questions (What, Where, When, Why, Who and How) with six rows according to reification transformations.The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes. The Framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since.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 term Zachman Framework has multiple meanings. It can refer to any of the frameworks proposed by John Zachman:• The initial framework, named A Framework for Information Systems Architecture, by John Zachman published in an 1987 article in the IBM Systems journal.• The Zachman Framework for Enterprise Architecture, an update of the 1987 original in the 1990s extended and renamed .