Zachman framework row 2 the owner perspective
Download
1 / 79

Zachman Framework Row 2 : The Owner Perspective - PowerPoint PPT Presentation


  • 112 Views
  • Uploaded on

CS 6899. Zachman Framework Row 2 : The Owner Perspective. By: Viral Rathod Aman Goyal. Organization. Enterprise Architecture. History of Enterprise Architecture Overview of Zachman Framework The Owner’s Perspective (Row 2) Security in Owner’s Perspective. Criticism of Zachman Framework

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Zachman Framework Row 2 : The Owner Perspective' - lynch


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Zachman framework row 2 the owner perspective

CS 6899

Zachman FrameworkRow 2 : The Owner Perspective

By: Viral Rathod

AmanGoyal


Organization

Organization

Enterprise Architecture.

History of Enterprise Architecture

Overview of Zachman Framework

The Owner’s Perspective (Row 2)

Security in Owner’s Perspective.

Criticism of Zachman Framework

Other Framework / Approaches.


1 enterprise architecture

1. Enterprise Architecture

What is Enterprise?

What is Enterprise Architecture?

Why to use an Enterprise Architecture?

What are currently available solutions?

IBM Enterprise Architecture

SAP – ERP

Oracle Enterprise Manager


2 history of enterprise architecture

2. History of Enterprise Architecture

1980-1990

1990-2000

2000-2010

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

  • CapgeminiIntegrated Architecture Framework (IAF)

  • The Open Group Architecture Framework (TOGAF) 1.0

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

TOGAF 7.0 / 8.0 / 9.0

Zachman

DoDAF1.0 / 2.0

FEAF (mostly complete)

Development of various Enterprise Architecture:


2 history of enterprise architecture1

2. History of Enterprise Architecture

Zackman

1987

TAFIM

1994

Adoption

Relationships between various Enterprise Architecture:

EAP

1992

TOGAF

1995

Influence

FEAF

1999

C4ISR

1996

DODAF

2003

TEAF

2000


3 overview of zachman framework

3. Overview of 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.

What is Zachman Framework?


3 overview of zachman framework1

3. Overview of Zachman Framework

Any complex problem involving multiple individual components.

E.g. Flight Reservation System.

E.g. Building a rail road.

E.g. Building Empire State Building.

What problems does it solve?



1 enterprise architecture1

1. Enterprise Architecture

Market Research

Company

Most basic Work Flow Diagram for Car Manufacturing.

Cars


1 enterprise architecture2

1. Enterprise Architecture

Car Manufacturing company

Design

Regulation Check

HR

Finance

Testing

Manufacturing for Testing

Marketing

Manufacturing

Sales



3 overview of zachman framework3

3. Overview of Zachman Framework

  • Motivation/Why: Business goals

  • Ex: Company Core Values, Mission Statement, Strategic Goals

Row 1: The Planner Perspective


3 overview of zachman framework4

3. Overview of Zachman Framework

  • Data/What: Objectives.

  • Multiple objectives align and help achieving the business goals.

  • Each objective should provide the outputs clearly.

Row 1: The Planner Perspective


3 overview of zachman framework5

3. Overview of Zachman Framework

  • 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.

Row 1: The Planner Perspective


3 overview of zachman framework6

3. Overview of Zachman Framework

  • Network/Where : Alignment of the objectives

  • Ex: Head office, Manufacturing Units, Dealer Locations

Row 1: The Planner Perspective


3 overview of zachman framework7

3. Overview of Zachman Framework

  • People/Who: Stakeholders related to each function & objective

  • Ex: Roles & Responsibilities in the Process.

Row 1: The Planner Perspective


3 overview of zachman framework8

3. Overview of Zachman Framework

  • Time/When : Cycles and events related to each function

  • Ex: External events, Process execution.

Row 1: The Planner Perspective


3 overview of zachman framework9

3. Overview of Zachman Framework

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

  • Consider various constraints while achieving this goal.

Row 2: The Owner Perspective


3 overview of zachman framework10

3. Overview of Zachman Framework

  • Data/What: Business data

  • Ex: Inputs & Outputs for each functioning Unit.

Row 2: The Owner Perspective


3 overview of zachman framework11

3. Overview of Zachman Framework

  • Function/How: Business Process

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

Row 2: The Owner Perspective


3 overview of zachman framework12

3. Overview of Zachman Framework

  • Network/Where: Locations related to each process / objectives

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

Row 2: The Owner Perspective


3 overview of zachman framework13

3. Overview of Zachman Framework

  • People/Who: Roles and responsibilities in each process

Row 2: The Owner Perspective


3 overview of zachman framework14

3. Overview of Zachman Framework

  • 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 .

Row 2: The Owner Perspective


3 overview of zachman framework15

3. Overview of Zachman Framework

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

  • Provide a model or blueprint of enterprise.

Row 3: The Designer Perspective


3 overview of zachman framework16

3. Overview of Zachman Framework

  • 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.

Row 3: The Designer Perspective


3 overview of zachman framework17

3. Overview of Zachman Framework

  • 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 .

Row 3: The Designer Perspective


3 overview of zachman framework18

3. Overview of Zachman Framework

  • 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.

Row 3: The Designer Perspective


3 overview of zachman framework19

3. Overview of Zachman Framework

  • 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.

