Z100 MasterClass: Framework Introduction Print E-mail

A One-Day Course by John A. Zachman

Purpose

Enterprise Architecture is fundamental for enabling an enterprise to assimilate internal changes in response to the external dynamics and uncertainties of the information age environment. It not only constitutes a baseline for managing change, but also provides the mechanism by which the reality of the enterprise and its systems can be aligned with management intentions.
Note: This is a VERY ambitious agenda. Therefore, the topics covered are dependent upon the time available and the interest of the specific audience in attendance.  We recommend that you take the Z105 Framework Tutorial after completing this seminar to gather the more in depth specifics of your enthusiam generated by John.
Course Objectives
The objective of this two-day course is to build an understanding of the concepts of Enterprise Architecture and develop a sense of urgency for implementing those concepts in a modern enterprise.

Course Contents

There are ten ideas included in this exciting, evangelistic overview by John A. Zachman himself.

  1. Environmental Challenges Facing the Modern Enterprise
  2. Introduction to Enterprise Architecture
  3. Architecture versus Implementations
  4. The System IS the Enterprise
  5. Architecture Work
  6. MetaFrameworks
  7. Classification Illustrations
  8. Reducing Time-to-Market
  9. Federated Architecture
  10. Conclusions and Recommendation

Environmental Challenges Facing the Modern Enterprise

"Environmental Challenges" develops the conditions that currently are driving the modern enterprise to address the issues of Enterprise Architecture. It develops the challenges that literally demand a revolution in concepts as the tools of the Industrial Age begin to limit our effectiveness for addressing the complexities and rate of change of the 21st Century Enterprise.
  • Characteristic of the Information Age
    • "Future Shock" – The Rate of Change
    • "The Third Wave" – The Structure of Change
    • "Powershift" – The Culture of Change
  • Complexity and change
Top

 

Introduction to Enterprise Architecture

"Introduction to Enterprise Architecture" develops the Zachman Enterprise Framework2™ as a basis for defining what architecture is for Enterprises. (We know what "architecture" is for buildings, for airplanes, for automobiles, etc. What is it for Enterprises?) Out of the context of The Framework, it is easy to observe the physics surrounding Enterprises, that is, the "laws of nature" that are operating and affecting the Enterprise operation. Further, it is easy to observe why the approaches of the past, the Industrial Age, are breaking down in the face of the Information Age, and why knowledge of the classic "short term/long term trade-off" is fundamental to survival in the foreseeable future. This course component also includes the development of the metamodel of The Framework which would constitute the model of the Knowledgebase for the Enterprise.
  • Enterprise Architecture – The Definition
  • Architecture is Architecture is Architecture
  • Ontology versus Methodology
  • The Framework is a Schema
  • The Framework Metamodel
  • The Enterprise Knowledgebase
Top

 

Architecture versus Implementations

"Architecture versus Implementation" differentiates the classic IS/IT approach of building and running systems (short-term) to the Enterprise Architecture approach for engineering the Enterprise (long-term). To produce an Enterprise that is flexible, integrated, aligned, interoperable, reusable, etc. is far different from build and running systems. Single-variable "Primitive" models are required for engineering the Enterprise whereas multi-variable "Composite" models are required for manufacturing, that is, implementing systems. If no Primitive models are being produced, the Enterprise is not being engineered and therefore it is not going to be flexible, integrated, aligned, interoperable, reusable, etc. because these are engineering-derived characteristics.
  • Primitive Models are for Engineering
  • Composite Models are for Manufacturing
  • Architecture versus Implementation
  • The Three Dimensional Enterprise View
Top

The System IS the Enterprise

"The System IS the Enterprise" develops the observation that we have been replacing the people of the Enterprise with systems for the last 50 or more years. That is, the systems are now the Enterprise and therefore, I/S has effectively been manufacturing the Enterprise all of this time before the Enterprise was ever engineered. There is little wonder that the Enterprise is not flexible, not integrated, not aligned, not reusable, not interoperable, etc., etc. It was never engineered. Enterprise Architecture is the discipline that marks the transition from the Industrial Age to the Information Age.
  • Manual Systems and Automated Systems
  • Blue Collar Systems and White Collar Systems
  • Business Systems and Technology Systems
Top

 

Architecture Work

"Architecture Work" addresses the three potential compromises that can be made in partitioning the work of architecture such that it can be accomplished "iteratively and incrementally" over some long period of time. The question is, how do you partition the architecture work so that it can be done producing results in the short term but maintaining Enterprise integrity in the long term. Some things might be compromised in the short term in the interest of producing results whereas other things may be critical for maintaining integrity in the long term.
  • Explicit Models versus Implicit Models
  • Enterprise-wide Models versus less than Enterprise-wide Models
  • High level of detail Models versus Excruciating Level of Detail Models
  • The End State Vision
  • I/S Imperative: Build, Store, Manage, Change Models
  • Enterprise Architecture – Iteratively and Incrementally
Top

 

MetaFrameworks

