by: viral rathod aman goyal 1. 1. enterprise architecture. 2. history of enterprise architecture 3....

Zachman FrameworkRow 2 : The Owner Perspective

By: Viral RathodAman Goyal

CS 6899

1

Organization1. Enterprise Architecture.

2. History of Enterprise Architecture

3. Overview of Zachman Framework

4. The Owner’s Perspective (Row 2)

5. Security in Owner’s Perspective.

6. Criticism of Zachman Framework

7. Other Framework / Approaches.

2

1. Enterprise Architecture What is Enterprise?

What is Enterprise Architecture?

Why to use an Enterprise Architecture?

What are currently available solutions?1. IBM Enterprise Architecture2. SAP – ERP3. Oracle Enterprise Manager

3

2. History of Enterprise ArchitectureDevelopment of various Enterprise Architecture:

1980-1990

• A framework for information systems architecture,' John Zachman article in IBM Systems Journal.

1990-2000

• Capgemini Integrated Architecture Framework (IAF)

• The Open Group Architecture Framework (TOGAF) 1.0

• Federal CIO Council introduces Federal Enterprise Architecture Framework (FEAF)

2000-2010

TOGAF 7.0 / 8.0 / 9.0

Zachman

DoDAF 1.0 / 2.0

FEAF (mostly complete)

4

2. History of Enterprise ArchitectureRelationships between various Enterprise Architecture:

Zackman

1987

EAP1992

FEAF1999

TEAF2000

TOGAF1995

TAFIM1994

DODAF2003

C4ISR1996

5

Adoption

Influence

3. Overview of Zachman FrameworkWhat is Zachman Framework?

Classification schema.

Tabular tool / matrix.

Provides Rational for decisions made.

Clear understanding of what is happening.

Clear understanding of why is happening.

Problem solving kit.

6

3. Overview of Zachman FrameworkWhat problems does it solve?

Any complex problem involving multiple individual components.

E.g. Flight Reservation System.

E.g. Building a rail road.

E.g. Building Empire State Building.

7

3. Overview of Zachman Framework

8

1. Enterprise ArchitectureMost basic Work Flow Diagram for Car Manufacturing.

Company

Market

Research

Cars

9

1. Enterprise Architecture

Car Manufacturing company

HR

Finance

Marketing

SalesManufacturi

ng

TestingManufacturi

ng for Testing

Regulation Check

Design

10

1. Enterprise Architecture

11

3. Overview of Zachman FrameworkRow 1: The Planner Perspective

Motivation/Why: Business goals

Ex: Company Core Values, Mission Statement, Strategic Goals

12


Data/What: Objectives.Multiple objectives align and help achieving the business goals.

Each objective should provide the outputs clearly.

13


Function/How: How to achieve business objectives ?

In this cell we mostly concentrate on the all the aspects of the activity to achieve the goal.

14


Network/Where : Alignment of the objectives

Ex: Head office, Manufacturing Units, Dealer Locations

15


People/Who: Stakeholders related to each function & objective

Ex: Roles & Responsibilities in the Process.

16


Time/When : Cycles and events related to each function

Ex: External events, Process execution.

17

3. Overview of Zachman FrameworkRow 2: The Owner Perspective

Motivation/Why: Business Procedures and standards for each process.

Consider various constraints while achieving this goal.

18


Data/What: Business data

Ex: Inputs & Outputs for each functioning Unit.

19


Function/How: Business Process

One of the most important block in the Zachman Framework Architecture.

20


Network/Where: Locations related to each process / objectives

Ex: Communication may be through email, mail, fax, VoIP

21


People/Who: Roles and responsibilities in each process

22


Time/ When: Events for each process and sequencing of integration and process improvements.

Owner will go through the life cycle of the product i.e. Corporate calendar

Planner will propose various proposals .

23

3. Overview of Zachman FrameworkRow 3: The Designer Perspective

Motivation/Why: Policies, standards and procedures associated with a business rule model.

Provide a model or blueprint of enterprise.

24


Data /What: Data models and data relationships underlying information

The data received from the owner is now verified by the designer.

The designer may schedule data backup at this stage.

25


Function/How: Information systems and their relationships

Ex: The designer defines the functions of different modules of the enterprise.

The designer checks the process for access control, recovery control .

26


Network/Where: Distributed system architecture for locations

Ex: The designer now designs the network and depending on the security of the data provides security end to end or link to link or both.

27


People/Who: Access privileges constrained by roles and responsibilities

Ex: Role are assigned to different users based on their skillset.

A hierarchy is built for better result.

The end product of every employer is decided.

28


Time/When : Events and their triggered responses constrained by business events and their responses

Ex: Designers defines the timely events of the enterprise and the up gradation of product to be done on timely basis.

29

3. Overview of Zachman FrameworkRow 4: The Builder Perspective

Motivation/Why: Business rules constrained by information systems standards

Ex: This cell deals with the constrained due to the limitation of resources and technology.

30


Data/What: DBMS type requirements constrained by logical data models

Ex: Requirement are expressed in technology format.

