Subscribe to the FREE Business Rules Journal Newletter





The Zachman Framework Evolution
Part 1

by John P. Zachman

The Zachman Framework™ has evolved over time and has a rich history in the space we call "Enterprise Architecture."  While the fundamental concepts have not changed at all, refinements to its graphical representation, in addition to more precise language, embody The Framework's history and what you see today.  Here is a brief trip down its historical evolution....


Figure 1.  The Zachman Framework™ — 1984.

Never published until now, Figure 1 shows the original Zachman Framework:  Information Systems Architecture — A Framework, by John A. Zachman.  Created in June of 1984, this was a crude representation that John created himself of what would later be referred to as The Zachman Framework™.

Notice it has only 3 Columns.  While all 6 Columns did actually exist, John was nervous that people might not be able to fully appreciate (or be willing to accept) his thoughts, particularly since Enterprise Architecture hadn't been born yet and this was a Framework for INFORMATION SYSTEMS architecture.

Also notice Column 1, Row 2 contains a Chen Diagram, Row 3 contains a Bachman Diagram, and Row 4 has an IMS Root-Segment Diagram.  Also, Column 2, Rows 2 & 3 contain IDEF0 notation.  These notations were the best available at the time as John was formulating what Architecture was relative to Enterprises.  John would later realize that these notations (or models of The Framework) were representations of "Composite" constructs in the Enterprise Architecture.  This would become a FUNDAMENTAL distinction that would revolutionize how people thought about Enterprise Architecture — "Primitive" models versus "Composite" models — and be the FOUNDATION for how John would later define the concepts of dealing with complexity and change.  More on this later...


Figure 2.  The Zachman Framework™ — 1984 (v2).

The Figure 2 representation of The Framework was created from John's original drawings by IBM graphics support.  John used this graphic until he retired from IBM in 1990.

Notice the original title:  Information Systems Architecture — A Framework.  Also, notice the "diamond" in the Column 1, Row 2 Chen notation model.  John would later remove this because this representation is a composite view of that particular cell.  The "diamond" is a representation of a process (a verb) connecting two entities (nouns), which violates the later-developed fundamental Framework rule that cells can only contain primitive constructs, not composites (i.e., no processes can be in that particular cell:  Column 1, Row 2).  This is a perfect example of what we would call a composite model today, not a primitive model.

Also notice the IDEF0 notations in Column 2, Rows 2 & 3.  These are also a composite view because of the vertical arrows.  These are not pure, primitive models.


Figure 3.  The Zachman Framework™ — 1987.

Figure 3 is the original, and first published, Framework for Information Systems Architecture, appearing in the 1987 IBM Systems Journal.[1]  Notice that only the first 3 Columns made it, in spite of all 6 actually existing.  Most people had no concept of thinking about Architecture being for the ENTIRE Enterprise or "Enterprise Architecture" as John would later coin.  Since The Framework was originally published for I/S, there was no precedent set for thoughts about Responsibility (Column 4), Timing (Column 5), or Motivation (Column 6).  Notice the composite model in Column 1, Row 2 as defined above, in addition to some of the other notation changes.


Figure 4.  The Zachman Framework™ — 1992.

Still called A Framework for Information Systems Architecture in the 1992 IBM Systems Journal article[2] Enterprise Architecture was starting to gain a small amount of recognition based on John's ideas that strategy and information systems needed to be "engineered" for the ENTIRE Enterprise, not just "manufactured" by the I/S department.  However, this Framework so revolutionized the I/S concept that existed at this time, that people began to refer to this Framework, and the previous Frameworks, as The Zachman Framework.

The Figure 4 artist's rendition is fairly close to John's original graphic.  Note that John added the words 'Owner', 'Designer', and 'Builder' to Rows 2, 3, and 4 for clarification.  John Sowa (co-author of the 1992 article) said, "Oh, we can call Row 1 'Planner', and Row 5 'Sub-Contractor'."

Also note that the cells of Columns 4, 5, & 6 are each populated with the same model.  The I/S community, at that time, did not have much experience, or notion, for the models in those Columns, so these are John's personal models that he used in each of those Rows.


Figure 5.  The Zachman Framework™ — 1993.

It was at this point that John decided to officially call his Framework:  Enterprise Architecture – A Framework.  He had recently formed his consulting and education company, Zachman International®, nearly two years earlier and had been using the term 'Enterprise Architecture' for some time.  He felt convinced that people would be more willing to accept his ideas about "Enterprise" Architecture as opposed to "Information Systems" Architecture.

