Zachman Framework

The Zachman EA Framework ( colloquially Zachman Framework) is a 1987 conceived by John Zachman domain- neutral regulatory framework for the development of information systems. As a conceptual framework of the Group Management Framework is a framework available exceeding 50 on the market.

It forms a guide that provides suggestions on what aspects should be taken into account perspectives from which to successfully set up the IT architecture of an enterprise. Using this modeling both the documentation and the planning of such a project can be supported, if you want to, for example, traced, have drawn the technical reactions according to the choices.


In contrast to similar frameworks that often include process models, the Zachman Framework does not point to continuous process sequence, but focuses on the roles involved, which it assigns to each to be viewed objects according to different perspectives. In this case, no concrete methods are given, but only the pre-structured point of view to be tracked. The Zachman Framework provides thus is an instrument to be considered in system planning and development of all relevant aspects from all perspectives to be considered comprehensively.


  • Planner
  • Owner
  • Designer
  • Builder
  • Programmer
  • User


  • What (data)
  • How (function)
  • Where ( network)
  • Who ( people)
  • When ( time)
  • Why ( motivation)

Zachman Framework


The perspectives of "what", "how" and "when" found in many methods into account. The observation of the cross-linking using the perspective of "where" and the reference to the reasons why certain actions are required to be "why" addressed in the perspective of what is novel.

The Zachman Framework is a generic concept with a low degree of formalization, which does not include specific guidelines to be used on methods, but each to reach objectives showing. This is revealed by the consideration of different roles involved a large part of the phases of the software development process. However, the accompanying project management is hidden there. Since there is a scheme of order in this concept, the potential degree of automation affected is relatively low. Through his methodological openness, however, allows the inclusion of new methods so that it can maintain its relevance in the long run.