Some of the common myths about the framework are: Is the framework for Enterprise or IT or both; colors are random; there is no Integration across columns; transformation vs. decomposition; number of rows can change, columns are arbitrary, perspectives are random; no rules to separate primitive vs. composites; architecture constructs vs. manufacturing constructs; methodology vs. ontology; taxonomy vs. ontology; checklist vs. periodic table; row 1 & row 2 vs. row 6; etc

1. Architect Corner
WHAT, WHY & HOW OF DOING ENTERPRISE & IT ARCHITECTURE
BLOGS ICMG HOME OUTSOURCING CONSULTING TRAINING & EVENTS RESOURCES ARCHITECTURE STORE POSTS
Awards 2013 Survey & Trends Webinars Architect Pavilion Enter keywords...
LATEST POPULAR COMMENTS TAGS
Top 21 Zachman Framework Myths
– Busted Biggest myth – “Enterprise
Architecture is a discipline
FEBRUARY 9, 2012 BY SUNILDUTTJHA 12 COMMENTS aimed at creating models”.
JANUARY 23, 2013
8 Votes
Last year, we had a discussion in iCMG VTU partners iCMG to set up
LinkedIn group (over 20,000 members) which world’s largest center of
ignited the passion and invited over 1000 excellence in
comments. The title of the thread was “What’s Enterprise Architecture
killing the Enterprise Architecture? – quote JANUARY 6, 2013
extracted from one of John Zachman’s article.”
As the time has gone by, the number of people The most prestigious John
who misrepresent and misinterpret the Zachman Award for Enterprise
Zachman framework has gone up significantly. Architecture in 2013 –
nominations are invited
The problem is that the framework is easily
DECEMBER 5, 2012
available for download and it has English labels which are legible.
You will agree that downloading recipe from a cookery portal doesn’t make one a master chef. Six questions participants
asked during the recent
As the time has gone by, number of misrepresentations has only gone up – thanks to the growing webinar on managing Enterprise
interest in the discipline of “Enterprise Architecture.” Disorders (videos)
NOVEMBER 28, 2012
Some of the common myths about the framework are: Is the framework for Enterprise or IT or both;
colors are random; there is no Integration across columns; transformation vs. decomposition; number This one’s for YOU- iCMG
of rows can change, columns are arbitrary, perspectives are random; no rules to separate primitive vs. Architecture Excellence
composites; architecture constructs vs. manufacturing constructs; methodology vs. ontology; Awards 2013
NOVEMBER 21, 2012
taxonomy vs. ontology; checklist vs. periodic table; row 1 & row 2 vs. row 6; etc.
Myths Facts
1. Column 1 is labelled “Data,” which Not correct. It’s not the framework for Information
classify Zachman Framework™ as Systems. Categories
a Framework for Information
Systems. In fact, in 2004, the term “data” was removed from
the framework. Please note that in 2011 version of Select Category
the framework graphics – The enterprise name for
“What” is “Inventory Sets”. Follow
Twitter Updates
2. “Data” is the most important aspect Not correct. Order of columns has nothing do to Follow “Architect
of the enterprise as it’s in the first with their relative importance in the context of Corner” Who is responsible for technology in your
column. “Motivation” is “least” “Enterprise”. Get every new postThe CEO or CIO - take the poll
company? delivered
important as it’s in column six to your Inbox.
bit.ly/CEOasCIOpoll 1 day ago
The order of column just reflect the order in which 6
communication interrogative i.e. what, how, where, Join 937 other followers
RT @andrewjstevens: I missed the Logies.
who, when, why are being used. “What or earlier
Enter your email addresstimes I believe in fate. 3 days ago
There are
data” column being the first column is just reflecting
the order in which people (around the world) have CEOs myth - It would take too long and cost
Sign me up
been using these 6 interrogative. too much to do enterprise architecture
#entarch http://t.co/w5mkwhCtEB 3 days ago
Powered by WordPress.com
3. The Framework, and Enterprise No.The reality is that the Zachman Framework is CEO myth - It would take too long and cost too
Architecture for that matter, are an Ontology for Enterprise Architecture.
much to do enterprise architecture #entarch
IT issue
Unfortunately, most people who come from IT http://t.co/4j7o3FhNaq 3 days ago
today are thinking of building and running systems
and not about engineering and manufacturing RT @MrVirtualCIO: Vivek Kundra was right.
enterprises. Feds can't make Enterprise Architecture work
and I am not sure if I should keep banging my

