• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
John Zachman's: Foundations for Enterprise Architecture
 

John Zachman's: Foundations for Enterprise Architecture

on

  • 980 views

 

Statistics

Views

Total Views
980
Views on SlideShare
980
Embed Views
0

Actions

Likes
0
Downloads
27
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    John Zachman's: Foundations for Enterprise Architecture John Zachman's: Foundations for Enterprise Architecture Document Transcript

    • A two-day briefing for business and IT executives John Zachman’s: Foundations for Enterprise Architecture John Zachman is the internationally renowned originator of “The framework for Enterprise Architecture” which has been adopted as part of the US Federal Enterprise Architecture Framework Standard. You will learn the what, how, where, who and why of Enterprise Architecture and take away valuable techniques to motivate and lead others in your organisation’s move to planned enterprise change. Key features Perth 25-26 August 2008 • Why Enterprise Architecture is the issue of the century Canberra 28-29 August 2008 • Essentials of launching an Enterprise Architecture program Auckland 4-5 September 2008 • Version two of the Zachman Framework • Hear it from the acknowledged world leader in and originator of Enterprise Architecture • From $1600 per person, you can’t afford to miss this once-only public briefing
    • Foundations for Enterprise Architecture Two Day Seminar 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. Seminar Contents There are ten major components of the seminar: i. Environmental Challenges Facing the Modern Enterprise ii. Introduction to Enterprise Architecture iii. Architecture versus Implementations iv. The System IS the Enterprise v. Architecture Work vi. Meta Frameworks vii. Classification Illustrations viii. Reducing Time-to-Market ix. Federated Architecture x. Conclusions and Recommendations “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. “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. “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. “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. “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. “Meta Frameworks” 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.
    • “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. “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. “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. “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. 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 I. Global Environment • Escalating complexity • Escalating Rate of Change II. Introduction to Enterprise Architecture • The Zachman Enterprise Framework2 • Enterprise Knowledgebase III. Architecture Versus Implementation • Primitive Models • Composite Models IV. The System IS the Enterprise V. Architecture Work • Three Possible Compromises • Architecture is Cheaper and Faster than Implementation VI. Meta Frameworks VII. Classification Illustrations • Classification by Framework • Classification by Row • Classification by Column VIII. Reducing Time-To-Market IX. Federated Architecture X. Conclusions • A New Destination • Zachman Propositions • Closing Thoughts
    • BTELL brings you the internationally renowned Intended Audience originator of “the framework for Enterprise The briefing is designed for enterprise professionals of every Architecture” exclusively for this public briefing. discipline including non-information disciplines as well as information disciplines. Although it is addressing technology If there is one must-see seminar in Enterprise issues, it is not a “technical” seminar. It addresses the subjects Architecture, this is it. that both enterprise professionals and information professionals must understand to operate effectively in collaboration in the What makes this briefing unique? Information Age environment. There are many courses and seminars available from consultants and analysts representing themselves as Enterprise Architecture JOHN ZACHMAN experts. Although the ideas about Enterprise Architecture have been acknowledged for many years, there still remains a lack of John A. Zachman is presently Chairman of the Board of common understanding as to what exactly constitutes “Enterprise Zachman Framework Associates. Architecture.” The recent re-launch of the Zachman Framework John serves on the Executive Council for Information as Zachman Enterprise Framework2 ™ marked the establishment of Management and Technology (ECIMT) of the United States the definition for Enterprise Architecture that is consistent with John Government Accountability Office (GAO). He is a Fellow Zachman’s original proposition that the concept of Enterprise for the College of Business Administration of the University Architecture goes far beyond the present information systems of North Texas. He serves on the Advisory Board for the (or, information technology) paradigm. Data Resource Management Program at the University of Why Enterprise Architecture and why now? Washington and on the Advisory Board of the Data Administration Management Association International In the current environment of uncertainy Enterprise Architecture (DAMA-I) from whom he was awarded the 2002 Lifetime is more critical than ever. Enterprise Architecture is fundamental Achievement Award. He was awarded the 2004 Oakland for enabling an enterprise to assimilate internal changes in University, Applied Technology in Business (ATIB), Award response to the external dynamics and uncertainties of for IS Excellence and Innovation. the information age environment. It not only constitutes a baseline for managing change, but also provides the mechanism by which Mr. Zachman has been focusing on Enterprise Architecture the reality of the operating enterprise and its systems can be since 1970 and has written extensively on the subject. He aligned with management intentions. is the author of the book, “The Zachman Framework for Enterprise Architecture: A Primer on Enterprise Engineering What you will take away: and Manufacturing.” He has facilitated innumerable executive team planning sessions. He travels nationally • A definition (description) of what Enterprise Architecture and internationally, teaching and consulting. is and what it is not • Techniques to demonstrate the value of Enterprise Unbeatable value at Architecture across the organisation $AU2000.00 per person + GST. • A “language” (that is, a Framework) for improving Groups 2-4 at$1800 + GST. enterprise communications about architecture issues Groups 5+ at $1600 + GST. • An understanding of what various Architecture Register today to guarantee your place! “frameworks” are and what they can be used for To register contact: • Alternatives for doing Architecture work iteratively Paul Kemp +612 9387 3344 and incrementally pkemp@btell.com www.btell.com • Clear differentiation of engineering enterprises and Tailored sponsorship opportunities available. building systems Contact Paul Kemp.
    • A TWO-DAY BRIEFING FOR BUSINESS AND IT EXECUTIVES John Zachman’s Foundations for Enterprise Architecture 25 August – 5 September 2008 TO REGISTER PLEASE COMPLETE THIS FORM AND FAX TO +612 9387 8399 FOR ASSISTANCE WITH REGISTRATIONS CALL: 612 9387 3344 VISIT: WWW.BTELL.COM EMAIL: INQUIRIES@BTELL.COM Organisation Details Pricing Organisation Address Single delegate $2000 Contact name Email address Group 2-4 $1800 Phone Group 5+ $1600 Attendee Details Attendee 1 Early bird (prior to 1 July 2008) $1800 Job title Email All prices exclude GST Attendee 2 Total: $AUD ___ ___ ___ ___ + 10% GST Job title Email Payment Method Attendee 3 Credit Card Job title Name Email Number Expiry Attendee 4 Signature Job title AMEX M/Card VISA Diners Email Please Invoice Attendee 5 Name Job title Email Email Cheque Made payable to BTELL Venue Mailto: PO Box 39 Randwick NSW 2031 Australia Perth 25-26 August 2008 Bank Transfer Canberra 28-29 August 2008 National Australia Bank, 255 George St Sydney NSW 2000 Auckland 4-5 September 2008 BSB: 082-057 Account: 48018-3247 All BTELL registrations are subject to terms and conditions. For more information please visit www.btell.com. Cancellations are permitted less a 20% administration fee where notice is received prior to 15 August 2008. Substitutions can be made after this.