"MetaFrameworks" develops the four "knowledge domains" that are potentially present in every Enterprise, that is, there are three and potentially four Frameworks of descriptive representations in every Enterprise, the Product Framework™, the Enterprise Framework™, the Profession Framework™ (formerly named the I/S Framework) and the Normative (or Zachman™) Framework™. These Frameworks are related in a meta structure which is important in the longer term because of the significant leverage to be realized in managing complexity and extreme rates of change.
  • The Industrial Age Product Framework™
  • The Enterprise Framework™
  • The Profession (of engineering and manufacturing Enterprises) Framework™
  • The Zachman (Classification or Normative) Framework™
  • The "Meta" Framework Relationships – Recursive Employment of the Same Framework
  • The "Total" Picture
Top

Classification Illustrations

"Classification Illustrations" shows how to classify the various Enterprise Concepts of the Enterprise into the correct Framework, into the correct Column within a Framework (specifically, the Enterprise Framework™) and into the correct Row within the Framework (specifically, the Enterprise Framework™). This is the key to creating the single variable "Primitive" models that constitute the "raw material" for doing the Enterprise Engineering work.
  • Classification by Framework
  • Classification by Perspective (i.e. Row)
  • Classification by Abstraction (i.e. by column)
  • Making the Enterprise Lean and Mean
Top

 

Reducing Time-to-Market

"Reducing Time-To-Market" shows that there are eight possibilities for reducing the time it takes from the moment an order for a new Enterprise is placed until some implementation results are produced. The principle option is to create the implementation by assembling the composite artifacts from the components of the Primitive models that have been created and stored in the "repository." This would in effect be the employment of the concept of "mass customization" to the creation of the Enterprise. Assuming the primitive models are created and retained in inventory (in a database) new versions of the Enterprise could be created on demand.
  • Eight Possibilities for Reducing Time to Market
  • Make to Order Strategy – Applications
  • Provide from Stock Strategy – Packages
  • Assemble to Order Strategy – Mass Customization of the Enterprise
Top

 

Federated Architecture

"Federated Architecture" shows how to use the Zachman Enterprise Framework2™ as an analytical tool to think through the complexities of the modern enterprise in which there are multiple business units with varying degrees of commonalities as well as "meta" relationships between the Product, the Enterprise and the Profession domains. Some things must be common to all business units (federal) and some things must be left unique to any one business unit (provincial). This trade-of can only be made in the context of the single variable, Primitive models.
  • Inter-Enterprise Integration
  • The "Sameness" Template
  • Friendly Advice
  • Federated Architecture Equals Interoperability
Top

 

Conclusions and Recommendations

"Conclusions" postulates a "new destination" that is dictated by the characteristics of the Information Age and that far surpasses the classical Industrial Age Enterprise. Also, the Zachman™ Propositions are summarized and some concluding thoughts are advanced to urge the adoption of Enterprise Architecture, specifically the Primitive Models as characterized in the Zachman Enterprise Framework2™.
  • The New Destination
  • Zachman™ Propositions
  • Framework Resources
Top

 

Intended Audience

This course is designed for enterprise professionals of every discipline including non-information disciplines as well as information disciplines. Although the course is addressing technology issues, it is not a "technical" seminar. It addresses the subjects that both enterprise professionals and information professionals must understand to operate effectively in collaboration in the Information Age environment.

Further, the course is appropriate for both management and operational (technical) professionals. For management it clarifies the issues for decision purposes and enables more meaningful dialog with and among the technology community. For operations, it establishes the context for developing improved approaches and implementation strategies.

 

What the Participant will take away:

  • A sense of urgency for aggressively pursuing Enterprise Architecture
  • A definition of Enterprise Architecture
  • A "language" (that is, a Framework) for improving enterprise communications about architecture issues
  • An understanding of basic Enterprise physics
  • A differentiation between building and running systems and Enterprise Architecture
  • An understanding of Enterprise engineering design objectives
  • An understanding of the cultural changes implied by Enterprise Engineering
  • An approach for implementing iteratively and incrementally
  • A list of resources to facilitate architectural work

 

Agenda

  • Global Environment
    • Escalating complexity
    • Escalating Rate of Change
  • Introduction to Enterprise Architecture
    • The Zachman Enterprise Framework2™
    • Enterprise Knowledgebase
  • Architecture Versus Implementation
    • Primitive Models
    • Composite Models
  • The System IS the Enterprise
  • Architecture Work
    • Three Possible Compromises
    • Architecture is Cheaper and Faster than Implementation
  • Meta Frameworks
  • Classification Illustrations
    • Classification by Framework
    • Classification by Row
    • Classification by Column
  • Reducing Time-To-Market
  • Federated Architecture
  • Conclusions
    • A New Destination
    • Zachman™ Propositions
    • Closing Thoughts

 

Note: This is a VERY ambitious agenda. Therefore, the topics covered are dependent upon the Time available and the interest of the specific audience in attendance.  We recommend that you take the Z105 Framework Tutorial after completing this seminar to gather the more in depth specifics of your enthusiam generated by John.

 

Back