The Figure 5 version is still a minor carry-over from the 1987 article as it only has 3 columns.  John used only the first three columns when teaching about The Framework because of the dominant I/S perspective that still existed at the time.  He was afraid to overtly discuss the "other three Columns" because people, particularly the I/S people, might become discouraged and give up!

Notice that this version is the first to use the adjectives 'Contextual', 'Conceptual', 'Logical', 'Physical', and 'Out-of Context' when defining the Rows.  John used these terms in an attempt to convey that each Row was a representation of a TRANSFORMATION when moving down each Column — NOT another layer of detail (more on this later).

Column 2, Row 3 "Business Process Model" came from the 1990 book, Re-engineering the Corporation, which popularized the words 'Business Process'.

There were some minor problems with this Framework which were actually rooted back from its inception.  The first (noted earlier) is the use of the Chen Diagram in Column 1, Row 2.  This is still a composite model — the diamond indicates a process (or verb) hard-bound in the Inventory (thing) model, making that model totally inflexible.  The Column 2, Rows 2 & 3 IDEF0 notation are also composite models — the vertical arrows represent controls and mechanisms on these process models, making them a composite as well (hard-biding multiple meta-entities into one model).  Also notice the Column 1, Row 4 model (IMS Root-Segment) is a hierarchy, which is a problem because nothing can be normalized in a hierarchy because you end up with things showing up in more than one place.  Each of these models was changed in later versions to better support the "Primitive" model concept John had conceived.

In addition, observe the map in Column 3, Row 1.  The map changed from a US map (1992 version above) to a World map because of John's first seminar in Australia, truly making Zachman International® international.  This representation, however, is actually quite an inaccurate model, because the map is an instantiation, which belongs in Row 6 (see more detail about this in the discussion of the 2001 version).


Figure 6.  The Zachman Framework™ — 1993 (The Other Three Columns).

Several of John's friends from the Business Rules community persistently pressed him to talk about "The Other Three Columns" because it is Column 6 from which the "Business Rules" are derived.  This 'version', while not widely distributed, was part of John's lecture series on "What is Enterprise Architecture" as evidenced by the title of this version:  Enterprise Architecture — The Other Three Columns.


Figure 7.  The Zachman Framework™ — 2001.

During this time, Enterprise Architecture was really gaining ground due to John's thoughts about the subject.  Fully recognized as The Zachman Framework, the Figure 7 version was very widely distributed and had many of the refinements from the previous 10 years of research.

In particular, notice the model in Column 1, Row 2 is no longer an early Chen Diagram because Peter Chen had actually removed the diamond from his notation just before the release of this Framework graphic.  Removal of the 'diamond', or process (verb), made this model "primitive."  Also, the controls and mechanisms (vertical arrows which were integral to the IDEF0 Process Modeling notation) were removed from the Column 2, Rows 2 & 3 models.  It does, however, still contain the IMS Root-Segment notation in Column 1, Row 4.

The colors of the models in each Row are significant here.  John used the color models as a teaching tool to re-enforce the idea that each Row is different and is the result of a transformation, NOT a decomposition of detail (more on this later).  It is difficult to graphically depict this idea with black lines on a white background in order to form the cells of the matrix, but John was attempting to depict this concept with the use of color.  He used spectrum colors:  Red, Orange, Yellow, Green, Blue, and Orange.  Most people ask why he didn't round out the spectrum with Purple in Row 6.  He answers that, "Row 6 is Orange to match Row 2; because whatever the Owners have in mind (Row 2 — Business Concepts — Orange) should be what is actually instantiated in the Enterprise (Row 6 — THE ENTERPRISE — Orange)."

As you can also see, while Row 6 existed, the Functioning Enterprise wasn't fully acknowledged as part of The Framework yet, but John was re-thinking this idea heavily.  Without Row 6, people had the tendency to embed instances into their architecture, making it VERY inflexible.  The instance (when embedded in the higher Rows) will bind things together.  Proper nouns belong in Row 6 and generally mean you have an instance.  Common nouns imply you have a set, which can be counted.  Abstractions belong in the first five Rows — instances belong in Row 6 (i.e., Stockholm cannot be in Row 1 because it is an instance of capital citiesStockholm belongs in Row 6 because it is the instantiation of the scoping context of capital cities which would be in Row 1).  Technically, Architecture is always ABSTRACTIONS (Rows 1-5), whereas the RESULT of Architecture — THE ENTERPRISE (instances) — are always Row 6.

