Zachman Classification, Implementation & Methodology · 1 Zachman Classification, Implementation & Methodology Stan Locke B.Com, M.B.A. Zachman Framework Associates [email protected]

1

ZachmanZachmanClassification,Classification,

Implementation Implementation & Methodology& Methodology

Stan Locke B.Com, M.B.A.

Zachman Framework Associates

[email protected]

© Copyright 1998-2005 Zachman Framework Associates Slide 2

As Managing Director of Metadata Systems Software (Canada) Inc., Stan Locke B.Com, MBA, Queen’s provides leadership and consulting support to leading corporations and large government organisations in the areas of Enterprise Architecture – including Business semantic, transformation, organization, timing and motivation components. His specialised database and repository capabilities in model management integration, software engineering and project implementation have helped numerous large organisations with the unique know-how to strategically implement Enterprise Architecture. He brings his years of learning experience to the Framework Implementation. In April 2004, he was appointed Managing Director and Chief Operating Officer of Zachman Framework Associates.

Stan was a systems designer in a University Personnel setting for seven years; occupied a number of management roles of data groups for a high growth public telephone company for seven years; gave guidance as the Principal Consultant to the practice of business modelling for an early entry enterprise architecture consulting firm for 4 years; and has directed a system software company for 12 years. His professional interest has long been in the metasystems, metadata and metaframeworks arena. As a long time associate of John Zachman they served for a number of years on the International Repository Application Development board together. His work over the past dozen years has been directed at applied research of framework compliant techniques and framework teaching standards and tools, particularly with not-for-profit organizations and governments who share models.

Stan has been active in church affairs over this same time period, serving in many Presbyterian congregations as Finance chairman, Board chairman, Stewardship chair, and Elder for much of that time. His particular interest in the past few years has been in the worldwide Alpha program, initiated by Holy Trinity Church (Anglican), Brompton (London) England. He and his wife are active members of Kingsway-Lambton United Church in Toronto. He also assists with his wife’s musical interests particularly in support of the 350 voice strong Toronto Children’s Chorus and The Oriana, a auditioned women’s choir, and both sons and daughters love of music.

2


Zachman Overview Topics

1. Classification– the way we describe the business

2. Implementation– the way we deploy business solutions

3. Methodology – the way we accomplish the solution


Is all about breaking things …into component pieces

3


Proposition Theory

Thing is related to Thing

– Where thing has existence– And thing has characteristics of interest– And thing is a count noun allowing the

abstraction to a set or class


Scope

Business

System

Technology

Component

WhyWhenWhat How Where Who

Operations

4


Columnar Taxonomy

Thing– Entity– Transform– Location– Role– Cycle– end

Association– Relationship– Input– Connection– Work– Moment– Means


Point in Time, Length of time

5


Point in Time, Length of time


Where is Quality Job 1 ?

6


Where is counting accuracy critical ?


Where is intellectual capital paramount ?

7


The constant cry “Where is it ?”


Capable of answering Why

8


Industry ExamplesName major companies or industries1. require very high integrity in enumerating things

• Financial Institutions, Statisticians, Actuaries2. that are concerned about the process quality

• Manufacturers3. who are constantly adjusting their logistics routes

• Transportation, Retailers4. that have high intellectual capital outputs

• Consulting, Educational Institutions5. who are driven by something at a moment in time

• Emergency Services, Orchestras6. who are driven by their goals alone

• The church


Some ‘magic’ which allows us to cope with:

– Significantly increasing complexity • more with less resources• different outcomes from the present

– Rapidly decreasing time to market• Or from “idea to implementation”

– Constant evolution in implementation• Technology “Silver Bullets”• Best Practices & Better Methods (Methodology)

Classification Topics

9


Helping Words

Linguists tell us that helping words

• assist in understanding the context of communication• clarify our ability to understand what something does not mean


outcomes

boundaries

concepts

logic

constructs

instructions

operations

Lists

semanticmodels

instances

schematicmodels

blueprintmodels

listings

identify

define

realize

represent

specify

configure

scope

business

enterprise

system

technology

component

10


Helping Words Constructs

identify scope boundariesVisionaries’ lists

define business conceptsExecutive Leaders’ semantic models

realize enterprise operationsWorkers’ instances

logicsystemrepresentArchitects’ schematic models

constructstechnologyspecifyEngineers’ blueprint models

instructionscomponentconfigureImplementers’ listings



Operations

Scope

Business

System

Technology

Component

11


Ontology

Each class has a unique set of enterprise knowledge No two classifications overlapEach Classification can be namedThe classification content is described by a unique thing-relationship-thing model.


Framework Metamodel

Specifies the operating characteristics between the classifications in a framework– What is produced (deliverable)– How, or Why, When, Where and Who

and the meta constructs of the four frameworks.

12


So could we have missed some important history ?

The Zachman framework is deceivingly simpleThere are four metaframeworks in the Zachman setImplementation is different than ClassificationMethodology is the value choices we make on the architecture primitives


Classification Constructs ~ the cell

Cell Width ( enterprise vs less than enterprise)

Cell Depth ( planning vs implementation detail)

Cell Slivers– Horizontal ( planning & control )

– Vertical ( implementation )

13


Unique Deliverable

Each cell is a discrete deliverableEach cell is a discrete deliverable

InterrogativePerspective

AudiencePerspective


In how much detail ?

Cell width and depthCell width and depthHow much of the Enterprise is covered ?

• Horizontal Sliver or a Vertical Sliver

High Level ofDetail Model

Or

ExcruciatingDetail Models

sliver

sliver

14


sliver

sliver

sliver

“good for enterprise implementation”

Adding detail is a function

of a cell not a column

