Enterprise Architecture – Vision and Reality on the Same Page

Enterprise Architecture – Vision and Reality on the Same Page

Dr Simon PolovinaLEAD Certified Enterprise Architecture eXpert

TOGAF Foundation CertifiedSAP Certified Associate Enterprise Architect

Conceptual Structures Research Group

EA Vision & Reality 2

Overview

• History of EA• Why EA• What is EA• EAFs – Zachman, TOGAF, LEAD and others• Metamodels, Ontology and Semantics• Essential Tool as an Exemplar• Relevance to Your Organisation• Glimpse into the future• Summary, and ReferencesOctober 2014


Where did EA come from?• EA essentially began in 1987, with the publication of "A

Framework for Information Systems Architecture," by J.A. Zachman (IBM Systems Journal), in which:– He stated that “The cost involved and the success of the business

depending increasingly on its information systems require a disciplined approach to the management of those systems.”

– Laid out both the challenge and the vision of enterprise architectures that continue to guide the field today

– Gave a vision was that business value and agility could best be realised by a holistic approach to systems architecture that explicitly looked at every important issue from every important perspective

– Was originally described as an information systems architectural framework, soon renamed as an enterprise architecture framework

Zachman (1987), Sessions (2007)

October 2014


v1

October 2014

Sowa & Zachman (1992)

EA Vision & Reality 5October 2014

And

Toda

y…


TOGAF• In 1995, TOGAF 1.0 mainly based

on TAFIM, developed since the late 1980s by the US DoD

• Today, TOGAF 9.1 has a formal Content Metamodel, and many more examples and templates

October 2014


Why do we need it?• Originally (reactive):

– System complexity—Organisations were spending more and more money building IT systems; and

– Poor business alignment—Organisations were finding it more and more difficult to keep those increasingly expensive IT systems aligned with business need

– Even More Cost, Even Less Value (Sessions, 2007)

October 2014


Why do we need it?• Today (proactive, too):

– Fragmented to Integrated—optimise across the enterprise the often fragmented legacy of processes (both manual and automated), into an integrated environment that is responsive to change and supportive of the delivery of the business strategy

– IT and business success—effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage

– Achieving the right balance between IT efficiency and business innovation (TOGAF, 2011)

October 2014


The scope of EA

• Understanding the knows and don’t knows of the Enterprise that it needs to know to survive and to succeed:– “... there are known knowns; there are things we know that we know.

There are known unknowns; that is to say, there are things that we now know we don't know. But there are also unknown unknowns – there are things we do not know we don't know.”(United States Secretary of Defense, Donald Rumsfeld, 2002)

• Complex Problems; Simple Solutions– “Everything should be made as simple as possible, but no simpler

than that”(attributed to Einstein)

October 2014

The Semiotic Ladder(Organisational Semiotics, after Stamper 1997)

PHYSICAL WORLD signals, traces, physical dimensions,hardware, component density, speed, economics

EMPIRICS patterns, variety, noise, entropy,channel capacity, redundancy, efficiency, codes, ...

SYNTACTICS formal structure, language, logic,data, records, deduction, software, files, ...

SEMANTICS meanings, propositions,validity, truth, signification, denotations, ...

PRAGMATICS intentions, communication,conversations, negotiations, ...

SOCIAL WORLD beliefs, expectations,commitments, contracts, law, culture, ...

Hum

an In

form

atio

n Fu

nctio

nsVA

LUE

PRO

DUC

ING

The

Tech

nolo

gy P

latfo

rmCO

ST IM

POSI

NG

Enterprise Architecture

The

Com

pute

r Wor

ld

The Real World?

more like a semiotic

snake to me

October 2014 EA Vision & Reality 10

http://scholar.google.com/scholar?hl=en&lr=&q=stamper+organisational+semiotics


What is EA?

• Enterprise• Architecture• Models

October 2014

Enterprise

• “Space: the final frontier. These are the voyages of the starship Enterprise. Its five-year mission: to explore strange new worlds, to seek out new life and new civilizations, to boldly go where no man has gone before.” (Star Trek, quotes)

• Origin: late Middle English: from Old French, 'something undertaken', feminine past participle (used as a noun) of entreprendre, based on Latin prendere, prehendere 'to take‘ (OED)

• An undertaking, especially one of some scope, complication, and risk (thefreedictionary.com)

• A business organisation (thefreedictionary.com)• You and me


http://www.imdb.com/title/tt0060028/quotes

http://www.oxforddictionaries.com/definition/english/enterprise

http://www.thefreedictionary.com/enterprise

http://www.thefreedictionary.com/enterprise

Architecture

• The art or practice of designing and constructing buildings (OED)• The complex or carefully designed structure of something (OED)• The conceptual structure and logical organization of a computer

