Zachman Framework

1. Zachman Framework Source: Enterprise Architecture, Intervista Institute www.intervista-institute.com

2. Enterprise Engineering Design Objectives • Alignment • Integration • Reusability • Flexibility

3. Alignment • Means… • The implemented systems to be aligned with the business purpose • Build Row 1 models • Build Row 2 models • Build Row 3 models • Build Row 4 models • Build Row 5 models • Ensuring the intent of each Row is successfully represented in the succeeding Row

4. Alignment • To keep the implementation (Row 6) aligned with management’s intent (Rows 1, 2) • Management’s intent (Rows 1, 2) • The Design state of the art (Row 3) • The Technology constraints (Row 4) • The Technology products (Row 5) And • The Enterprise Data (Column 1) • The Processes(Column 2) • The Distribution Network (Column 3) • The Organization (Column 4) • The Dynamics (Column 5) • The Business Strategy (Column 6) (You have to retain and maintain the models)

5. Integration • means… • No discontinuity between the various related concepts within the Enterprise • Scope integration –no discontinuity within any one kind of model across the scope • Horizontal integration—no discontinuity across the different kinds of related models from Column to Column • Vertical integration—no discontinuity between the various Rows, the Owner’s, Designer’s, and Builder’s constraints

6. Three Definitions of “Integration” Horizontal Integration (any row) Vertical Integration (any column)

7. Integration • Integration implies sharing, normalization • You have any one concept defined only one time • Any time you need some one concept, you reuse what has already been defined • Do not re-create that same concept because it will cause redundancies and potential inconsistencies, discontinuities, etc. • Integration is the Enterprise equivalent of Standard Interchangeable Parts

8. Reusability • Related to integration • If you want to engineer something to be reused, you have to know the total set of possibilities in order to engineer characteristics that will accommodate multiple uses. • The key to reuse (and Integration) is Enterprise-wide normalized models.

9. Flexibility • Means… • Things implemented such that they can be changed in minimum time with minimum disruption, at minimum cost • Similar concept: adaptability • To achieve flexibility… • Working with standard, interchangeable parts, that is, integrated architecture • Any one concept exists only one time so if you need to change it… you change it once and it is changed for every deployment. • Having an inventory of all the reusable concepts so you know where they are and that they are and could find them when you want to re-use them

10. Enterprise Division A Division B Division C

11. Enterprise Division A Division B Division C A Division? Easiest structure to conceptualize because it clearly consists of a set of business functions all integrated in support of a common business objective

12. Enterprise Division A Division B Division C The whole enterprise?

13. Enterprise Division A Division B Division C The Corporate Office?

14. Enterprise Division A Division C Division B The Intersection of the Divisions?

15. Enterprise Division A Division B Division C An Implementation, i.e. an application? If you choose a boundary less than the natural integration boundary, you will dis-integrate the Enterprise

16. Division A Division A Division B Division B Division C Division C Enterprise Division A If you choose a boundary beyond your jurisdictional control, you can no longer “declare” the models, you must “negotiate” the models. Division B Division C

17. Where to Start? • The best place to start is at Row 1… Row 1 people build Row 1 models Row 2 people build Row models Row 3 people build Row 3 models; and so on. • If you can’t get the Row 1 and Row2 people to build the Rows 1 and 2 models, the next best alternative is for Row 3 people to make assumptions about the Rows 1 and 2 models, but to make the assumptions explicit by actually building the models. • Which column to start with is a function of your value system. The column you start with, you are tending to optimize. Subsequent columns you are tending to compromise. • Zachman’s suggestion: starting with Col. 1, 3, & 6

18. Strategic Planning Generic Responsibilities

19. Strategic Planning Other Three Columns Business Planning

20. Zachman’s Architectural Principles • Ensure implementations reflect the characteristics of the business such that the reality of the implemented Enterprise is consistent with management’s requirements/expectations. • Ensure the meaning (semantics) of the data is consistent from implementation to implementation so that cross-application views are relevant and historical analysis over time is possible. • Ensure hardware/system software is compatible from node to node to sustain the capability to successfully send messages between Enterprise components.

21. Zachman’s Architectural Principles • Ensure business rules are enforced consistently from implementation to implementation to coordinate and/or change behavior within the Enterprise. • Ensure systems are defined logically, independent of technology constraints such that the implementation technology can be changed with minimum disruption and cost. • Ensure change is incorporated as a design and a management criteria such that any aspect of the Enterprise (including the systems) can be maintained relevant in a dynamic environment.