whereto from zachman - the open · pdf file1 whereto from zachman enterprise architecture...

1

WHERETO FROM ZACHMANEnterprise Architecture Practitioners’ conference

October 2003

VISH VISWANATHAN

Managing Consultant- CCANDC Solutions

Regional Partner- The Open Group (Australia/ New Zealand /ASEAN)

Vice Chair-Asia/Pacific Architecture Forum

e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/SetsProc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Architecture

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

John A. Zachman, Zachman International (810) 231-0531

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGYENTERPRISE

e.g. Business Plan

TM

2

Global Needs for EA

ü Rationalisation

ü Integration

ü Better ROI

ü Alignment to business

Etc ,, Etc

Plus Regional Needs for EA

(as dictated by the tyranny of distance)

ü Heavy reliance on remote overseas vendors for products

ü Combination of US, European and Japanese standards

ü Package dependency

ü Several local home-made innovations

SIGNIFICANCE OF EA TO AUSTRALASIA

3

CIO champions EAAs the solution

Appoints Enterprise ArchitectRequires EA to be developed ASAP

Enterprise Architect looks for help

ROI Pressures

On CIO

ØConsultants

ØWeb based information

Ø Seminars

CURRENT STATE OF PLAY OF EA IN AUSTRALASIA

4

Employ first tier consultants(outsource)

Take over implementation(in source)

Investigation Phase Reports Initial Implementation Full Implementation

Get training & hand holding Assistance from specialist consultants

Select Framework, methodology & tools Assistance from specialist consultants

Use in-house resources

QA Review /audit By specialist consultants

TYPICAL EA PROJECT START UP PROCESS

In-house investigation

OR

e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

A

G

BC

F

P

Practical Enterprise Architecture implementation using a hybrid approach

ZACHMAN FRAMEWORK

E

DH

TOGAF8

A WELL KNOWN HIGH LEVEL FRAMEWORK……….

ØZACHMAN FRAMEWORK ------ STRENGTHS

• De-facto standard for classifying the Enterprise architectural artifacts

• Logical structure for analysing and presenting artifacts from a management perspective

• Draws parallels from the well understood Engineering or Construction paradigm

• Widely recognised as a management tool for checking architectural completeness and maturity

ØZACHMAN FRAMEWORK ------ WEAKNESSES

• No processes for implementation

• Difficult to implement in total

• No ready examples or checklists

• Extent of coverage of the cells unclear

A DISCIPLINED PROCESS……………

ØTOGAF – STRENGTHS

• Focuses on implementation cycle (ADM) and processes

• Rich in the technical architecture area

• Resources base provide a lot of reference materials

Ø TOGAF – WEAKNESSES

• Top three layers need to be strengthened

• No standard templates across all domains(for Building blocks etc)

• No reusable (ready made) artifacts

and AN EASY –TO-USE TOOL ………….

Ø SYSTEM ARCHITECT—STRENGTHS

• Supports both TOGAF and Zachman

• Can be extended to facilitate a hybrid approach

• Has a variety of built-in models

• Easy to learn

Ø SYSTEM ARCHITECT—WEAKNESSES

•Support for each framework as is

•No EA processes or start up “Shell”

• No end-to-end EA Examples

e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Architectural vision

Simplified mapping of EA layers onto Zachman Framework

e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Business Architecture


e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

IS (Data) Architecture


e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

IS (Application) Architecture


e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

Technology Architecture


e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

COVERAGE OF ALL FOUR ARCHITECTURE LAYERS

e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

A

G

BC

F

P

1. TOGAF Phase P plus: Creation of the “EA shell” & initial management agreement

2. Snapshot study of current “architecture” & Concerns analysis to highlight the need for EA

3. Customise ADM / Customise Zachman cell checklists

4. Training of Architects and other key stake holders

5. TOGAF Phase A

6. TOGAF phases B/C/D: Complete Version 1 of Reference Models

7. Identify ,Create and store Building Blocks ( ABB/SBB)

8. Refer to relevant Zachman cells for completeness at the end of each phase

9. TOGAF ADM Phases E/F: Provide touch points to existing processes

10. Complete processes for phases G/H

Steps towards Enterprise Architecture

PRACTICAL EA DEVELOPMENT PROCESS

ZACHMAN FRAMEWORK

ENTERPRISE SPECIFIC ARCHITECTURE

TOGAFRESOURCES-FoundationArchitecture-TRM /SIB-Checklists-Templates

-Case studiesEtc.,

E

DH

A BRIEF LOOK AT THE ENHANCED TOOL

Ø Index

ØTOGAF & Zachman linking

ØChecklists

ØSample models

Ø Flexible objects

ENHANCEMENTS UNDERWAY/ONGOING …………...

Ø Improve and add to standard templates / checklists

Ø ABB / SBB format standardisation

Ø End-to-end case studies

Ø Link into System Architect TOGAF support modules

Ø Continued support for The Open Group’s IIRM

Ø Link into other Architecture Forum deliverables ( Eg . MDA compliant ADM)

18

WHERETO FROM ZACHMANEnterprise Architecture Practitioners’ conference

October 2003

For further details please contact:

VISH VISWANATHAN

[email protected] [email protected]

Tel No: 61 2 94109855 or 61 412293336

e.g. DATA


Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor









e.g. Semantic Model








e.g. System Design


e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF CONTEXT)

Sub-Contractor

FUNCTIONING




e.g. Rule Design















e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

TM

whereto from zachman - the open · pdf file1 whereto from zachman enterprise architecture...

Documents