Continuing with this idea is one more small flaw that continued to show up until the 2004 version.  The picture (or model) of the World map in Column 3, Row 1 (Network) is grossly inaccurate.  John liked it for its aesthetic value, the artistic contribution; however, the inaccuracy is in the fact that the World map is a representation of a physical place, which is actually an instantiation (Row 6) of the scope (Row 1).  The Row 1 models are scoping lists and nothing more, not instances.  If anything, the picture (or model) of the World map belongs in Row 6.  While this was done as more of a tribute to the original Framework (see above), John would later point out that this would lead to potential confusion in the Framework fundamental concept and was subsequently changed in a later version.

In addition, to John's regret, he named Column 1 "Data," which he feels inaccurately continued to classify The Zachman Framework™ as a Framework for Information Systems, despite having "Enterprise Architecture" titled across the top.  In fact, most of the terminology in this Framework is I/S related, which further perpetuated the misconception that the Framework, and Enterprise Architecture for that matter, were an I/T issue.

One other significant problem with this Framework is its rampant use of adjectives.  Adjectives are not countable sets; they are always subject to interpretation and therefore make the concepts here dramatically less precise.

Barring these deficiencies, however, this Framework was instantly and widely accepted as a representation for Enterprise Architecture and proliferated its way across the globe very quickly.


Figure 8.  The Zachman Framework™ — 2002.   

The Figure 8 graphic was developed by Intervista-Institute in Canada, whom we still work with extensively.  After obtaining copyright clearance from John, and with his development help, this was a HUGE upgrade in aesthetics and graphic design.  While this representation of The Framework was the most attractive aesthetically, it still contained Information Systems terminology, lots of adjectives, a deemphasized Row 6, the IDEF0 notation in Column 2, Row 2, and the IMS Root-Segment notation in Column 1, Row 4.

One significant improvement in this version, however, is the use of the black-to-white gradient, vertical banding, which works its way down the columns.  This gradient significantly emphasized that there is more going on with The Framework than just a matrix.  This de-emphasized people's misperception that working your way down the columns is merely an increase in level of detail.  This is still a misconception about The Zachman Framework™ today, and the black-to-white gradient was an attempt to correct this fundamental misinterpretation.  The movement down each column has nothing to do with level of detail; it has to do with transformation.

This Framework illustration helped emphasize the transformation concept of the Columns.


Figure 9.  The Zachman Framework™ — 2003.   

Developed at roughly the same time period, the Figure 9 graphic was a very widely-distributed, and very recognizable, representation of The Zachman Framework™ because of its development during the time when ZIFA existed.  Some of the ZIFA partners, other than John, were unsatisfied with the Intervista version (Figure 8), which was a more aesthetically-pleasing version and showed the Transformation black-to-white gradient banding down the Columns.  The objection was related to the predominant Intervista advertising, despite its having the ZIFA logo on the right. 

Therefore, they commissioned the Figure 9 version, which only had reference to ZIFA, but surprisingly reverted to earlier notation problems.  This Framework does have some significant shortcomings.  It still contains I/S terminology, not the current Enterprise terminology, in addition to an extensive use of less-precise adjectives (which proliferates ambiguity in interpretation) and a minimized Row 6, even worse than the Intervista version of Figure 8.

Most surprisingly, however, notice that the IDEF0 notation made its way back into Column 2, Rows 2 & 3, which violated the fundamental rule of The Framework about no cell containing composite constructs.  The vertical arrows make those processes dependent on some control or mechanism, which destroys the primitive (or 'Periodic Table') idea of The Framework.  John had made this correction in his 2001 version (Figure 7), but it unfortunately came back in this Figure 9 version.

In addition, the colors of Rows 2 and 3 became inverted and purple was added to Row 5.  Because of the predominate use of color in each Row, this Framework illustration emphasizes the Integration concept of the Rows.


Figure 10.  The Zachman Framework™ — 2003 (v2).   

Developed in 2003, the Figure 10 graphic was a minor variation of the graphic from 2002 (Figure 8), also developed by Intervista Institute in Canada.  This representation was most certainly the most pleasing aesthetically up to that time.

The changes were minor from the Figure 8 version — it still contained Information Systems terminology, adjectives, and a de-emphasized Row 6.  The most significant improvement in this version is the use of the gradient color banding across the Rows and down the Columns.  This gradient color banding between each cell best illustrates the concepts of Integration (across the Rows) and Transformations (down the Columns) above all previous versions of The Framework because each cell stands alone, which creates space between them and the ability to depict that more is going on.

