TOGAFTM 9 Capability Framework - The Open...

TOGAFTM 9 Capability Framework

London EAPC28 April 2009

Paul van der Merwe

TOGAF is a trademark of The Open Group.

2

Copyright © Real IRM Solutions (Pty) Ltd

2006 - 2009

TOGAF 9 Capability FrameworkApril 2009

Document ControlDate Author Version Change Reference

21/04/2009 Paul van der Merwe 00.01 No previous document

3


2006 - 2009

TOGAF 9 Capability Framework

leading enterprise architecture valueTM

Key Focus Areas

Enterprise Architecture

Strategy

Governance

April 2009

4


2006 - 2009

TOGAF 9 - Context


TOGAF Enterprise Continuum & Tools

TOGAF ADM & Content Framework

TOGAF Capability Framework

Architecture Development Method (Part II)

Architecture Capability Framework (Part VII)

Enterprise Continuum & Tools (Part V)

ADM Guidelines & Techniques (Part III)

Architecture Content Framework (Part IV)

TOGAF Reference Models (Part VI)

Business Vision and

Drivers

Business Capabilities

Informs the Business

of the current state

Ensures Realization

of Business Vision

Informs the capability

Refines

Understanding

Business needs feed into method

Delivers new business solutions

Operational changes cause updates

Sets targets, KPIs, budgets for

architecture roles

Drives need for Architecture Capability

maturity

5


2006 - 2009

Purpose Introduce TOGAF 9 Capability Framework Understand purpose of a capability Overview on how to establish an EA capability using the ADM Practical examples


6


2006 - 2009

Capability Framework


7


2006 - 2009

CapabilityA capability means

having all the desired qualities to do something, available when required

for the full duration required.

A capability is therefore:not a projectongoingsustainablebusiness-appropriate


8


2006 - 2009

Real IRM ApproachReal IRM implements capabilities within organisations based on the following principles:Directed by architectural principlesInformed by industry best practices, frameworks and standardsEnabled through a well-defined and managed architectureTransferred into a sustainable practiceEmpowered through knowledge transferGuided by business requirements


9


2006 - 2009

Business Environment



Capability

Capability Solution and Technology

Capability People

Capability Processes

Capability Product / Service

Capability Implementation

10


2006 - 2009




Capability

People


Plan Build Run

Gove

rnan

ce

Perfo

rman

ce M

gt

Infra

stru

ctur

e Mgt

Life

cycle

Man

agem

ent

Cons

umer

Mgt

Chan

ge L

eade

rshi

p

Infrastructure

Information

Application

Method

11


2006 - 2009

Use the ADM to define Architecture CapabilityGo through each phase with the requirement to establish an Architecture Capability based on TOGAF.


12


2006 - 2009

Architecture ScopeWhat is the breadth of the overall architecture effort?


Group Architecture

Company Architecture Company Architecture

Division Architecture




Project Architecture








13


2006 - 2009

Architecture Scope

What is the scope of the overall architecture effort?Align business and ITApplication integrationInformation flowTechnology deploymentIT strategyEtc.


Business Architecture

Information Architecture

DataArchitecture

ApplicationsArchitecture

TechnologyArchitecture

Knowledge

14


2006 - 2009

Architecture StakeholdersWho are the architecture stakeholders?Executive ManagementCIOIT ManagementBusiness analystsTrainersBusiness managersUsersOutsourced partners


15


2006 - 2009

Architecture Definition

Standardise the definition of architecture in the organisation

Agree the architecture domains

Agree where does architecture stop and where does design begin


© Real IRM Solutions

Sector Focus Framework

Architecture DomainBusiness Architecture

Information Architecture

Data Architecture

Applications Architecture

Technology Architecture

People

Process

Content

Tools

Products and Services

16


2006 - 2009

Architecture Maturity Assessment

Perform an architecture maturity assessment

Assess maturity in terms of: Current architecture maturity Required architecture maturity

in the short term (e.g. one year)

Ultimate required architecture maturity

Refer to public domain architecture maturity models


Environment People Process Technology

Innovation

Predictable

Standardised

Managed

Initial

17


2006 - 2009



18


2006 - 2009