Row 3: The Designer Perspective


3 overview of zachman framework20

3. Overview of Zachman Framework

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

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

Row 3: The Designer Perspective


3 overview of zachman framework21

3. Overview of Zachman Framework

  • Motivation/Why: Business rules constrained by information systems standards

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

Row 4: The Builder Perspective


3 overview of zachman framework22

3. Overview of Zachman Framework

  • 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.

Row 4: The Builder Perspective


3 overview of zachman framework23

3. Overview of Zachman Framework

  • 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.

Row 4: The Builder Perspective


3 overview of zachman framework24

3. Overview of Zachman Framework

  • 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.

Row 4: The Builder Perspective


3 overview of zachman framework25

3. Overview of Zachman Framework

  • 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 .

Row 4: The Builder Perspective


3 overview of zachman framework26

3. Overview of Zachman Framework

  • 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???

Row 4: The Builder Perspective


3 overview of zachman framework27

3. Overview of Zachman Framework

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

  • Reduce the complexity of the operation.

  • Provide better quality work in specific time frame.

Row 5: The Sub-Contractor Perspective


3 overview of zachman framework28

3. Overview of Zachman Framework

  • Data/What: Data definitions constrained by physical data models

Row 5: The Sub-Contractor Perspective


3 overview of zachman framework29

3. Overview of Zachman Framework

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

Row 5: The Sub-Contractor Perspective


3 overview of zachman framework30

3. Overview of Zachman Framework

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

Row 5: The Sub-Contractor Perspective


3 overview of zachman framework31

3. Overview of Zachman Framework

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

Row 5: The Sub-Contractor Perspective


3 overview of zachman framework32

3. Overview of Zachman Framework

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

Row 5: The Sub-Contractor Perspective


4 the owner s perspective row 2

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.


4 the owner s perspective row 21

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


4 the owner s perspective row 22

4. The Owner’s Perspective (Row 2)

How does this model solve these problems?

Holistic

Objective

Complete Understanding

Revisiting the Car Company.








4 the owner s perspective row 29

4. The Owner’s Perspective (Row 2)

What is important in business.

Classification of Data:

Highly Sensitive

Ex: Financial Data / Future Strategies

Very few people have access (Access control & Authorization)

Secrecy (Strict Confidentiality; Digital Signatures + Encryption)

Validity (Integrity & Availability)

Sensitive

Ex: Operational Information

Comparatively large group knows (Access Control & Authorization)

Secrecy (Confidentiality; Encryption only, No Digital Signatures)

Validity (Integrity & Availability)


4 the owner s perspective row 210

4. The Owner’s Perspective (Row 2)

Classification of Data (ctd…)

Company Secret:

Ex: Business Processes

Company 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 Results

Publically available information (No Access control or authorization)

No Secrecy (No Confidentiality)

Validity (Integrity)



4 the owner s perspective row 212

4. The Owner’s Perspective (Row 2)

  • 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 Planning

  • Security:

  • 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.


4 the owner s perspective row 213

4. The Owner’s Perspective (Row 2)

  • 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.


4 the owner s perspective row 214

4. The Owner’s Perspective (Row 2)

  • 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.


4 the owner s perspective row 215

4. The Owner’s Perspective (Row 2)

  • 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


4 the owner s perspective row 216

4. The Owner’s Perspective (Row 2)

  • 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)


4 the owner s perspective row 217

4. The Owner’s Perspective (Row 2)

  • 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.


4 the owner s perspective row 218

4. The Owner’s Perspective (Row 2)

  • Security:

  • Inter-office communication using VPN on Frame-relay.

  • Inter-office backup-communication using lease lines.

  • Intra-office communication using Giga-bit Ethernet.

  • Intra-office backup-communication using lease lines.

  • Each office network is protected by Firewall & Gateway.

  • One active (NY) & one backup authentication servers.

  • Each office has several certificates, for authentication, integrity & authorization.


4 the owner s perspective row 219

4. The Owner’s Perspective (Row 2)

  • Define Roles & Responsibility.

  • Organizational Chart.

  • Departments

    • Department Head

      • Higher control over department

      • Might have access to other departments

    • Department Staff



4 the owner s perspective row 221

4. The Owner’s Perspective (Row 2)

  • 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.



4 the owner s perspective row 223

4. The Owner’s Perspective (Row 2)

  • Earn Money

  • Corporate Ethics

    • Ex:

      • Ethics in Human Resources

      • Ethics in Finance

      • Ethics in Production

      • Ethics in Intellectual Property.

  • Government Rules & Regulations


6 criticism

6. Criticism

Generalized

Every business is special.

Old school

Analysis paralysis

Hard to include changes


7 other frameworks

7. Other Frameworks

The Open Group Architectural Framework (TOGAF)

The Federal Enterprise Architecture.

The Gartner


7 other frameworks1

7. Other Frameworks

The Open Group Architectural Framework (TOGAF)

Defines categories as follows

Business architecture.

Application architecture.

Data architecture.

Technical architecture.


7 other frameworks2

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 frameworks3

7. Other Frameworks

Gartner

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

Believes in defining goals first.

Prime importance is strategy.


7 other frameworks4

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 comparision

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.



7 other frameworks comparision2

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.



Conclusion

Conclusion

Zachman 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

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



ad