Subscribe to the FREE Business Rules Journal Newletter


 

 

 

     ZACHMAN ARCHIVES ...
untitled

John Zachman's Concise Definition of The Zachman Framework™

by John A. Zachman

The Zachman Framework™ is a schema — the intersection between two historical classifications that have been in use for literally thousands of years.  The first is the fundamentals of communication found in the primitive interrogatives:  What, How, When, Who, Where, and Why.  It is the integration of answers to these questions that enables the comprehensive, composite description of complex ideas.  The second is derived from reification, the transformation of an abstract idea into an instantiation that was initially postulated by ancient Greek philosophers and is labeled in The Zachman Framework™:  Identification, Definition, Representation, Specification, Configuration, and Instantiation.[1]

Since The Zachman Framework™ classification was observed empirically in the structure of the descriptive representations (the architecture) of buildings, airplanes, and other complex industrial products, there is substantial evidence to establish that The Zachman Framework™ is the fundamental structure for Enterprise Architecture and thereby yields the total set of descriptive representations relevant for describing an Enterprise.

The Zachman Framework™ typically is depicted as a bounded 6 x 6 "matrix" with the Communication Interrogatives as Columns and the Reification Transformations as Rows.[2]  The Framework classifications are represented by the Cells — that is, the intersection between the Interrogatives and the Transformations.  This matrix would necessarily constitute the total set of descriptive representations that are relevant for describing something ... anything — in particular an enterprise.

More specifically, The Zachman Framework™ is an ontology — a theory of the existence of a structured set of essential components of an object for which explicit expressions is necessary and perhaps even mandatory for creating, operating, and changing the object (the object being an Enterprise, a department, a value chain, a "sliver," a solution, a project, an airplane, a building, a product, a profession, or whatever or whatever).

The Zachman Framework™ IS NOT a methodology for creating the implementation (an instantiation) of the object.  The Framework IS the ontology for describing the Enterprise.  The Framework (ontology) is a STRUCTURE whereas a methodology is a PROCESS.  A Structure is NOT a Process.  A Structure establishes definition whereas a Process provides Transformation.

Processes based on ontological structure will be predictable and produce repeatable results (for example, Chemistry, based on the Periodic Table).

Conversely, Processes without ontological structures are ad hoc, fixed, and dependent on practitioner skills (for example, Alchemy, based on trial and error).

The Zachman Framework™ is a metamodel and, unlike a methodology, does not imply anything about:

  1. Whether you do Architecture or whether you simply build implementations — that is, whether you build Primitive Models (the ontological, single-variable intersections between the Interrogatives and the Transformations) or whether you simply build ad hoc, multi-variable, composite models made up of components of several Primitive Models.

  2. How you do Architecture:  top-down, bottom-up, left to right, right to left, where to start, etc., etc.

  3. The long-term/short-term trade-off relative to instantiating the expression of the components of the object — that is, what is formalized in the short-term for implementation purposes versus what is engineered for long-term reuse.

  4. How much flexibility you want for producing composite models (Enterprise implementations) from your Enterprise Architecture (primitive models) — that is, how constrained (little flexibility) or unconstrained (much flexibility) you make the horizontal, integrative relationships between the Cell components across the Rows and the vertical, transformational relationships of the Cell components down the Columns.

  5. Although these are significant, identifiable, methodological choices, they are not prescriptions of The Framework structure.

The Zachman Framework™ is the basis for Architecture — We know what architecture is for industrial products (buildings, airplanes, locomotives, computers, etc., etc.) because in the Industrial Age, it was the industrial products that were increasing in complexity and the industrial products that were changing.  If we had not gotten extremely sophisticated relative to architecture for industrial products, we would not likely be able to create and change complex industrial products and we would likely still be in the Industrial Age learning about Product Architecture.

Now that we are in the Information Age, it is the Enterprise that is increasing in complexity and the Enterprise that is changing.  It is my opinion that Enterprise Architecture is the determinant of survival in the Information Age.  Therefore, The Framework for Enterprise ArchitectureThe Zachman Framework™ — has some profound significance in putting definition around Enterprise Architecture, the survival issue of the Century.  We have yet a LOT to learn about Enterprise Architecture, but I submit, The Zachman Framework™ would be a good place to start.

Published with permission from Zachman International, Inc.

References

[1]  Originally described by John A. Zachman in the classic article: "A Framework for Information Systems Architecture," IBM Systems Journal, Vol. 26, No. 3, p. 276 (1987). Available at: www.zachman.com/images/ZI_PIcs/ibmsj2603e.pdf  return to article

[2]  For the latest graphic of the The Framework (Zachman Framework 3.0) visit: www.zachman.com/  return to article



standard citation for this article:
John A. Zachman, "John Zachman's Concise Definition of The Zachman Framework™," Business Rules Journal, Vol. 14, No. 4 (Apr. 2013), URL:  http://www.BRCommunity.com/a2013/b696.html  

January 2017
The Issue Is THE ENTERPRISE
By John A. Zachman


October 2016
Strategy Spectrum for Enterprise Engineering and Manufacturing
By John A. Zachman


July 2016
The New EA Paradigm
(4) The Assemble-to-Order Pattern

By John A. Zachman


June 2016
The New EA Paradigm
(3) The Provide-from-Stock Pattern

By John A. Zachman


May 2016
The New EA Paradigm
(2) The Make-to-Order Pattern

By John A. Zachman


April 2016
The New EA Paradigm
(1) Expenses and Assets

By John A. Zachman


March 2016
The Information Age: (3) Powershift
By John A. Zachman


February 2016
The Information Age: (2) The Third Wave
By John A. Zachman


January 2016
The Information Age: (1) Future Shock
By John A. Zachman


