Zachman framework

From Free net encyclopedia

The Zachman Framework is a framework for Enterprise Architecture which provides a formal and highly structured way of defining an enterprise's systems architecture. It uses a grid model based around 6 basic questions (What, How, Where, Who, When, and Why) asked of 5 nominated stakeholder groups (Planner, Owner, Designer, Builder and Subcontractor) to give an holistic view of the enterprise which is being modelled.

Often used as part of a systems architecture or enterprise level technology review exercise it is popular within IT architecture departments but has little hold of either the developer or user communities. The enterprise architecture can form an input to a firm's software architecture.

The strong points are the complete coverage gained by touching each of the cells on the matrix. The weak point is that this approach generates a lot of documentation, due to its completeness, which can be difficult to digest and sometimes of questionable utility.

Originally conceived by John Zachman at IBM in the 1980s the framework is now in the public domain. The full technical name is Zachman Framework for Enterprise Architecture and Information Systems Architecture

[edit]

The table

Zachman Framework for Information System Architecture
Layer	View	Data (What)	Function (How)	Network (Where)	People (Who)	Time (When)	Motivation(Why)
1	Scope/Contextual (Planner view)	List of things important to the business	List of processes the business performs	List of locations in which the business operates	List of organizations important to the business	List of events significant to the business	List of business goals/strategies
2	Business Model/Conceptual (Owner view)	e.g., Semantic or Entity-relationship Model	e.g., Business Process Model	e.g., Business Logistics System	e.g., Work Flow Model	e.g., Master Schedule	e.g., Business Plan
3	System Model/Logical (Designer view)	e.g., Logical Data Model	e.g., Application Architecture	e.g., Distributed System Architecture	e.g., Human Interface Architecture	e.g., Processing Structure	e.g., Business Rule Model
4	Technology Model/Physical (Builder view)	e.g., Physical Data Model	e.g., System Design	e.g., Technology Architecture	e.g., Presentation Architecture	e.g., Control Structure	e.g., Rule Design
5	Detailed Representations/ out-of-context (Subcontractor view)	e.g., Data Definition	e.g., Program	e.g., Network Architecture	e.g., Security Architecture	e.g., Timing Definition	e.g., Rule Specification
6	Functioning Enterprise	e.g., Data	e.g., Function	e.g., Network	e.g., Organization	e.g., Schedule	e.g., Strategy

Each cell in the table must be aligned with the cells immediately above and below it. All the cells in each row also must be aligned with each other. However, cells will not be aligned diagonally.

[edit]