Zachman framework sample model

Explore The Enterprise Architecture Toolkit

John Zachman's framework for information systems architecture - first proposed in 1987 and later extended
in 1992 - is a widely used approach for developing and/or documenting an enterprise-wide information
systems architecture. Zachman based his framework on practices in traditional architecture and engineering.
This resulted in an approach which on the vertical axis provides multiple perspectives of the overall
architecture and on the horizontal axis a classification of the various artifacts of the architecture.

The purpose of the framework is to provide a basic structure which supports the organization, access,
integration, interpretation, development, management, and changing of a set of architectural representations
of the organizations information systems. Such objects or descriptions of architectural representations are
usually referred to as Artifacts.

The framework, then, can contain global plans as well as technical details, lists and charts as well as natural language statements. Any appropriate approach, standard, role, method, technique, or tool may be placed
in it. In fact, the framework can be viewed as a tool to organize any form of meta-data for the enterprise.

	DATA What	FUNCTION How	NETWORK Where	PEOPLE Who	TIME When	MOTIVATION Why
SCOPE Contextual	Enterprise Data Dictionary	Functional Hierarchy Breakdown	Locations List	Organization & Stakeholder View list	Business Event	Strategic Plan Goals, CSF etc
ENTERPRISE MODEL Conceptual	Summary Information Model	Activities within Function & Costing	Linkage of Location to Motivation	Organization & Stakeholder Hierarchy	Business Event Hierarchy	Business & Operational Plan
SYSTEM MODEL Logical	Logical Data Model	Process Model or Detailed Activities	Location data/process links	Activity for Org view & Org Data Authority	Logical Process Model or Sequence diagram	Rules & Sys Requirements w/ Logical links
TECHNICAL MODEL Physical	Physical Database Design	Object model/ Components or structured*2	Network Design*3	Security design for App/DB/Net*4	Job Scheduler*5 & App Modules for Events	Links to DB/App that implements
DETAILS Imple- mented	SQL DDL/ DBMS Tables*1	Source Code/ Executable Applications*2	Network Cabling & protocols*3	Net/App/ DBMS   Security	Scheduled Batch & Online apps    (Function Details)	App modules & DB tables, Data and Function Details
	*Other tool(s) recommended.  See notes below.   1) Your selected DBMS is the appropriate tool for this cell.  2) Your application development environment (including language, Java, C++ VB, etc) fits here.             A roundtrip Object Modeling tool may also be appropriate. 3) A tool that helps to map detailed network traffic and network node design would be appropriate here. 4) Main security mechanism (Application, Database or Network) is selected and the tool used to manage             security will be highly dependent on the method selected for your particular environment. 5)  Job Scheduling management software recommended to manage batch/offline process scheduling