Business Architecture Architecture principles that will define the architecture business rules Roles and responsibilities of the Architecture Function, including

governance structures Architecture process, including the governance processes Architecture information requirements – i.e. the architecture classification

framework that will be used Architecture performance metrics Architecture products and services


19


2006 - 2009

Architecture PrinciplesDevelop principles that guide and direct the Architecture Function, for example:How would architecture be governed?What are the rules for architecture repositories?How would architects be employed?Etc.


20


2006 - 2009

Architecture Roles


EA Repository Administrator

EA DomainArchitect

EnterpriseArchitect

EA Domain Modeller

EARepository

DomainQuality

Regulator EA Domain Owner

EA DomainTrainer

EACustomer

EA ChangeLeader

directs

standardises

quality assu

res

guide

s

administerstrains

trains

requires

trains

communicates

comm

unica

tes

manages

Please note that:• this diagram only indicates the

primary relationships between the roles and doesn’t depict all the relationships

• domain refers to at least the five primary domains, i.e. Business, Information, Data, Application and Technology. A role with domain as part of the role name would therefore be five different roles, one for each domain

EA TechnicalSpecialist

supp

orts

21


2006 - 2009

Architecture Skills FrameworkCategory Examples

Generic Skills Leadership, team working, inter-personal skills

Business Skills and Methods

Business cases, business process, strategic planning

Enterprise Architecture Skills

Modelling, building block design, applications and role design, systems integration

Program or Project Management Skills

Managing business change, project management methods and tools

IT General Knowledge Skills

Brokering applications, asset management, migration planning, SLAs

Technical IT Skills Software engineering, security, data interchange, data management

Legal Environment Data protection laws, contract law, procurement law, fraud

April 2009 TOGAF 9 Capability Framework

22


2006 - 2009

Skill Proficiency Levels

Level Achievement Description

1 Background Not a required skill though should be able to define and manage skill if required.

2 Awareness Understands the background, issues and implications sufficiently to be able to understand how to proceed further and advise client accordingly.

3 Knowledge Detailed knowledge of the subject area and capable of providing professional advice and guidance. Ability to integrate capability into architecture design.

4 Expert Extensive and substantial practical experience and applied knowledge on the subject.


23


2006 - 2009

Architecture Skills MatrixTechnical IT Skills

Legal Environment


24


2006 - 2009

Levels of GovernanceHierarchy of governance structures: Corporate Governance Technology Governance Information Technology (IT) Governance Architecture Governance

Domains of governance: Global Regional Local


25


2006 - 2009

IT Governance

IT Governance is a structure of relationships and processes to direct and control the enterprise in order to achieve the enterprise’s goals by adding value while balancing risk versus return over IT and its processes.

CobiT is the industry standard IT governance framework.


26


2006 - 2009

IT Governance

CobiT 4.1 recognises the role of Chief Architect


27


2006 - 2009

TOGAF – CobiT Mapping


28


2006 - 2009

Architecture Governance Framework Phase G of TOGAF Architecture Development Method concerns

Implementation Governance Management and control of development and evolution of enterprise architectures Only one aspect of architecture governance

Generic framework that can adapt to existing governance Identify effective processes and organisational structures, so that the

business responsibilities can be elucidated, communicated, and managed


29


2006 - 2009

Architecture Governance Framework


30


2006 - 2009

Organisational Structure


31


2006 - 2009

Architecture BoardArchitecture Board oversees strategy implementation.

Board comprises: Representative key stakeholders Executives responsible for review and maintenance of architecture Combination of

Local (domain experts, line responsibility) Global (organisation-wide responsibility)

Established with identifiable and articulated: Responsibilities and decision-making capabilities Remit and authority limits


32


2006 - 2009

Architecture ProcessCustomise ADM to integrate with: Programme / portfolio / project management processes Product development lifecycle System development lifecycle Corporate and IT governance processes and structures Change management processes


33


2006 - 2009

Architecture Framework

Develop an Architecture Framework mapped to the architecture deliverables.

E.g. What models/elements would constitute the Business Architecture?


e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

S COPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

S YSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = Fie ldRe ln = Addre ss