Also, the IDEF0 notation was changed in Column 2, Row 2.  In addition, the model in Column 5, Row 2 was changed to a "circular" icon, which did not convey the idea of "event-cycle-event" very well and was subsequently changed.  However, the IMS Root-Segment notation was still used in Column 1, Row 4 and the Bachman diagram in Column 1, Row 3.

The brilliance of this Framework illustration was that it emphasized both the integration concepts of the Rows and transformation concepts of the Columns.


Figure 11.  The Zachman Framework™ — 2004.   

Much to John's chagrin, the Figure 11 version of The Zachman Framework , developed in 2004, was titled The Zachman Framework2™ .  John never liked the "squared" in the title, but because of the internal structure of Zachman International at the time, he was forced to accept the change.  The superscript "2" was added to indicate that this was the "2nd version" of John's most recognizable, 6-column representation — the 2001 version (Figure 7).

Aside from this, however, this version did mark some very significant changes that John was pleased about.  Most notably is the migration away from I/S terminology to more generic Business terminology, which had helped make tremendous strides in getting the Framework in front of General Management as opposed to just hanging on the walls of I/T shops.  Also, the use of noun-modified nouns (instead of adjective-modified nouns) makes this version much more precise.

Other improvements include the removal of the World map model in Column 3, Row 1 (see 2001 version — Figure 7), more representative "Primitive" model notation in the Columns, and no Instantiations other than in Row 6.

One very significant problem that persists with this version, however, is that the Figure 11 graphic representation uses only white lines on a light blue background in order to form the matrix, making it impossible to convey the idea of Integration and Transformation.  As referred to earlier, this was a problem with many of the previous representations as well (sans the Intervista renditions presented earlier). 

While this Framework had many improvements, it did nothing to convey the idea of TRANSFORMATION when moving from the top to the bottom of each column.  Intervista had attempted this with moderate success by their use of gradients (2002 & 2003 versions, Figures 8 & 10); however, this 2004 version continued to facilitate many Enterprise Architects (EAs) to wrongly assume that each Row of the Framework merely represented an increase in the level of detail, or 'waterfall', as the Architects move their way down each Row vertically.

By the same token, this problem persists horizontally as well.  There is NO indication that INTEGRATION exists between the Columns.  This was also a serious problem because many EAs were building Composite models and hard-binding multiple concepts together in their Architecture, rather than separating independent variables and then integrating the variables across each Row.

Because of the limitations of using single lines to create the cells of a matrix, much confusion continued to be perpetuated by this version (stemming back to The Framework's inception).  These FUNDAMENTAL concepts that The Zachman Framework has always embodied:  the models of the Enterprise INTEGRATE horizontally, and they TRANSFORM vertically are difficult to depict graphically.  Due to the fact that these concepts were not graphically evident in this version, it was left up to the Zachman Certified™ certification[3] instructors to convey this point.  These foundational issues were subsequently addressed in the next version.

This review of the historical evolution of The Zachman Framework concludes next month with a look at the 2011 Zachman Framework Version 3.0.

This article can also be viewed on John's website — presented here, with permission.


[1]  John A. Zachman, "A Framework for Information Systems Architecture," IBM Systems Journal, Volume 26, Number 3, page 276 (1987) — at  return to article

[2]  John A. Zachman and John Sowa, "A Framework for Information Systems Architecture," IBM Systems Journal, Volume 31, Number 3, page 590 (1992) — at  return to article

[3]  For information on Zachman Certified™ certification visit  return to article

standard citation for this article:
John P. Zachman, "The Zachman Framework Evolution (Part 1)," Business Rules Journal, Vol. 16, No. 5 (May 2015), URL:  

January 2017
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 P. Zachman is the CEO of Zachman International®, Inc., an organization dedicated to the research and advancement of the state of the art in Enterprise Architecture principally based on the Framework for Enterprise Architecture - The Zachman Framework. As son of Zachman Framework originator, John A. Zachman, John has worked closely with his father in the management of Zachman International for nearly a decade. In addition to the operation of Zachman International and the FEAC® Institute (FEAC), John is the President of the Zachman Institute, a non-profit organization devoted to leveraging Zachman International's vast network of professionals and resources to offer services to small businesses and non-profit organizations as they prepare for and experience growth. John can be contacted at




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