“Location” was previously used for the “Where” Column, which caused some people to put in instances (e.g., “Sacramento”). So, Column 3 now uses “Distribution Networks.”
The “Who” Column now uses “Responsibility Assignments” to emphasize that it covers roles rather than the individuals.
The “When” Column previously used the terms “Cycle” and “Event” for artifact models, which were often misunderstood. The Column 5 primitive models now use “Interval (for “Cycle”) and “Moment” (for “Event”). For example, Row 2 now features “Business Interval” and “Business Moment”.
The Model Names used to be shown to the left, and the Audience Perspectives on the right. These have been swapped.
As part of the ongoing work to improve communication about the Framework, the “Audience” labels now use “Perspective”.
Also, use of “Planner” was removed because it conveyed the wrong idea about the nature of the audience for the top Rows. Row 1 now uses “Executive Perspective” and Row 2 uses “Business Management Perspective”.
Zachman seriously considered moving the Classification Names (What, How, Where, Who, When, Why) to the bottom of the graphic and moving the Enterprise Names to the top. At the last minute he decided not to because a practitioner shared a compelling story with him about how W-H-W-W-W-W inspired an important discovery in his work.
To communicate that going down the rows does not indicate decomposition, crooked arrows are now shown between each of the Rows. These crooked arrows emphasize that moving from one Row to the next represents a transform. (Credit was given to Ron for this suggestion.)
Note: The transforms relationship can be one-to-many, but that’s something you need to manage very carefully.
For horizontal alignment (across a Row), make sure your tool supports the primitives and then helps you manage the compositions.
For vertical alignment (up/down a Column), you cannot just ‘push the button’ (do the transform), then forget about managing the vertical relationships. Change is inevitable, so vertical alignment must be maintained.
[Keri and I both think that was a good decision.]
“Because I came from an ‘information’ community I had initially used words like ‘data’ in column 1. Big mistake! People thought the Framework was about IT! The first thing people saw was the word ‘data’.
[The Framework has always been about business engineering – that was clear even from the earliest talks I heard Zachman give in the late 1980s and early 1990s. In truth, I would have never guessed it would still be an issue 20+ years later.]
The Framework is well-known for its depiction of the engineering primitives (the columns, which are normalized – one thing in one place). The engineering models, however, don’t do anything in and of themselves. The enterprise also needs its manufacturing models – the composites. So these new faint gray lines have been added as a reminder that the composite models also exist and they are also important.
Note: These new faint gray lines are meant as ‘for example’ connections. In this sense they are like the examples shown in the Framework for the primitives in the columns.
[The row 2 / row 6 alignment is consistent with the business-engineering theme that Zachman so ably promotes.]