or computer-based system (OED)• Winchester Mystery House• “From the blank piece of paper to the last nail in the wall”


http://www.oxforddictionaries.com/definition/english/architecture



http://en.wikipedia.org/wiki/Winchester_Mystery_House

Models

• Can’t touch an enterprise, but it’s very real

• Only see through models• “All Models are Wrong, But Some are Useful” (Box, 1987)

Sowa, 2002



Enterprise Architecture Frameworks

• The Two Representative Frameworks:– Of the many…– Zachman, TOGAF

• What they offer– Artefact vs. Process– Reference Content– Metamodels– Ontology– Semantics

• ToolsOctober 2014


Artefact vs. Process• The Zachman Framework for

Enterprise Architectures– Originally self-described as a

framework– But more accurately defined

as a taxonomy– And now Enterprise Ontology– A declarative grid of objects

and relationships, not process (directly)

– You populate the grid with your EA

• It’s thus artefact-driven

October 2014


Artefact vs. Process

• The Open Group Architectural Framework (TOGAF)– Also called a framework– Central to TOGAF is its

Architecture Development Method (ADM)

– It’s thus process-driven

October 2014

18October 2014

19EA Vision & Reality

http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap34.html


Some Others• The Federal Enterprise

Architecture (FEA)– Can be viewed as either

a) an implemented enterprise architecture, or

b) a proscriptive methodology for creating an EA

– Was FEAF• Framework dropped

accordingly…– Segments

• EA in Organisational units• Technical, Business and Data

architecturesOctober 2014

Sessions (2007)


Some Others• Gartner

– Can be best described as a enterprise architectural practice

– proprietary, by the respected GartnerGroup

• LEAD– Layered Enterprise Architecture

Development (now simply LEADing Practice)

– again practice, but open source– with a developing ecosystem across

industry and academic expertise

October 2014


LEAD• Overview diagram• & more about (in notes)

October 2014


LEAD

’s St

ruct

ural

Way


LEAD’s Structural Way• As a detailed view


In all levels of detail…

• One for LEADing Practice Framework Concepts, Enterprise Modelling & Enterprise Architecture Artifacts, Value Reference, Service Reference, Process Reference, Maturity Reference, Architecture and Modelling Skills Mapping

October 2014


Metamodels• Meta = ‘about’• White entities are “core”

and not to be omitted• Red/Blue/Green entities

are “extensions” and can be omitted

• Entity renaming is possible

• Modification and removal of entities is not recommended

• It’s the base template for your EA

October 2014

27

SAP

EAF

Infrastructure Consolidation Extension Governance Extension

Process Modelling Extension Data Modelling Extension

Business / IT Alignment Extension Core Content

ARCHITECTURE VISION, CONTEXT AND ROADMAP

BUSINESS ARCHITECTURE

TECHNOLOGY ARCHITECTUREAPPLICATION

ARCHITECTUREDATA ARCHITECTURE

Associated With All Objects

Organisation Unit

Goal

Objective

MeasureGovernance Extension

( Business , Information System ) ServiceServices are Contained in Core , Business / IS split supports the Business / IT Alignment Extension

Function

Process

Actor

Role

ControlProcess Extension

EventProcess Extension

ProductProcess Extension

Data Entity

Logical Information Component

Data Extension

LocationInfrastructure Consolidation

Extension

Physical Information Component

Data Extension

Logical Application Component

Physical Application ComponentInfrastructure

Consolidation Extension

Logical Technology Component

Infrastructure Consolidation Extension

Physical Technology Component

Principle Constraint Requirement

ContractGovernance Extension

Gap Work Package

Driver

Platform Service

Owns and governs

Operates in

Operates in

Is Hosted in

Is Hosted inIs Hosted inEncapsulates

Encapsulates

Resides within

SuppliesIs Supplied By

Is Realised by Realises

Operates on

Is processed by

Provides, consumes

Is accessed and updated through

Resides within

Is implemented on

Provides platform forImplements

Is realised through

Contains

Co

ntai

ns

Co

ntai

ns

Con

t ai n

s

Con

t ai n

s

Contains

Belongs to

Co

nsum

es

Participates in

Interacts with, Performs

Performs task in

Generates, Resolves

Produces

Is Produced byIs owned by

Owns

Supports, Is performed by

Accesses

Can be accessed by

Orchestrates, decomposes

Supports, Is realised by

Is bounded by

Provides governed interface to access

Produces

Is Produced by

Involves

Participates in

Involves

Is Resolved by, Is Generated by

Generates, Resolves

Is Resolved by

Is Resolved by, Is Generated by

Resolves

Supports, Is realised by

Orchest rat es,

decom

poses

Ensures correct operation of

I s gui ded

by

Governs, Measures