The main goal of this cell is to make sure that the data is available in proper format i.e. secured for various technologies.

31


Function/How :Specifications of applications that operate on particular technology platforms

Ex: The builder decides what technology to be used for the particular process and its counter measures.

32


Network/Where: Specification of network devices and their relationships within physical boundaries

Ex: This cell decides which hardware to use for networking and where they should be installed.

33


People/Who: Specification of access privileges to specific platforms and technologies .

Ex: What access control should be provided to different people for different technology??

Also the workflow is decided .

34


Time/When: Specification of triggers to respond to system events on specific platforms and technologies

This stage decides when to trigger which process.

When to release a particular data for a particular process???

35

3. Overview of Zachman FrameworkRow 5: The Sub-Contractor Perspective

Motivation/Why: Business rules constrained by specific technology standards .

Reduce the complexity of the operation.

Provide better quality work in specific time frame.

36


Data/What: Data definitions constrained by physical data models

37


Function/How: Programs coded to operate on specific technology platforms

38


Network/Where: Network devices configured to conform to node specifications

39


People/Who: Access privileges coded to control access to specific platforms and technologies

40


Time/When: Timing definitions coded to sequence activities on specific platforms and technologies

41

4. The Owner’s Perspective (Row 2) Who is Owner?

What is Owner’s Perspective? Business Process

Business Model

Entities & Relationships

The Complete facts about business & processes.

42

4. The Owner’s Perspective (Row 2) Owner’s Problems in Enterprises.

Business Process

Internal & External Entities

Analyzing changes in the business processes.

Business Entities Adding

Removing

Merging

43

4. The Owner’s Perspective (Row 2)How does this model solve these problems?

Holistic

Objective

Complete Understanding

Revisiting the Car Company.

44


45


46


47


48


49


50

4. The Owner’s Perspective (Row 2)What is important in business.

Classification of Data:

Highly Sensitive

Ex: Financial Data / Future StrategiesVery few people have access (Access control & Authorization)Secrecy (Strict Confidentiality; Digital Signatures + Encryption)Validity (Integrity & Availability)

Sensitive

Ex: Operational InformationComparatively large group knows (Access Control & Authorization)Secrecy (Confidentiality; Encryption only, No Digital Signatures)Validity (Integrity & Availability)

4. The Owner’s Perspective (Row 2) Classification of Data (ctd…)

Company Secret:

Ex: Business ProcessesCompany wide everybody knows. (Access control & Authorization)Everyone can read but only few can modify (top levels)No Secrecy (No Confidentiality)Validity (Integrity)

Public:

Ex: Quarterly ResultsPublically available information (No Access control or authorization)No Secrecy (No Confidentiality)Validity (Integrity)


Data Sensitivity

Financial Data Highly Sensitive

Research Statistics Highly Sensitive

Design Requirements Highly Sensitive

Design Document Highly Sensitive

Test Cases Sensitive

Test Results Highly Sensitive

Defining Assembly Company Secret

Marketing Strategy Sensitive

Quarterly Statements

Public


Define the business process How components function & how they

interact.

Use rules, regulation & feedback. Marketing Research

• Refer information about previously made cars/competitive cars.

• Produces "Statistics" for PlanningSecurity:

Only available to Market Research & Planning departments

Designing may access it based on requests.Planning•Refers the "Statistics" from Marketing Research•Uses experience as 'feedback‘.•Produces "Design Requirements", "Marketing Strategy", "Sales

Strategy”•Security:

• Only available to planning.


Design• Refers "Design Requirement" • Uses regulations & experience as 'feedback'.• Produces "Design Document“• Security:

• Available to Planning, Design, Regulatory check

Design Regulations check• Refers "Design Document“• Uses

• design guide lines as 'control‘• Previous experience as 'feedback‘• Produces "Acceptance Status".

• Security:• Available to Planning, Design, Regulatory

check.


Sandbox• Refers "Design Document“• Uses

• Manual Manufacturing & Testing methods as 'control‘

• Previous experience as 'feedback‘• Produces "Test Results“

• Security:• Available to Testing & Planning.

Manufacturing• Refers "Design Document“• Uses

• Manufacturing methods as 'control‘• Previous experience as 'feedback‘• Produces "Cars“

• Security:• Available to Manufacturing, Design &

Planning.


Marketing • Refers "Marketing Strategy”• Uses

• Marketing methods as 'control’• Previous experience as 'feedback’

• Produces public awareness/hype of the new car

Sales• Refers "Sales Strategy”• Uses dealerships & other methods as 'control’• Produces

• defines dealers & geographical availability.• channels for supply• serves actually demand


Market Research : Where market is ex: Detroit

Planning: Head office ex: New York (corporate HQ)

Design: Where designs are made as per requirements ex: • SF (US specific security requirements)• Munich, Germany (Basic design)

Sandbox: Where test models are created and tested ex: Detroit (Test manufacturing & testing)


Manufacturing: Where cars will be manufactured ex: • China(all basic parts will be

manufactured)• India (backup supply)• Detroit (Basic frame & assembly for all

the parts)• Fremont, CA (Backup facility)