2. 4. People’s misperception that working The movement down each column has nothing to
head... 4 days ago
your way down the columns is do with level of detail; it has to do with
merely an increase in level of detail. transformation @MrVirtualCIO 4 days ago
The idea of Enterprise Architecture is to
5. Each cell containing composite Oops! Wrong again. Each cell consists of primitive
describe the fundamental structure of an
constructs. constructs, not composites.
Enterprise bit.ly/YKb5mO 5 days ago
6. The Framework is just a matrix The brilliance of this Framework is in the concepts
of Integration (across the Rows) and Follow @sunilduttjha
Transformations (down the Columns).
Often, constructs within the “Enterprises” are in
Last date for submission of nomination
for Awards 2013
“composites” form created by integrating the
elements across the cells.This helps in effective Last date for
diagnosis, better predictability and enhanced nomination
traceability for change and complexity April 19th, 2013
management. Once you will use it, you will
8
understand what I am talking about.
7. The Framework is a checklist. It’s similar to saying “Periodic Table” is a checklist.
You can use the framework as a checklist, but it’s days to go.
oversimplifying the fact.
We know that one can use the periodic table for
Email Subscription
creating complex compounds with predictive
characteristics or behaviour. Similarly, one should
Enter your email address to subscribe to this blog
use the framework for creating complex enterprise
and receive notifications of new posts by email.
constructs (composites) to meet some defined
need. Join 937 other followers
8. There is NO indication that Blame the previously available framework graphics.
INTEGRATION exists between the Sign me up!
Columns.
In fact, the new framework graphics very clearly
represents the “Integration lines” linking elements
Archives
between the columns. This clearly establishes that
integration exists between the Columns as well.
Select Month
Architects can use the primitive cells of the
Framework (Periodic Table) to build the composite
implementations (Chemical Engineering) to
produce predictable, repeatable results (a Blogroll
science). The integrations and transformations are
like “mortar between the bricks” (the bonds WordPress.com
between the chemical elements).
WordPress.org
9. Framework is enterprise taxonomy It’s understatement.
Framework is “enterprise ontology” and not just
taxonomy i.e. complete set of things that makes the
enterprise similar to “Periodic Table.”
All the compounds (chemical) which exist on planet
earth can be formulated by mixing the primitive
elements (of periodic table). Similarly, all the
enterprise composites are possible by combining
the primitive cells in Zachman framework.
Every human being is different, yet they follow a
common body structure. Similarly, every enterprise
is different but they follow a common structure i.e.
Zachman framework.
Unfortunately, Human body is so complex that
medical people still doesn’t have a good ontology.
10. The Zachman Framework in There are many “Frameworks” in EA and there is
competition with other Enterprise significant confusion about what the word
Frameworks “Framework” actually means. The fact is that ALL
Enterprise Architecture “Frameworks” in the
industry is a methodology or derivative of the
Zachman Framework.

3. The Zachman Framework for Enterprise
Architecture is “Enterprise Ontology”.
11. Most people who misrepresent Grossly misunderstood.
Zachman Framework as a
“waterfall,” think that each Row This is not the case at all. The models of each Row
represents another level of detail, TRANSFORM- they do not get more detailed. Level
i.e. the highest level of detail at the of detail is represented in the height of each cell,
top of The Framework (Row 1) and i.e. a high level of detail at the top of each cell and
the most excruciating level of detail an excruciating level of detail at the bottom of each
at the bottom of The Framework cell
(Row 5)
12. The Framework’s fundamental The Framework’s fundamental concept is
concept is decomposition, down “transformation”, not “decomposition”, in the
each column reification process down each column.
An idea (or Scope-Row 1) has to go through 6 well-
known phases in order to reach reality (Operations-
Row 6) such that the reality retains an alignment
with the initial idea as it was conceived and
designed.
13. Column 3 (Network Nodes- 2004 The fact is that the fundamental concept of Column
Version).Enterprise Architects often 3 deals with distribution of resources as opposed to
thought of this as point-to-point node addresses on a network.
nodes and were not building their
models correctly.
14. The six rows are arbitrary i.e. John No it’s not arbitrary. John uses the 2000 year old
has just picked up 6 different concept of reification i.e. how to transform an
perspective (in six rows) and there abstract idea to reality.Reification consist of 6
are more perspective which can be phases of transformation i.e.- Identification
added – that is, more rows can be (mapped to Row 1)- Definition (mapped to Row 2)-
created. Representation (mapped to Row 3)- Specification
(mapped to Row 4)- Configuration (mapped to Row
5) and - Instantiation (mapped to Row 6)The
models in each row get transformed to the next
Row below, and the Row 6 wraps up the 6th phase
of reification
15. “Who”: Column 4 – Organization This is not so.
Groups.
This Column is all about “responsibility”. In
As soon as the Enterprise Architects Zachman Framework v3.0 (2011), meta-model has
saw this label, they incorrectly been changed to form the title “Responsibility
assumed it as: Organization Chart? Assignments” for Column 4.
16. Zachman Framework is a The Zachman Framework™ is the “Enterprise
“methodology” Ontology” and not “methodology”. It’s a
classification theory about the scientific nature of
any Enterprise and the kinds of “Things” (entities)
that have an existence in that Enterprise.
Therefore, The Zachman Framework for Enterprise
Architecture is the ENTERPRISE ONTOLOGY. The
way the “Periodic Table” is ontology for
“Chemistry”; the “Zachman” framework is the
ontology for “Enterprise”.
Once you know the “Enterprise Ontology”, you can
create /use a methodology of your choice. Using a
methodology without ontology is a “trial and error”
practise.
17. Creating the “composite model” is No, “composites” are manufacturing constructs.