Is governed and measured byIs Provided to

Is owned and governed by

Is tracked against

Sets performance criteria for

Sets performance criteria for

Is tracked against

Is motivated by

Motivates

Creates

Addresses

Is realised through

Realises

Service QualityGovernance Extension

Applies to

Meets

Applies to Meets

Is Performed by

Is Supplied or Consumed by

Supplies or Consumes


BEES

T

October 2014




BEEST Production and Logistics Organization Unit

Lower Working Capital / Facilitate

Supplier Collaboration

Improve Visibility of Leipzig Inventory to

Suppliers during 2005

Receiving and Material Storage

Costs KPI

Source Supplier Products for Operations

Supplier Collaboration and

Operational Procurement

Manage Warehouse and Storage

Leipzig Production Manager

MRP Controller

Inventory falls below forecast

production demand

Inventory replenishment

triggered

BEEST 911 GT 3 Sports Car

Stock Item

Inventory Records

LeipzigAssembly Factory

Purchsoft Stock Master

E- Procurement , Ordering and

Payments

BEEST Purchsoft

Procurement Software Suite

Purchsoft E -Procurement for

Oracle 8iVersion 3.1

Leoni - BEESTDriveTrain Supply

Contract

Global trend for customization and

increased efficiency of production

EDI / Bank Payments Engine

Daily Replenishment,Daily response

to replenish trigger


“Infi

nity

” Hi

gh-T

ech

October 2014




“Infinity” Manufacturing Unit

Increase Revenue

Improve Capacity Utilisation by 25% in

2007

Capacity Utilisation KPI

Capacity load / Resource Capacity *

100

Repetitive Manufacturing Planning Business Service

Make-to-Order Manufacturing

Production Planning

Head of Home Computer Product

Manufacturing

Production Planner

Confirmed Sales Order Received and Product current and

not < 200 items

Sales Order Arrives

InfinityPersonal Computer

Model xxx

Product

Product Stock Records

InfinityChicago

Production Centre

SAP Product Master Data

Supply Planning Enterprise Service

SAP Query Supply Planning AreaEnterprise Service

Database Server

HP Integrity Superdome

( Productiion Instance -Npar 12)

Manufacturing -Sales Contract

Deliver Shareholder Value

Transaction Processing

Plan must be updated each

hour on a 24 x7 x 365 basis

OutsourcedAustin Data

Centre

Map

ping

TO

GAF

to S

AP E

AFPreliminary

Business Architecture

Data Architecture

Application Architecture

Technology Architecture

Architecture Vision

Organisation Unit

Function

Business Service

Location

ActorRole

EventControl

Data Entity

Architecture Building Block

Process

StrategyGoal

Objective

Measure

User Interface

Principle

ScopeConstraint

VisionStakeholder Map

Deliverable

Architecture Framework

Cross-AspectRequirement

Gap Analysis

ProjectImplementation Roadmap

Contract

Candidate Solutions

Application

Technology ComponentPlatform Service

Architecture Vision, Context and Roadmap

Business Architecture

Technology Architecture

Application Architecture

Data Architecture

PrincipleConstraint

RequirementGap

Work Package

Organisation Unit

GoalObjective

Measure

FunctionProcess

ActorRole

ControlEvent

Product

Location

Contract

Driver

Service Quality

Business Service

Data EntityLogical Information ComponentPhysical Information Component

Logical Application ComponentPhysical Application Component

Logical Technology ComponentPhysical Technology

Component

Platform Service

Information System Service

Architecture Building Block

Not within the scope of structured modelling

Moved Phase. Goals and Objectives in the Vision phase would be collected in SAP EAF, but not formally modelled.

Changed to a more generic name.

Contract term in TOGAF equates to a terms of reference.

SAP EAF extends concept to include service contracts

Candidate solutions are shown as an architecture and don’t require metamodel entities

An implementation roadmap is a view of work packages.

User Interface is not considered to be architecturally significant for

Enterprise Architecture and is not formally included in SAP EAF

Changed to a more generic name.

SAP EAF extends applications and technology to be both logical and physical

SAP EAF adds an information component concept to allow segmentation and bounding of data

SAP EAF allows independent views of services from a business and IS perspective

SAP EAF extends service governance to allow service qualities and contracts to be applied to services

SAP EAF adds the concept of a Driver that motivates business to achieve objectives

Direct TOGAF – SAP EAF Mapping

Indirect TOGAF – SAP EAF Mapping

Not taken from TOGAF to SAP EAF

SAP EAF extension to TOGAF

TOGAF concept not relevant to structured modelling

Assumption

SAP EAF adds the concept of Assumptions


Synonyms etc…



Ontology• In Philosophy:

– A theory of being– “does truth exist?” or “does energy exist?”