Marketing: at head quarter ex: NY (Marketing head office)

Sales: at head quarter ex:• NY (Sales head office)• All regions will have their regional

branches.


Security:

1. Inter-office communication using VPN on

Frame-relay.

2. Inter-office backup-communication using lease

lines.

3. Intra-office communication using Giga-bit

Ethernet.

4. Intra-office backup-communication using lease

lines.

5. Each office network is protected by Firewall &

Gateway.

6. One active (NY) & one backup authentication

servers.

7. Each office has several certificates, for

authentication, integrity & authorization.


Define Roles & Responsibility.

Organizational Chart.

Departments

Department HeadHigher control over departmentMight have access to other

departments

Department Staff


When should things happen.

Corporate Calendar.

Sequence of the functions (Col 2) Specific Milestones.

Ex: • Design dead line• Testing Results dead line• Production start date• Market Release date• Sales start date.• Sales Targets dead lines

Each of them refers / depends on other.


Market Research


Earn Money

Corporate EthicsEx: • Ethics in Human Resources• Ethics in Finance• Ethics in Production• Ethics in Intellectual Property.

Government Rules & Regulations

6. Criticism Generalized

Every business is special.

Old school

Analysis paralysis

Hard to include changes

7. Other Frameworks The Open Group Architectural Framework (TOGAF)

The Federal Enterprise Architecture.

The Gartner

7. Other FrameworksThe Open Group Architectural Framework (TOGAF)

Defines categories as follows Business architecture.

Application architecture.

Data architecture.

Technical architecture.

7. Other Frameworks

Federal Enterprise Architecture (FEA)

FEA requires all of the following: A perspective on how enterprise architectures should be

viewed.

A set of reference models for describing different perspectives of the enterprise architecture.

A process for creating an enterprise architecture

A transitional process for migrating from a pre-EA to a post-EA paradigm

7. Other Frameworks

Gartner

• Constituents: business owners, information specialists, the technology implementer.

• Believes in defining goals first.

• Prime importance is strategy.

7. Other Frameworks• Taxonomy completeness : How well you can use the

methodology to classify the various architectural artifacts.

• Process completeness : How the methodology guides you through a step-by-step process for creating an enterprise architecture.

• Reference-model guidance : How useful the methodology is in helping you build a relevant set of reference models.

• Practice guidance : How much the methodology helps you assimilate the culture in which it is valued and used.

7. Other Frameworks

Taxo

nom

y

Compl

eten

ess

Proc

ess co

mpl

eten

ess

Refer

ence

-mod

el g

uida

nce

Prac

tice

guid

ance

0

1

2

3

4

ZACHMANTOGAFFEAGARTNER

7. Other Frameworks (Comparision)

• Maturity model : Level of guidance to assess the effectiveness and maturity of different organizations entities.

• Business focus : to whether the methodology will focus on using technology to drive business value,.

• Governance guidance : How much help the methodology will be in understanding and creating an effective governance model.

• Partitioning guidance : How well the methodology will guide you into effective autonomous partitions of the enterprise.


Maturity model

Business focus

Governance guidance

Partioning guidance

0

0.5

1

1.5

2

2.5

3

3.5

4

4.5


7. Other Frameworks (Comparision)• Prescriptive catalog : How well the methodology guides

you in setting up a catalogue of architectural assets .

• Vendor neutrality : How likely you are to get locked-in to a specific consulting organization by adopting this methodology.

• Information availability : The amount and quality of free or inexpensive information about this methodology

• Time to value : The length of time you will likely be using this methodology.


Pres

crip

tive

Catal

og

Vendo

r neu

tral

ity

Info

rmat

ion

avai

labi

lity

Tim

e to

val

ue0

1

2

3

4


ConclusionZachman Framework provide a holistic view of the Enterprises. The best case could also include consideration for future expansions and some unexpected changes to the organization. At the same time doing this may lead to “Analysis Paralysis”. So before implementing / accepting Zachman alternate solutions should be analyzed.

References• Enterprise Security Planning, Dr. Ertaul

[http://www.mcs.csueastbay.edu/~lertaul/CSTC6899INTRODUCTION.pdf ]

• IBM Enterprise Architecture [http://www-01.ibm.com/software/info/itsolutions/enterprisearchitecture]

• A Comparison of the Top Four Enterprise-Architecture Methodologies[http://msdn.microsoft.com/en-us/library/bb466232.aspx]

• History of the Frameworks[http://www.thefullwiki.org/Enterprise_architecture_framework]

• Gartner [http://www.gartner.com/DisplayDocument?doc_cd=133132]

• "Enterprise Architecture: Using the Zachman Framework", O'Rourke, Fishman, Selkow

• "The Zachman Framework Populated with Baseball Models", Terry Bahill, Rick Botta, and Jesse Daniels

Thank You!

by: viral rathod aman goyal 1. 1. enterprise architecture. 2. history of enterprise architecture 3....

Documents

ibm enterprise architecture

owners perspective row

adoption influence slide

framework approaches

overview of zachman

criticism of zachman

planner perspective

planner perspective