4. creating the “architecture” Primitives (single variable models) are Architecture
constructs.
Unfortunately, people are building composite
models by hard-binding multiple concepts together
in their “model” and calling it “Architecture”.
18. Six columns in Zachman Wrong, the columns are not arbitrary.
Framework are arbitrary, I can add
few more columns on need basis The 6 columns represent the universally accepted 6
communications interrogative i.e. what, how,
where, who, when and why.
19. The colours are just a decorative The colours of the models in each Row are
piece; I can use any colour. I don’t significant. Here, John used the colour models as
see any logic or significance. 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.
John used spectrum colours: Red, Orange, Yellow,
Green, Blue and Orange.
Why he didn’t round out the spectrum with Purple in
Row 6.?
The reason is 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).”
20. Enterprise Architecture is only Row1 Enterprise Architecture is comprised of Rows 1-5.
& Row 2. The instantiated Enterprise is represented in Row 6
21. Zachman Framework is complex. Ignorance.
The framework is not complex, but the enterprise
IS. The Periodic Table has to be complete in order
to allow the chemists to be able to analyse, and
create compounds with accuracy and repeated
predictability. Similarly, Enterprise framework has
to be complete to ensure that enterprise architects
are able to analyse, and create enterprise
constructs quickly and in a repeatable fashion to
achieve the results.
The problem lies in basic understanding and
application of the framework. A chemist never
creates “infinite” number of compounds just
because it’s theoretically possible using the
Periodic Table. They create the compound based
on the need.
Similarly, doctor never creates 1000 x-rays or
scans of all parts of the body of a patient and stores
it in the repository.
On the similar lines, the idea is not to create infinite
number of composites based out of the Zachman
framework, rather create those which are needed to
address some problem of the Enterprise.
Of course, 5 myths that one can find around the corner:
1. Enterprise Architecture is only row1 & row 2
2. Zachman Framework is a “methodology”
3. TheFramework’s fundamental concept of decomposition, down each column. Each Row
represents another level of detail

