THE ZACHMAN FRAMEWORK FOR AND ENTERPRISE ARCHITECTURE KNOWLEDGE MANAGEMENT ENABLING ENTERPRISE STRATEGY What Data Function List of Processes How Where Network Who People When Time Motivation List of Goals Why List of Things List of Locations List of Organizations List of Cycles Scope Planner ENTITY = Class of Business Entities PROCESS = Class of Business Processes NODE = Class of Business Locations PEOPLE = Class of Business Organizations CYCLE = Class of Business Cycles END = Class of Business Objectives Scope Planner The Zachman Framework for Enterprise Architecture s a comprehensive classification scheme for descriptive representations (models) of an enterprise.
First conceptualized nearly two decades ago by John Zachman, it has evolved to become a universal schematic for defining and describing today’s complex enterprise systems and for managing the multiple perspectives of an organization’s information and knowledge infrastructure. e. g.
, Semantic Model e. g. , Business Process Model e.
g. , Logistics Network e. g. , Work Flow Model e. g.
, Master Schedule e. g. , Business Plan INTERVISTA INSTITUTEEXECUTIVE EDUCATION Business Model (Conceptual) Business Model (Conceptual) ENTITY = Business Entity RELATION = Business Relationship I/O = Business Resources PROCESS = Business Process NODE = Business Location LINK = Business Linkage PEOPLE = Organization Unit WORK = Work Product TIME = Business Event CYCLE = Business Cycle ENDS = Business Objective MEANS = Business Strategy Owner Owner Intervista’s Enterprise Architecture courses provide you with an in-depth understanding of the Zachman Framework and the key success factors for implementation.Over 5000 IT and Management Executives from all sectors have chosen Intervista for their professional development and strategic advancement.
To learn more about our Enterprise Strategy, Enterprise Architecture and Knowledge Management Executive Education programs call 1-800-397-9744 or visit us at: www. Intervista-Institute. com e. g.
, Logical Data Model e. g. , Application Architecture System Model (Logical) e. g.
, Distributed System Architecture e. g. , Human Interface Architecture e. g. , Processing Structure e. . , Business Rule Model System Model (Logical) TIME = System Event CYCLE = Processing Cycle ENDS = Structural Assertion MEANS = Action Assertion Designer ENTITY = Data Entity RELATION = Data Relationship I/O = User Views PROCESS = Application Function NODE = IS Function LINK = Line Characteristics PEOPLE = Role WORK = Deliverable Designer Technology Model (Physical) e.
g. , Data Design e. g. , System Design e. g. , Technology Architecture e.
g. , Presentation Architecture e. g. , Control Structure e. g. , Rule DesignTechnology Model (Physical) Builder ENTITY = Table/Segment/etc. RELATION = Key/Pointer/etc. I/O = Data Elements/Sets PROCESS = Computer Function NODE = Hardware/System Software LINK = Line Specifications PEOPLE = User WORK = Screen/Device Formats TIME = Execute CYCLE = Component Cycle ENDS = Condition MEANS = Action Builder www.
zifa. com e. g. , Data Definition e.
g. , Program e. g. , Network Architecture e.
g. , Security Architecture e. g. , Timing Definition e. g.
, Rule Specification Detailed Representations SubcontractorENTITY = Field RELATION = Address I/O = Control Block PROCESS = Language Statement NODE = Addresses LINK = Protocols PEOPLE = Identity WORK = Job TIME = Interrupt CYCLE = Machine Cycle ENDS = Sub-condition MEANS = Step Detailed Representations Subcontractor www. ZachmanInternational. com Example Example Example Example Data Function Network Organization Example Example Schedule Strategy FUNCTIONING ENTERPRISE For the Enterprise Architecture Executive Education schedule call Intervista Institute at 1-800-397-9744. www.
Intervista-Institute. com Copyright 2003, Intervista Inc. All rights reserved. Framework by permission John A. Zachman.