• Horizontal Sliver or a Vertical Sliver• Planning Sliver or an Implementation Sliver

sliver“good for enterprise planning”High Level ofDetail Model

Or

ExcruciatingDetail Models

Cell width and depthCell width and depth

In how much detail ?

How much of the Enterprise is covered ?


InterrogativePerspective

AudiencePerspective

Each cell is a unique primitiveEach cell is a unique primitive

Primitive Perspective

15


Is all about breaking things …into component pieces


Zachman Topics

1. Classification– the way we describe the business



16


Zachman Topics

however …


Integration is about assemblies

Holistic nature of BusinessIntegrating the answers Integrating component detailsDiagonal integration implicationsMaking composites for practical use

17


Three kinds of Integration


Three kinds of Composites

18


The Hexagonal Model

What

Data

How

Process

Where

Location

Network

Who

People

Work

When

Time

Sequence

Why

Motivation

What

Data


Interconnecting the cells creates integrated viewpoint

Process

Data

Location

People

Time

VV

V

Motivation

19


Interconnecting the cells creates integrated viewpoint

Process

Data

Location

People

Time

VV

V

Motivation


Integration ~ Ensures Quality

15 Matrices (if no relationship direction)• Completeness• Leveling• Pattern Emergence

30 Matrices (if relationships have direction)• Completeness• Leveling• Pattern Emergence

20


Column Integrations0

c6-c4 c6-c5 c6-c6c6 c6-c1 c6-c2 c6-c3

c4-c4 c4-c5 c4-c6

c5 c5-c1 c5-c2 c5-c3 c5-c4 c5-c5 c5-c6

c4 c4-c1 c4-c2 c4-c3

c2-c4 c2-c5 c2-c6

c3 c3-c1 c3-c2 c3-c3 c3-c4 c3-c5 c3-c6

c2 c2-c1 c2-c2 c2-c3

c1-c4 c1-c5 c1-c6

c1 c2 c3 c4 c5 c6

c1 c1-c1 c1-c2 c1-c3


Zachman Topics

however …

21


Primitives and Composites No Diagonal moves on Framework

The place of objects in Architecture

What’s next in the object world


The Diagonal Move

Operations

Scope

Business

System

Technology

Component


22


The Diagonal Issue

Operations

Scope

Business

System

Technology

Component


Is No Architecture


WhatHowWhereWhoWhenWhyWhat

Scope

Business

System

Technology

Component





23



Objects are integrations

Assemblies involve more than 1 cellOften traverse over the rowsAre implementation mechanisms

24


Classic (Business) Object Theory

Object

Structure

Instance ofEntity:set ofclass of

Transform

Behaviour


Business Objects are Composites

Object

Structure

Instance ofEntity:

set ofclass of

Transform

SendReceive

Messages

ExposeInterface Triggers

InterpretRules

Behaviour

TemplateClass

25


Business Object to Questions

Object

Structure

Instance of

Entity:set ofclass of

Transform

SendReceive

Messages

ExposeInterface Triggers

InterpretRules

Behaviour

TemplateClass

what

how

where who when

why


Is all about assembly of things …from component pieces

26


MethodologySome ‘magic’ which allows us to cope with:

– Significantly increasing complexity • more with less resources• different outcomes from the present

– Rapidly decreasing time to market • Or from “idea to implementation”

– Constant evolution in implementation• Technology “Silver Bullets”• Best Practices & Better Methods (Methodology)


Repeatable way to implement …

27


Methodology in summaryDetermines which questions will be answeredDetermines which audience perspectives will be addressedThat is: what classifications will be doneWhat width of the classification will be done What depth of the classification will be done Which components will be integratedWhich components will be transformedThis sets the standards that will apply


TOGAF is a methodology

Formulated on the Zachman Classification Which cells to cover with which implementation deliverablesWhich order, with whom and under what governance Which transformations to ensure between the audience layers

28


Framework is neutral to methodology

Choosing which frameworksWhich cellsWhat depthWhich sliversWhat is to be integratedWhat is to be transformed

Are Decisions outside the classification


Random Selection

29


Natural Integration


First the bad news

– There is more than one Zachman framework

30


ClassificationClassification

ProfessionProfession

Enterprise Enterprise

Product Product The ZachmanMetaframeworks




Enterprise Enterprise Enterprise Enterprise Enterprise

[as-is]

Enterprise

[as-is]

Enterprise

[to-be]

Enterprise

[to-be]

Enterprise

[could-be]

Enterprise

[could-be]

Enterprise

[should-be]

Enterprise

[should-be]

Enterprise

[might-be]

Enterprise

[might-be]Enterprise Enterprise

The ZachmanFramework Setdepth

As Is Should BeTo Be Will BeMight Be Could Be

Product Product

31




Enterprise Enterprise Enterprise Enterprise Enterprise

[as-is]

Enterprise

[as-is]

Enterprise

[to-be]

Enterprise

[to-be]

Enterprise

[could-be]

Enterprise

[could-be]

Enterprise

[should-be]

Enterprise

[should-be]

Enterprise

[might-be]

Enterprise

[might-be]Enterprise Enterprise

The ZachmanFramework Setdepth

As Is Should BeTo Be Will BeMight Be Could Be

Product Product




EnterpriseEnterprise

The ZachmanFramework SetInheritance

Product Product

32


Now the good news

– There are only four frameworks

– They all obey the underlying normative structure


Zachman Overview Topics1. Classification

– the way we describe the business



4. Elaboration– the way we accomplish the solution

Zachman Classification, Implementation & Methodology · 1 Zachman Classification, Implementation & Methodology Stan Locke B.Com, M.B.A. Zachman Framework Associates [email protected]

Documents