5. 4. There is NO indication that INTEGRATION exists between the Columns.
5. Each cell containing composite constructs.
What’s your experience? Share your favorite myth about Zachman Framework. Feel free to share if
you have come across any other misperceptions? Would be happy to hear from you.
Note:For the insight on the evolution of framework since 1984, please visit article by John P
Zachman
Related articles
Zachman Framework graphics v3.0 – what’s NEW? (blogs.icmgworld.com)
John Zachman quotes on inherent complexity in running and managing enterprises
(blogs.icmgworld.com)
Share this:
Like this: ★Like
Be the first to like this.
Enterprise Architecture, Trends, Uncategorized
Column, common myths, decomposition, Enterprise Architecture, enterprise name, featured,
Framework, Information Systems, Information technology, John Zachman, misrepresentations, Ontology,
relative importance, Zachman Framework
About sunilduttjha
Chief Architect & CEO - iCMG Sunil is practicing architect & CEO of iCMG,
who is influencing enterprise decisions worth $250mn annually. In the last 11
years, he is instrumental in growing iCMG as leading full service Enterprise &
IT Architecture Firm, providing architectural services to a wide variety of clients
(over 20 domains) across 23 countries. Being Aerospace Engineer by qualification (IIT
Kharagpur), he enjoys working with complex systems such as Air Traffic Control System,
Water Leakage Management System (City/country), Shipping & Surveillance systems, of
course that also include few million or few billion dollar enterprises etc. As a practising
architect, he is often engaged in adoption of Enterprise & IT Architecture driven Transformation
and Planning, IT Landscape Rationalization for business success. He is an excellent
technologist, great visionary and one of the true thought leaders and practitioners of Eterprise
& IT Architecture. One can't miss his penchant for problem solving, reasoning based on
"engineering" principles and hands-on startegy-to-operation excellence in tacking issues (
small or big) related to asset consolidation, integration, efficiency, innovation,reusability and
governance etc. You will agree that you need a seasoned hand to approach for a project that is
enterprise-wide in scope. As an architecture coach/mentor, he has taught enterprise & software
architecture classes to over 5,000 professionals (cumulative) in 16 countries. The contribution
of Sunil Dutt Jha to an evolving discipline of Enterprise & IT Architecture through education &
training, consulting, Annual Awards, Architect Pavilion (Architects networking site) are worth
noting.
View all posts by sunilduttjha →
Zachman Framework v3.0 – what’s NEW? Missed it Last Year? Nominate for the Architecture Awards 2012
12 Responses to “Top 21 Zachman Framework Myths – Busted”
sunilduttjha February 10, 2012 at 11:54 am Reply
0 0 Rate This
Share your favorite myth about Zachman Framework http://t.co/bYgh8tSj
Scott Lawson (@Scott_L_Lawson) February 10, 2012 at 6:53 pm Reply

6. 2 0 Rate This
I agree with your myths and they are good, but still there is nothing
specific that is explained to allow people to understand. What would be
helpful, I think is to show an example of primitives in a cell. Show how the
transformation down a column is illustrated in an actual Enterprise
example. Thanks!
sunilduttjha February 11, 2012 at 2:04 pm Reply
0 0 Rate This
Thanks Scott! for reminding “to do list”…it’s planned later this month.
Gerald Khoury February 14, 2012 at 9:54 pm Reply
1 0 Rate This
Thanks Sunilduttjha. A very useful reference that shows a good
understanding of the taxonomy.
manuel di toma May 25, 2012 at 5:00 pm Reply
0 0 Rate This
Yes, this is very good thank you!
Manuel
Peo Ekström February 7, 2013 at 2:41 pm Reply
0 0 Rate This
This is very good – I personally like the universal idea of 6 communication
interrogatives and I usually add the resulting effect on me –> which
impact/result do/did it have on myself, my stakeholders, my public etc.
Trackbacks/Pingbacks
1. John Zachman will certify only 50 professionals in next 6 months world over,
are you the chosen one? | Architect Corner - February 23, 2012
0 0 Rate This
[...] Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com) [...]
2. Diagnosis and corrections of 9 enterprise disorders using Zachman Framework
| Architect Corner - March 1, 2012
0 0 Rate This
[...] Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com) [...]
3. Deconstruct Business Process Model using Zachman Framework Principles – 5
part videos | Architect Corner - March 16, 2012
0 0 Rate This
[...] Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com) [...]
4. Unknowingly, it’s like referring a “compound” as an “element” in the Periodic
Table ;-) | Architect Corner - May 17, 2012
0 0 Rate This
[...] Framework is “enterprise ontology” and not just taxonomy (Top 21 Zachman Framework Myths –
Busted). The framework is ontology, i.e. complete set of things that makes the enterprise, similar to [...]
5. Diagnosis & Corrections of Enterprise Dis-orders using Zachman Framework: a
three part webinar series | Architect Corner - November 14, 2012
0 0 Rate This
[...] Enterprise Architecture. Zachman Framework is “enterprise ontology” and not just taxonomy (Top 21
Zachman Framework Myths – Busted). The framework is ontology, i.e. complete set of things that makes
the enterprise, similar to [...]
6. Biggest myth – “Enterprise Architecture is a discipline aimed at creating
models”. | Architect Corner - February 12, 2013
0 0 Rate This
[...] Top 21 Zachman Framework Myths – Busted (blogs.icmgworld.com) [...]

7. Leave a Reply
Enter your comment here...
February 2012 Email Subscription
M T W T F S S
Enter your email address to subscribe to this blog
1 2 3 4 5 and receive notifications of new posts by email.
6 7 8 9 10 11 12
Join 937 other followers
13 14 15 16 17 18 19
20 21 22 23 24 25 26
Sign me up!
27 28 29
« Jan Mar »
Architect Corner. Blog at WordPress.com. Theme: Headlines by WooThemes.