e .g. Phys ica l Da ta Model

Ent = Se gme nt/Table /e tc.Re ln = Pointe r/Key/etc.

e.g. Logical Da ta Mode l

Ent = Da ta EntityRe ln = Da ta Re la tions hip

e.g. Se ma ntic Model

Ent = Bus ine ss EntityRe ln = Bus ines s Re la tionship

Lis t of Things Importa ntto the Bus ines s

ENTITY = Clas s ofBus iness Thing

List of Proce sse s theBusine ss Pe rforms

Function = Clas s ofBusine ss Proce ss

e .g. "Applica tion Archite cture "

I/O = Use r ViewsProc .= Applica tion Function

e.g. "Sys te m De s ign"

I/O = Scree n/Device Forma tsProc.= Compute r Function

e.g. "Program"

I/O = Control BlockP roc.= La nguage Stmt

e.g. FUNCTION

e.g. Bus ine ss Proce ss Model

Proc. = Bus ine ss Proce ssI/O = Bus ines s Resources

Lis t of Loca tions in which the Bus ines s Ope ra tes

Node = Major Bus ine ssLoca tion

e.g. Logis tics Ne twork

Node = Bus ine ss LocationLink = Bus ine ss Linka ge

e.g. "Dis tribute d S ys te m

Node = I/S Function(Proce ssor, S torage, e tc)Link = Line Chara cte ris tics

e .g. "Sys te m Archite cture "

Node = Ha rdware /Sys te mSoftware

Link = Line Specifica tions

e.g. "Network Archite cture"

Node = Addre sse sLink = Protocols

e .g. NETWORK

Archite cture "

Planner

Owner

Builder

ENTERPRIS EMODEL

(CONCEPTUAL)

Designer

S YSTEMMODEL

(LOGICAL)

TECHNOLOGYCONSTRAINED

