Editing Zachman Framework (section)

=== Flexibility in level of detail ===

One of the strengths of the Zachman Framework is that it explicitly shows a comprehensive set of [[view model|views]] that can be addressed by enterprise architecture.<ref name="GASLSJ03"/> Some feel that following this model completely can lead to too much emphasis on documentation, as artifacts would be needed for every one of the thirty cells in the framework.  Zachman, however, indicates that only the facts needed to solve the problem under analysis need be populated.

John Zachman clearly states in his documentation, presentations, and seminars that, as framework, there is flexibility in what depth and breadth of detail is required for each cell of the matrix based upon the importance to a given organization. An automaker whose business goals may necessitate an inventory and process-driven focus, could find it beneficial to focus their documentation efforts on What and How columns. By contrast, a travel agent company, whose business is more concerned with people and event-timing, could find it beneficial to focus their documentation efforts on Who,  When, and Where columns. However, there is no escaping the Why column's importance as it provides the business drivers for all the other columns.