• In Computer Science– Gruber “In the context of knowledge sharing, I use the term

ontology to mean a specification of a conceptualization. That is, an ontology is a description (like a formal specification of a program) of the concepts and relationships that can exist for an agent or a community of agents. This definition is consistent with the usage of ontology as set-of-concept-definitions, but more general. And it is certainly a different sense of the word than its use in philosophy.” (emphasis added).” (Malik, 2009)

October 2014


Context

Semantics

Rule of 3:

October 2014

Object Objectrelation

Some triples...

Laurier & Poels (2012)

w3c.org

Value-Performance Meta Model, leadingpractice.com


w3c.org

leadingpractice.com

Laurier & Poels (2012)

Some contexts…


Lanir (2012)

Also, Peirce's Triadic

Objects Create Signs



Tools• From Visio to Essential Project

– Capturing and structuring what’s in our heads, gut instinct, pen & paper, unstructured records…

• Picking one – Visio, ARIS, Sparx, iGrafx, …

• How well do they handle the semantics?– Rule of 3

• To what extent do they create signs from objects?– So you optimise the object not the sign

• An illustration: Essential ProjectOctober 2014

EssentialEssential Import

UtilityEssential

Modeller in Protégé

Essential Viewer

Semantic MappingHow spreadsheet maps to EMM

Knowledge BaseClasses and Instances of EMM

ViewsDynamically rendered from knowledge base

snapshot

UpdateUpload Publish

EMM = Essential Meta Model

Render

38October 2014 EA Vision & Reality

Essential Architecture Manager (EAM)A means to capture, view and analyse an Enterprise Architecture using the Essential Meta-Model

Domain experts and architects capture and publish enterprise architecture

information

Business and IT stakeholders view and analyse reports to support decision

making

39October 2014 EA Vision & Reality


Making it/IT relevant to You

• EA as a foundation for execution• “From Concept to the last network cable we

fit”• What kind of business are we?• Aligning our Vision with our (IT) Reality• Moore’s Core-Context• Four Operating Models

October 2014

Moo

re’s

core

-con

text



The Four Operating ModelsW

here

is y

our o

rgan

isatio

n?Co

ordi

nate

d, D

iver

sified

, Rep

licat

ed o

r Uni

fied?

October 2014 Ross et al. (2006)


Stakeholders

• Power Grid• RACI• Pragmatics

October 2014


The Baseline to Target Phases

• ‘As-Is’ to ‘To-Be’ Phases i.e.:– Business Architecture– Information Systems

Architecture– Technology

Architecture• Populating the

Architecture Definition Document (ADD)

October 2014

http://www.togaf.biz/TOGAFWebsitefiles/template_arch_def.doc

http://www.togaf.biz/TOGAFWebsitefiles/template_arch_def.doc


Measuring EA

• Reducing Cost and Risk• Vs. Increasing Profit and Value• KPI & PPI

– Key ‘vs’ Process Performance Indicators• “If it can’t be measured, it can’t be evaluated,

if it can’t be evaluated it can’t be managed”• Measuring the objects not the signs• Useful Models

October 2014


EA Maturity

October 2014

http://www.enterprise-architecture.com/EAvaluator/


‘Other’ Management Aspects

• Enterprise Architecture and…– Project Management– Change Management– Service Management– Governance

• The Baseline to Target Loop– Solutions or Better Questions?

October 2014


From Projects to Enterprise

• Think BIG; start small• Capability, Segment and Strategic EA

– The same vision and reality across the enterprise at different levels (Chapter 20 in TOGAF, 2011)

• Enterprise-wide Governance– Across all the levels (projects) thus the enterprise

as a whole– Thus governing the overall EA, not just the EAs

that make it up

October 2014


A possible future glimpse• Process Oriented Architecture (POA)

– Given that BPM and SOA are not Application and Data as given in the ‘classic’ EAFs, but much in common?

– e.g. Information Systems Architecture – Data/Application in TOGAF

– LEAD’s integration of Enterprise Architecture with Enterprise Modelling and Enterprise Engineering

– How would the TOGAF ADM and the Zachman grid look with POA?

• Transaction Oriented Architecture– Transactions as a strategic-level concept as well as an operational

concept (Polovina, 2013)

October 2014


A Mindset and Toolset for EA

@1October 2014


Summary• Overview• History of EA• Why EA• What is EA• EAFs – Zachman, TOGAF, LEAD and others• Metamodels, Ontology and Semantics• Essential Tool as an Exemplar• Relevance to your org incl. outline exercises• Glimpse into the future (POA, TOA)• Below: ReferencesOctober 2014


References

• See the notes to this slide

October 2014

Date post:	13-Feb-2017
Category:	Business
Upload:	simon-polovina
View:	999 times
Download:	1 times