MODEL(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEP EOP LE

e.g. Rule Spe cifica tion

End = Sub-conditionMe a ns = Ste p

e.g. Rule Des ign

End = ConditionMe a ns = Action

e.g., Bus ine ss Rule Mode l

End = S tructura l Asse rtionMe a ns =Action Asse rtion

End = Bus iness Obje ctiveMe a ns = Bus ine ss S tra te gy

Lis t of Bus ines s Goa ls /Stra t

Ends /Means=Ma jor Bus. Goa l/Critica l S ucces s Fa ctor

Lis t of Eve nts S ignificant

Time = Major Bus iness Event

e.g. P roce ss ing Structure

Cycle = Proce ss ing CycleTime = Sys tem Eve nt

e.g. Control S tructure

Cycle = Component CycleTime = Exe cute

e .g. Timing De finition

Cycle = Ma chine CycleTime = Inte rrupt

e .g. SCHEDULE

e.g. Ma ste r Sche dule

Time = Business EventCycle = Bus ine ss Cycle

Lis t of Organiza tions

People = Major Organiza tions

e.g. Work Flow Model

People = Organiza tion UnitWork = Work Product

e .g. Huma n Inte rfa ce

People = RoleWork = De live ra ble

e .g. P resenta tion Architecture

People = UserWork = Scre en Format

e.g. Se curity Archite cture

People = Ide ntityWork = J ob

e.g. ORGANIZATION

Planner

Owner

to the Bus inessImportant to the Bus ine ss

What How Where Who When Why

Copyright - John A. Zachman, Zachman International

SCOP E(CONTEXTUAL)

Architecture

e.g. STRATEGY ENTERPRISE

e.g. Bus ines s P lan

TM

Zachman Institute for Framework Advancement - (810) 231-0531

34


2006 - 2009

TOGAF and DODAF

Source: A White Paper Published by The Open Group


35


2006 - 2009

Architecture Performance Metrics


Define EA Governance

L3

Define EA Vision AndStrategy

L3

Develop EACommunication

And Training Plan

L3

Define EA Framework

L3

Develop EA Plan

L3

EA governance process current, approved and published on DMS

EA governance instantiated Meet business demand for modelling

Plan current, approved and published on EA website

All training requirements met Adequate training

Framework instantiated

EA Vision and Strategy current, approved, incorporated in ICT Strategy and published on EA website

Plan current, approved, incorporated in ICT Plan (SAP)

Identify number of models required to meet ICT Plan

Example

36


2006 - 2009



37


2006 - 2009

Applications Architecture What functionality is required to enable the architecture process? What functionality is required to populate architecture models? What functionality is required to generate architecture views? How much of that can be automated? Which solutions are available to satisfy these requirements? What is the integration requirements between the various toolsets? How is this implemented?


38


2006 - 2009

Data Architecture What is the logical data requirement for architecture based on the

architecture classification framework? This might result in a logical meta-model.

What is the physical structure of the architecture repositories? What is the integration requirement to move architecture data between

repositories? How is this implemented?


39


2006 - 2009



40


2006 - 2009

Technology Architecture Where must architecture functionality and be delivered? What is the processing requirement? What is the infrastructure requirement?


41


2006 - 2009



42


2006 - 2009

Opportunities & Solutions Select the most appropriate architecture toolset Apply architecture principles in the selection Attempt to consolidate architecture artifacts into one architecture

repository


43


2006 - 2009



44


2006 - 2009

Migration Planning Plan the implementation of the architecture toolsets and repositories Take the following into consideration:

Existing architecture repositories Stakeholder priorities


45


2006 - 2009

Real IRM Approach


BuildPlan

EA Guiding Principles (FWM)

EA Conceptual Framework

(FWM)

Implemented EA Environment

(EAEA)

EA Training

EA Assessment

(EAM)

Meta-models (FWM)

Business Meta-model

Information Meta-model

Application Meta-model

Data Meta-model

Technology Meta-model

EA Definition (FWM)

EA Reporting Capability (EAEA)

Run

EA Environment Administration

(EAEA)

EA Content Management

EA Modelling

EA Reporting

EA Monitoring (EAM)

EA Office

EA Roles & Responsibilities

EA Operating Model

EA Performance Management

EA Policies & Standards

Change Leadership

EA Vision and Strategy

EA Toolset Selection (EAEA)

EA Stakeholder Analysis (FWM)

EA Change Management

46


2006 - 2009



47


2006 - 2009

Implementation Governance Confirm that the implementation is according to the agreed architecture This implementation is usually performed by the architects themselves


48


2006 - 2009



49


2006 - 2009

Architecture Change Management Implement a change management process that will result in a controlled

change environment for all the aspects of architecture, including: Architecture Roles and Responsibilities Architecture Processes Architecture Framework Architecture Meta-model Architecture Toolsets Architecture Repositories


50


2006 - 2009




Capability

People


Plan Build Run

Gove

rnan

ce

Perfo

rman

ce M

gt

Infra

stru

ctur

e Mgt

Life

cycle

Man

agem

ent

Cons

umer

Mgt

Chan

ge L

eade

rshi

p

Infrastructure

Information

Application

Method

51


2006 - 2009

growth and sustainability ofa business appropriateEA capability

quality of models perceived

usefulness of models

re-use of models

+

+

creation of quality models

maintaining ofexisting models

business need for EA products

+

+

buy industry best practice models

+

+

business need for EA solutions

+

+

+ +

satisfaction of EA customer needs

ability to package model content to specific business needs

++

operational ability to satisfy business needs

+

++

+

willingness to invest in EA capability

+

stimulation of EA customer demand

+

+

investment in EA capability

+

ability to provide EA services specific to business needs

+

+

+

+

+

positive word-of-mouth

+

+

business need for EA services

+

+

effective strategicleadership andmanagement of EAcapability

-

+

effective tactical management of EA customer requirements

+

+

+

business value realised

++

+

+

scrapping of redundant and sub-standard models

-

+

+

+

+

+

+

++

52


2006 - 2009

TOGAF 9 Capability Framework

leading enterprise architecture valueTM

Key Focus Areas

Enterprise Architecture

Strategy

Governance

April 2009

Paul van der Merwe

[email protected]

+27 82 454 7965

mailto:[email protected]

Date post:	16-May-2018
Category:	Documents
Upload:	nguyenliem
View:	287 times
Download:	18 times

TOGAFTM 9 Capability Framework - The Open...

Documents