Why I Like the Zachman Framework Architecture

by Ronald G. Ross

The true measure of an idea’s elegance lies in its simplicity.  By this test, the Zachman Framework Architecture is a masterpiece.  Curiously, each proponent seems to conceive his own particular set of reasons for liking it.  Not to detract from others, here are mine.  They read like a litany for IRM.

• Because architecture is important.  Significant investment in constructing anything of substantial complexity or duration is made most wisely following a prior blueprint.  We know this to be true for skyscrapers, microchips, space shuttles, and home remodeling; the Framework supports it for information systems.
  
  
• Because perspective is important.  “Perspective” is a term sometimes used for a row in the Framework.  Clearly, the perspective relevant to the user is not the same as the perspective relevant to the designer, which is not the same as the perspective relevant to the builder, etc.  This is a simple insight, but sterling nonetheless.
  
  
• Because communication is important.  The columns of the Framework mandate the questions:  what, how, where, who, when, and why.  This guidance is both clear and complete.  Perspectives (as above), plus what questions to ask, equals matrix for communication.
  
  
• Because data is important.  Putting the question “what” (data) on an equal footing with “how” (process) runs counter to those basic habits of the industry that IRM professionals constantly battle.  The Framework stands out for that simple, yet courageous act.
  
  
• Because integration is important.  The essence of integration is unifying facts.  This is as true for systems of methodologies (meta-systems) as it is for systems of regular business information.  Think of the Framework as a comprehensive guide to unification (integration) of meta-facts.  This is subtle -- but elegance usually is.
  
  
• Because innovation is important.  The Framework is not complete, especially the three new columns.  But it permits us to grasp where completeness lies, and how to judge when we’ve achieved it.  For me, this methodological bootstrapping is a final stroke of brilliance.

standard citation for this article: Ronald G. Ross, "Why I Like the Zachman Framework Architecture," Data Base Newsletter, Vol. 19, No. 4, (Jul./Aug. 1991), URL:  http://www.BRCommunity.com/a1991/a217b.html.

September/October 1997

Implementing Application Packages: Is There A Better Way?

By Ronald G. Ross

July/August 1997

'Why' is Why Business Rule Methodology is Different

By Ronald G. Ross

May/June 1997

Never-ending On-the-Job Training

By Ronald G. Ross

September/October 1996

Re-Usability in the Business Rule Approach

By Ronald G. Ross

March/April 1996

The Newest Idea In Business Rules: Rules Normalize!

By Ronald G. Ross

January/February 1996

An Open Letter to DBMS Vendors: We Need Active Database Systems

By Ronald G. Ross

May/June 1995

The Greatest Irony Of The Information Age: Business Rules

By Ronald G. Ross

November/December 1995

Business Rules: Knowledge For Knowledge Workers

By Ronald G. Ross

March/April 1994

"Play Ball!"

By Ronald G. Ross

November/December 1999 & January/February 2000

Enterprise Architecture: Issues, Ingibitors, and Incentives

By John A. Zachman

July/August & September/October 1999

Packages Don't Let You Off The Hook

By John A. Zachman

November/December 1988

The History Of Steam-Powered Ships

By Ronald G. Ross

January/February & March/April 1999

Life Is a Series of Trade-Offs and Change Is Accelerating!

By John A. Zachman

January/February 1994

"Business Rules, At What Cost?"

By Ronald G. Ross

November/December 1998

"Yes Virginia, There IS an Enterprise Architecture"

By John A Zachman

May/June 1994

Business Rules:  Birth of a Movement

By Ronald G. Ross

January/February 2000

Business Systems And Information Support Systems 

By John Hall

July/August 1998

Enterprise Architecture:  Looking Back and Looking Ahead

By John A. Zachman

July/August 1991

Why I Like the Zachman Framework Architecture"

By Ronald G. Ross

January/February 1998

The Framework for Enterprise Architecture (The 'Zachman Framework') and the Search for the Owner's View of Business Rules

By John A. Zachman

March/April 1997

Business Process Re-Engineering

By Ronald G. Ross

Ronald G. Ross is Principal and Co-Founder of Business Rule Solutions, LLC, where he actively develops and applies the IPSpeak^™ methodology including RuleSpeak^®, DecisionSpeak^™ and TableSpeak^™.

Ron is recognized internationally as the "father of business rules." He is the author of ten professional books including the groundbreaking first book on business rules The Business Rule Book in 1994. His newest are:

• Business Rule Concepts: Getting to the Point of Knowledge
  (4th edition, 2013)

• Building Business Solutions: Business Analysis with Business Rules
  with Gladys S.W. Lam (2011, An IIBA^® Sponsored Handbook).

Ron serves as Executive Editor of BRCommunity.com and its flagship publication, Business Rules Journal. He is a sought-after speaker at conferences world-wide. More than 50,000 people have heard him speak; many more have attended his seminars and read his books.

Ron has served as Chair of the annual International Business Rules & Decisions Forum conference since 1997., now part of the Building Business Capability (BBC) conference. He was a charter member of the Business Rules Group (BRG) in the 1980s, and an editor of its Business Motivation Model (BMM) standard and the Business Rules Manifesto. He is active in OMG standards development, with core involvement in SBVR.

Ron holds a BA from Rice University and an MS in information science from Illinois Institute of Technology. For more information about Mr. Ross, visit www.RonRoss.info, which hosts his blog. Tweets: @Ronald_G_Ross