 |
Workshop attendance costs:
R1760 ex VAT for Open Group Members
R2145 ex VAT for Non-members. |
John Zachman
Chief Executive Officer, Zachman International
Plenary Presentation
Introduction to Case Study Examples
For many years, I have argued that engineering an Enterprise is different from building and running systems. Engineering an Enterprise requires single variable, “primitive” models, whereas building and running systems requires multiple variable, “composite” models. If you want the Enterprise to be “architected”, then the “composite” implementation (systems) models must be created from components of “primitive” engineering (architecture) models. If the “composite” implementation models are created before any “primitive” models exist, then the Enterprise will be implemented (running systems), but NOT “architected.” The problem is, for the last 60 or 70 years, those of us who come from the information community have been solely focused on building and running systems (implementations) not on engineering Enterprises (architecture). We build and use “composite” models. We don’t relate to “primitive” models because we don’t build or use “primitive” models. This presentation argues the utility and necessity of Primitive Models for Enterprise Architecture by way of introducing the Case Study Example Primitive Models.
Workshop
Managing Enterprise Complexity and Change
Enterprise Architecture tends to be a much mis-understood subject by General Management and the Information Technology community alike. Enterprise Architecture has everything to do with managing Enterprise complexity and Enterprise change and relates to information technology only in so far as information technology may be one of the choices that an Enterprise can make with regard to Enterprise operations. The Framework for Enterprise Architecture, the “Zachman Framework,” is derived from the descriptive representations that constitute architecture for any industrial object. The Framework defines the set of engineering design artifacts required for engineering an Enterprise for flexibility, integration, reusability, interoperability, alignment, etc. that is, it is the knowledgebase for creating, operating, managing the Enterprise and constitutes the baseline for managing Enterprise change.
 John Zachman
John A. Zachman is the originator of the “Framework for Enterprise Architecture” which has received broad acceptance around the world as an integrative framework, or "periodic table" of descriptive representations for Enterprises.
Mr. Zachman retired from IBM in 1990, having served them for 26 years. He is Chief Executive Officer of Zachman International, a business dedicated to research and education in the “Issue of the Century”, “Enterprise Architecture”.
Mr. Zachman serves on the Executive Council for Information Management and Technology (ECIMT) of the United States Government Accountability Office (GAO).and on the Advisory Board of the Data Administration Management Association International (DAMA-I) from whom he was awarded the 2002 Lifetime Achievement Award. He was awarded the 2009 Enterprise Architecture Professional Lifetime Achievement Award from the Center for Advancement of the Enterprise Architecture Profession as well as the 2004 Oakland University, Applied Technology in Business (ATIB), Award for IS Excellence and Innovation.
Mr. Zachman has been focusing on Enterprise Architecture since 1970 and has written extensively on the subject. He is the author of the book, “The Zachman Framework for Enterprise Architecture: A Primer on Enterprise Engineering and Manufacturing.” |
 Return to previous page
|
|
|