December 2015
Defining Enterprise Architecture: Economics and the Role of I.T.
By John A. Zachman


November 2015
Enterprise Physics 101
By John A. Zachman


September 2015
A Historical Look at Enterprise Architecture with John Zachman
By John A. Zachman


August 2015
Cloud Computing and Enterprise Architecture
By John A. Zachman


June 2015
The Zachman Framework Evolution (Part 2)
Special Guest: John P. Zachman


May 2015
The Zachman Framework Evolution (Part 1)
Special Guest: John P. Zachman


April 2015
Architecture is Architecture is Architecture
By John A. Zachman


April 2013
John Zachman's Concise Definition of The Zachman Framework
By John A. Zachman


November 2004
The Zachman Framework and Observations on Methodologies

 

November 2003

Framework Fundamentals: Frameworks, Reference Models, and Matrices

 

August 2003

Framework Fundamentals:  A Dialog With John Zachman

 

June 2003

Framework Fundamentals:  Miscellaneous Enterprise Engineering Concepts

 

April 2003

Framework Fundamentals:  Framework Fundamentals:  Level of Detail is a Function of a CELL

 

February 2003

Framework Fundamentals:  Responding to Questions from the OMG

 

May 2002

Enterprise Quantum Mechanics (Part 2)

 

March 2002

Enterprise Quantum Mechanics (Part 1)

 

January 2002

"What" Versus "What"

 

November 2001

Security And The "Zachman Framework"

 

September 2001

Fatal Distractions (Part 2)

 

July 2001

Fatal Distractions (Part 1)

 

May 2001

You Can't "Cost-Justify" Architecture

 

March 2001

Conceptual, Logical, Physical:  It Is Simple  (Part 2 of 2)

 

January 2001

Conceptual, Logical, Physical:  It Is Simple  (Part 1 of 2)

 

September 2000

Building The Enterprise - An Infusion Of Honesty

 

July 2000

All the Reasons Why You Can't Do Architecture or ("We Has Met the Enemy and He Is Us")

 

May 2000

Enterprise Architecture Artifacts vs Application Development Artifacts (Part 2)

 

March 2000

Enterprise Architecture Artifacts vs Application Development Artifacts (Part 1)

 

November/December 1999 & January/February 2000

Enterprise Architecture: Issues, Ingibitors, and Incentives


July/August & September/October 1999

Packages Don't Let You Off The Hook

By John A. Zachman


January/February & March/April 1999

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


November/December 1998

"Yes Virginia, There IS an Enterprise Architecture"


July/August 1998

Enterprise Architecture:  Looking Back and Looking Ahead


January/February 1998

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

 

 

 about . . .

 JOHN A. ZACHMAN

 

John A. Zachman is the originator of the “Framework for Enterprise Architecture” (The Zachman Framework™) which has received broad acceptance around the world as an integrative framework, an ontology for descriptive representations for Enterprises. Mr. Zachman is not only known for this work on Enterprise Architecture, but is also known for his early contributions to IBM’s Information Strategy methodology (Business Systems Planning) as well as to their Executive team planning techniques (Intensive Planning).

Mr. Zachman retired from IBM in 1990, having served them for 26 years. He is Chief Executive Officer of his own education and consulting business, Zachman International®.

Mr. Zachman serves on the Executive Council for Information Management and Technology (ECIMT) of the United States Government Accountability Office (GAO) and on the Advisory Board of the Data Administration Management Association International (DAMA-I) from whom he was awarded the 2002 Lifetime Achievement Award. He was awarded the 2009 Enterprise Architecture Professional Lifetime Achievement Award from the Center for Advancement of the Enterprise Architecture Profession as well as the 2004 Oakland University, Applied Technology in Business (ATIB), Award for IS Excellence and Innovation.  In August 2011,  he was awarded the Gen. Colin Powell Public Sector Image Award by the Armed Services Alliance Program.

Mr. Zachman has been focusing on Enterprise Architecture since 1970 and has written extensively on the subject. He has facilitated innumerable executive team planning sessions. He travels nationally and internationally, teaching and consulting, and is a popular conference speaker, known for his motivating messages on Enterprise Architecture issues. He has spoken to many thousands of enterprise managers and information professionals on every continent.

In addition to his professional activities, Mr. Zachman serves on the Elder Council of the Church on the Way (First Foursquare Church of Van Nuys, California), the Board of Directors of Living Way Ministries, a radio and television ministry of the Church on the Way, the President’s Cabinet of the King’s College University, the Board of Directors of the Los Angeles Citywide Children’s Christian Choir, the Board of Directors of Heavenworks, an international ministry to the French-speaking world and on the Board of Directors of Native Hope International, a Los Angeles-based ministry to the Native American people.

Prior to joining IBM, Mr. Zachman served as a line officer in the United States Navy and is a retired Commander in the U. S. Naval Reserve. He chaired a panel on "Planning, Development and Maintenance Tools and Methods Integration"  for the U. S. National Institute of Standards and Technology. He holds a degree in Chemistry from Northwestern University, has taught at Tufts University, has served on the Board of Councilors for the School of Library and Information Management at the University of Southern California, as a Special Advisor to the School of Library and Information Managementat Emporia State University, on the Advisory Council to the School of Library and Information Managementat Dominican University and on the Advisory Board for the Data Resource Management Programat the University of Washington. He has been a Fellow for the College of Business Administration of the University of North Texas and currently is listed in Cambridge Who’s Who.

 

 

 

[ Home ] [ Staff ] [ About BRC Publications ] [ Editorial Feedback ] [ About BRCommunity ]
[ Contributor's Guidelines ] [ Privacy Policy ]