Chapter Topics Keywords Input OutputChapter Topics Keywords Input OutputChapter Topics Keywords Input Output

ComponentsComponents

• ADM, Guidelines & Techniques (to apply ADM), Ent • ADM, Guidelines & Techniques (to apply ADM), Ent • ADM, Guidelines & Techniques (to apply ADM), Ent

Content fwk, Ent Continuum, Ref Model, Capability fwk (6 Content fwk, Ent Continuum, Ref Model, Capability fwk (6 Content fwk, Ent Continuum, Ref Model, Capability fwk (6

#s)#s)#s)

Arch Content FwkArch Content FwkArch Content Fwk

• Deliverables, Artifacts (3 Types) & BBs • ADM is Iterative, • Deliverables, Artifacts (3 Types) & BBs • ADM is Iterative,

• Provides Model of arch work products • Arch Landscape (Strategic, Segment & Capability), • Provides Model of arch work products

• Provides Open std for describing Architecture

• Arch Landscape (Strategic, Segment & Capability),

Generic to Specific, • Provides Open std for describing Architecture Generic to Specific, • Provides Open std for describing Architecture

• Includes MetaModel

Generic to Specific,

• TRM & IIIRM, • Includes MetaModel • TRM & IIIRM, • Includes MetaModel

Enterprise ContinuumComponents

• TRM & IIIRM,

• Arch Repository, Enterprise ContinuumComponents • Arch Repository, Enterprise Continuum

• Found Arch -> CSA -> Industry -> Org specific

Components • Arch Repository,

• Boundaryless Info Flow™ • Found Arch -> CSA -> Industry -> Org specific • Boundaryless Info Flow™ • Found Arch -> CSA -> Industry -> Org specific

• Made of Arch Continuum & Solutions Continuum • Arch Capability as an Operational Entity should • Made of Arch Continuum & Solutions Continuum

• Arch Cont - Defines the Architecture (Ph A,B,C & D)

• Arch Capability as an Operational Entity should

include several capabilities (no Network, IT, • Arch Cont - Defines the Architecture (Ph A,B,C & D) include several capabilities (no Network, IT, • Arch Cont - Defines the Architecture (Ph A,B,C & D)

• Sol Cont - Defines the Implementation (Phase E)

include several capabilities (no Network, IT,

Change/Release Mgmts) • Sol Cont - Defines the Implementation (Phase E) Change/Release Mgmts) • Sol Cont - Defines the Implementation (Phase E)

Reference Models

Change/Release Mgmts)

Reference ModelsReference Models

• Use TRM to define FA & IIIRM to define CSA • Use TRM to define FA & IIIRM to define CSA • Use TRM to define FA & IIIRM to define CSA

• IIIRM (Info consumer,provide,dev tools,mgmt util & • IIIRM (Info consumer,provide,dev tools,mgmt util &

brokering apps)brokering apps)brokering apps)

Capability Framework - Helps to establish Arch PracticeCapability Framework - Helps to establish Arch PracticeCapability Framework - Helps to establish Arch Practice

Provides a set of Core of TOGAF, is a process for developing EA, High Provides a set of Core of TOGAF, is a process for developing EA, High Provides a set of

• Arch Views, recommended Deliverables, method for

Core of TOGAF, is a process for developing EA, High

level deliv (ver 0.1), Detailed deliv (ver 1.0), • • Arch Views, recommended Deliverables, method for level deliv (ver 0.1), Detailed deliv (ver 1.0), •

ADM Intro

• Arch Views, recommended Deliverables, method for

managing rqmts, Guidelines on tools for Arch Dev

level deliv (ver 0.1), Detailed deliv (ver 1.0), •

Scope,Constrtains & Expectations are set in Vision, ADM Intro managing rqmts, Guidelines on tools for Arch Dev Scope,Constrtains & Expectations are set in Vision,

• 4 Dimensions of Scope (Breadth, Depth/Level, Time & • Analyze Cost, Benefits & Risk in Phase F• 4 Dimensions of Scope (Breadth, Depth/Level, Time &

Domain)

• Analyze Cost, Benefits & Risk in Phase F

• Only Phases B,C,D cycle through ViewsDomain) • Only Phases B,C,D cycle through ViewsDomain) • Only Phases B,C,D cycle through Views

• Model for structuring a repository and methods for • Model for structuring a repository and methods for • Model for structuring a repository and methods for

classifying Architecture & Solution artifactsclassifying Architecture & Solution artifactsclassifying Architecture & Solution artifacts

• It's practical implementation is Arch Repository• It's practical implementation is Arch Repository

• Aids organizing reusable Arch/Soln assets• Arch vs Soln Continuum Relationship =

• Aids organizing reusable Arch/Soln assets

• Provides common language• Arch vs Soln Continuum Relationship =

• Provides common language• Arch vs Soln Continuum Relationship =

Guidance, Direction & SupportEnt Continuum

• Provides common language

• Arch Governance decides which assent to be in this Guidance, Direction & Support

Ent Continuum • Arch Governance decides which assent to be in this Guidance, Direction & Support

• Open Group's Found Arch built using TRMEnt Continuum • Arch Governance decides which assent to be in this

• Soln Cont = Soln Inventory or Reuse Library• Open Group's Found Arch built using TRM

• Soln Cont = Soln Inventory or Reuse Library• Open Group's Found Arch built using TRM

• Open Group's CSA built using III-RM• Soln Cont = Soln Inventory or Reuse Library

Tools• Open Group's CSA built using III-RM

Tools

• Re-use, Share arch info within Org, ensure common

• Open Group's CSA built using III-RM

• Re-use, Share arch info within Org, ensure common • Re-use, Share arch info within Org, ensure common

terminology, easy maintenance of architecture, provide terminology, easy maintenance of architecture, provide terminology, easy maintenance of architecture, provide

stakeholders with relevant modelsstakeholders with relevant modelsstakeholders with relevant models

• Provides formal taxonomy to Architectural Assets• Provides formal taxonomy to Architectural AssetsTypes of Standard

• Provides formal taxonomy to Architectural Assets

• ADM has reminders when to use assets from RepoTypes of Standard

• ADM has reminders when to use assets from RepoTypes of Standard

• Legal & Regulatory, Industry & Organizational• ADM has reminders when to use assets from Repo

Contents (6 #s) • Legal & Regulatory, Industry & Organizational

Contents (6 #s)

• Metamodel - Describes Arch framework in useStandards Lifecycle

• Metamodel - Describes Arch framework in useStandards Lifecycle

• Trial, Active, Deprecated & Obsolete • Metamodel - Describes Arch framework in use

• Arch Landscape - Shows state of operating Enterprise • Trial, Active, Deprecated & Obsolete

• Arch Landscape - Shows state of operating Enterprise • Trial, Active, Deprecated & Obsolete

Classification • Arch Landscape - Shows state of operating Enterprise

in a particular point in timeClassification

in a particular point in timeClassification

• Business std - Business Funcs, Role & Actor defn, Arch Repo

in a particular point in time

• Ref Library - Contains Best Practice/Template • Business std - Business Funcs, Role & Actor defn,

Arch Repo • Ref Library - Contains Best Practice/Template • Business std - Business Funcs, Role & Actor defn,

security & governance for business activityArch Repo • Ref Library - Contains Best Practice/Template

Materials/Re-usable arch work productssecurity & governance for business activity

• Data std - Structure/Format/Origin/Ownership & Materials/Re-usable arch work products

• Standards Info Base - Defines Compliance Criteria • Data std - Structure/Format/Origin/Ownership &

• Standards Info Base - Defines Compliance Criteria • Data std - Structure/Format/Origin/Ownership &

Restriction on Replication/Access • Standards Info Base - Defines Compliance Criteria

(Specification to which Architectures should conform)Restriction on Replication/Access

(Specification to which Architectures should conform)Restriction on Replication/Access

• App std - Appln for specific business fns, App (Specification to which Architectures should conform)

• Gov Log - Results of Governance Activity • App std - Appln for specific business fns, App

• Gov Log - Results of Governance Activity • App std - Appln for specific business fns, App

communication & interoperation, Access, • Gov Log - Results of Governance Activity

• Arch Capability - Roles,Skills & Resp of EA practicecommunication & interoperation, Access,

• Arch Capability - Roles,Skills & Resp of EA practicecommunication & interoperation, Access,

Presentation & Style.Presentation & Style.

• Tech std - h/w, s/w and s/w development

• Is a checklist of o/p of each phase in building an Arch • Based on a Standard Content Metamodel that

• Is a checklist of o/p of each phase in building an Arch • Based on a Standard Content Metamodel that

defines all types of building blocks in an Arch• Is a checklist of o/p of each phase in building an Arch

• Defines structure, content of o/p & it's relationship to defines all types of building blocks in an Arch

• Defines structure, content of o/p & it's relationship to defines all types of building blocks in an Arch

• Provides Model of arch work products• Defines structure, content of o/p & it's relationship to

each other • Provides Model of arch work products

each other • Provides Model of arch work products

• Provides Open std for describing Architectureeach other

• Helps to improve TOGAF outputs by presenting them in • Provides Open std for describing Architecture

• Helps to improve TOGAF outputs by presenting them in • Provides Open std for describing Architecture

• Includes MetaModel Arch Content Fwk an consistent & structured way

• Includes MetaModel

• Artifact Types - Catalog, Matrix & DiagramsArch Content Fwk an consistent & structured way

• Deliverables - Formal Products, Contractually specified • Artifact Types - Catalog, Matrix & Diagrams

• Deliverables - Formal Products, Contractually specified • Artifact Types - Catalog, Matrix & Diagrams

• Is a companion to ADM • Deliverables - Formal Products, Contractually specified

• Artifacts - Fine grained products describing • Is a companion to ADM

• Artifacts - Fine grained products describing • Is a companion to ADM

• ADM describes what needs to be done to create • Artifacts - Fine grained products describing

Architecture from a specific viewpoint • ADM describes what needs to be done to create

Architecture from a specific viewpoint • ADM describes what needs to be done to create

an ArchitectureArchitecture from a specific viewpoint

• Build Blocks - To deliver Architecture & Solutionsan Architecture

• Build Blocks - To deliver Architecture & Solutionsan Architecture

• ACF describes what id should look like • ACF describes what id should look like

• Enables EA Tool mapping & Formalizes EA • Model describing how and with what Architecture will

• Enables EA Tool mapping & Formalizes EA • Model describing how and with what Architecture will

be described in a structured waydefinition

be described in a structured waydefinition

• Motivational - To understand Org motivation in be described in a structured way

• Core - provides min set of Arch Content to support • Motivational - To understand Org motivation in

• Core - provides min set of Arch Content to support • Motivational - To understand Org motivation in

detail and to understand & address conflicting • Core - provides min set of Arch Content to support

traceability across artifactsdetail and to understand & address conflicting

traceability across artifactsdetail and to understand & address conflicting

drivers/objectives.traceability across artifacts

It's Entities aredrivers/objectives.

It's Entities aredrivers/objectives.

• Process Modeling - used at Event driven Arch It's Entities are

• Actor-Role• Process Modeling - used at Event driven Arch

• Service Xtn is used when • Actor-Role

• App Component-Tech Component• Service Xtn is used when

• App Component-Tech Component• Service Xtn is used when

We need a common lang btwn Business & IT • App Component-Tech Component

• Business Service - Platform Service We need a common lang btwn Business & IT

TOGAF • Business Service - Platform Service

We need a common lang btwn Business & IT

IT Service misaligned with BusinessTOGAF • Business Service - Platform Service

• Organizational Unit - Function IT Service misaligned with BusinessTOGAF

Content MetaModel • Organizational Unit - Function

IT Service misaligned with Business

IT takes initial steps to talk to businessContent MetaModel • Organizational Unit - Function

• Data - Information System Service IT takes initial steps to talk to businessContent MetaModel

• Data - Information System Service IT takes initial steps to talk to business

• Infra Consol - App portfolio Rationalization• Extension - allows more specific/in-depth modeling

• Infra Consol - App portfolio Rationalization

• Data Xtn - Arch has risk with • Extension - allows more specific/in-depth modeling

• Motivational• Data Xtn - Arch has risk with

• Motivational• Data Xtn - Arch has risk with

location/mgmt/access/encap to data • Motivational

• Process Modelinglocation/mgmt/access/encap to data

• Process Modelinglocation/mgmt/access/encap to data

• Governance Xtn - To show ownership & Mgmt of • Process Modeling

• Services• Governance Xtn - To show ownership & Mgmt of

• Services• Governance Xtn - To show ownership & Mgmt of

systems and is used when • Services

• Infrastructure Consolidationsystems and is used when

• Infrastructure Consolidation

• Data Extension

systems and is used when

IT change significantly impacting Gov Models • Data Extension

IT change significantly impacting Gov Models

Rqmts of service levels diff for each service • Data Extension

• Governance Rqmts of service levels diff for each service

• Governance Rqmts of service levels diff for each service

Rqmt is to tnsfrm Org Operational Gov Practice • Governance

Rqmt is to tnsfrm Org Operational Gov Practice Rqmt is to tnsfrm Org Operational Gov Practice

Steps 6 #sSteps 6 #sSteps 6 #s

• Scope the Enterprise's Organizations getting impacted• Scope the Enterprise's Organizations getting impacted• Scope the Enterprise's Organizations getting impacted

Core Ent/Soft Ent/Xtended Ent/Communities & Gov Core Ent/Soft Ent/Xtended Ent/Communities & Gov Core Ent/Soft Ent/Xtended Ent/Communities & Gov

• Confirm Governance & support Frameworks• Confirm Governance & support Frameworks

Understand existing governance & support models. Understand existing governance & support models.

Consult with Sponsor/Stakeholders regd the impact Consult with Sponsor/Stakeholders regd the impact• Other Arch Frameworks • Organizational Model

Consult with Sponsor/Stakeholders regd the impact

• Define & Establish Enterprise Architecture Team Core Enterprise (Directly impacted)• Other Arch Frameworks • Organizational Model

• Define & Establish Enterprise Architecture Team Core Enterprise (Directly impacted)• Other Arch Frameworks

• Business & IT Strategy

• Organizational Model

• Tailored Arch Framework• Define & Establish Enterprise Architecture Team

Determine existing Ent & Bus capability

Core Enterprise (Directly impacted)

Soft Enterprise (Indirectly impacted)• Business & IT Strategy • Tailored Arch Framework

Determine existing Ent & Bus capability Soft Enterprise (Indirectly impacted)• Business & IT Strategy

• Business Principles, Goals & •

• Tailored Arch Framework

• Architecture Principles Determine existing Ent & Bus capability

Conduct BTR Assessment

Soft Enterprise (Indirectly impacted)

Principle (Name/Stmt/Rationale/Implications)• Business Principles, Goals & • • Architecture Principles

Preliminary Phase Conduct BTR Assessment Principle (Name/Stmt/Rationale/Implications)

• Business Principles, Goals & •

Drivers

• Architecture Principles

• Architecture Governance FwkPreliminary Phase Allocate key roles & responsibilities URCCS - 5 Qualities of principles

Drivers

• Governance & Legal Fwk

• Architecture Governance Fwk

• Request for Architecture Work Allocate key roles & responsibilities

Scope new Enterprise Arch Work

URCCS - 5 Qualities of principles

Fmwk Tailoring (Terminology/Process & Content)• Governance & Legal Fwk • Request for Architecture Work

Scope new Enterprise Arch Work Fmwk Tailoring (Terminology/Process & Content)• Governance & Legal Fwk

• Existing Org Model, Arch fwk,

• Request for Architecture Work

• Restated Business Principles, Goals Scope new Enterprise Arch Work

Determine constraints on Enterprise Arch Work

Fmwk Tailoring (Terminology/Process & Content)• Existing Org Model, Arch fwk, • Restated Business Principles, Goals

Determine constraints on Enterprise Arch Work• Existing Org Model, Arch fwk,

Principles & Repository

• Restated Business Principles, Goals

& Drivers Determine constraints on Enterprise Arch Work

Review with Sponsor & BoardPrinciples & Repository & Drivers

Review with Sponsor & BoardPrinciples & Repository & Drivers

Review with Sponsor & Board

Assess Budget requirements Assess Budget requirements

• Identify & Establish Architecture Principles (which • Identify & Establish Architecture Principles (which • Identify & Establish Architecture Principles (which

provide a framework for decision)provide a framework for decision)provide a framework for decision)

• Select & Tailor Architecture Framework• Select & Tailor Architecture Framework• Select & Tailor Architecture Framework

• Implement Architecture Tools (Tool Selection)• Implement Architecture Tools (Tool Selection)• Implement Architecture Tools (Tool Selection)

• Governance should be established in Prelim Phase• Governance should be established in Prelim Phase• Governance should be established in Prelim Phase

IncludesIncludes• Hierarchy of Gov Domains (Technology, IT & Arch

Includes

• Controls creation & monitoring of components & • Hierarchy of Gov Domains (Technology, IT & Arch

• Controls creation & monitoring of components & • Hierarchy of Gov Domains (Technology, IT & Arch

Governance)activities

Governance)

• COBIT - Open std, Helps to Ctrl & Measure IT activities

• Ensuring compliance with stds & regulatory obligations• COBIT - Open std, Helps to Ctrl & Measure IT

• Ensuring compliance with stds & regulatory obligations• COBIT - Open std, Helps to Ctrl & Measure IT

Resources• Ensuring compliance with stds & regulatory obligations

• Ensuring Accountability to Int & Xternal StakeholdersResources

• Ensuring Accountability to Int & Xternal StakeholdersResources

• Process, Content & Context (Arch Gov Fwk - Struc)• Ensuring Accountability to Int & Xternal Stakeholders

• Ensures Integrity & Effectiveness of Architectures• Process, Content & Context (Arch Gov Fwk - Struc)

• Ensures Integrity & Effectiveness of Architectures• Process, Content & Context (Arch Gov Fwk - Struc)

• Arch Compliance - 6 Types (Venn Diagram)• Ensures Integrity & Effectiveness of Architectures

• Integral to Ent Continuum (manages it's contents)• Arch Compliance - 6 Types (Venn Diagram)

• Integral to Ent Continuum (manages it's contents)• Arch Compliance - 6 Types (Venn Diagram)

[ Irrelevant, Consistent, Compliant, Conformant, [ Irrelevant, Consistent, Compliant, Conformant,

Fully Conformant & Non-Conformant ]Benefits

Fully Conformant & Non-Conformant ]Benefits

Fully Conformant & Non-Conformant ]Benefits

• Links process/resource/info to Org Strategy & Obj • Links process/resource/info to Org Strategy & ObjKey Success factor:

• Links process/resource/info to Org Strategy & Obj

• Enable Orgs to take full adv of digital assetsKey Success factor:

• Enable Orgs to take full adv of digital assetsKey Success factor:

Submit->Adopt->Reuse->Report ->Retire • Enable Orgs to take full adv of digital assets

• Supports Regulatory & Best Practice rqmtsSubmit->Adopt->Reuse->Report ->Retire

• Supports Regulatory & Best Practice rqmts

• Promotes visible Risk Management(Arch Policies/Procedure/Roles/Skills/Org Struct)

• Promotes visible Risk Management(Arch Policies/Procedure/Roles/Skills/Org Struct)

• Promotes visible Risk Management

Architecture BoardArchitecture BoardArchitecture Board

What it does ? What it does ?Board Value is offset by preventing one-off

What it does ?

• Oversees implementation of governance strategy Board Value is offset by preventing one-off

• Oversees implementation of governance strategy Board Value is offset by preventing one-off

solutions leading to • Oversees implementation of governance strategy

Who does it ?solutions leading to

Who does it ?

• Stakeholders responsible for Review & • High cost of dev, operation & support of

• Stakeholders responsible for Review & • High cost of dev, operation & support of

numerous environments, languages, interfaces & • Stakeholders responsible for Review &

Maintenance of Architecture (Local & Global)numerous environments, languages, interfaces &

Arch Governance Maintenance of Architecture (Local & Global)numerous environments, languages, interfaces &

protocolsArch Governance Maintenance of Architecture (Local & Global)

How it does ?protocols

Arch Governance

How it does ?protocols

• Difficulty in replicating & re-using solutions How it does ?

• Responsibilities & Decision making capabilities • Difficulty in replicating & re-using solutions

• Responsibilities & Decision making capabilities • Difficulty in replicating & re-using solutions

• Remit [Legal Mandates] and Authority Limits • Remit [Legal Mandates] and Authority Limits

Architecture ComplianceArchitecture Compliance

• Prepare Project Impact Assessments - project views • Prepare Project Impact Assessments - project views

illustrating how EA impact a projectillustrating how EA impact a projectillustrating how EA impact a project

• Perform Architecture Compliance Review • Perform Architecture Compliance Review • Perform Architecture Compliance Review

Architecture Compliance Review Architecture Contracts - Btwn Development Architecture Compliance Review Architecture Contracts - Btwn Development Architecture Compliance Review

• Catch Errors early

Architecture Contracts - Btwn Development

partners & sponsors on deliverables, quality & • Catch Errors early

• Ensure application of Best Practices

partners & sponsors on deliverables, quality &

fitness-for-purpose of Architecture • Ensure application of Best Practices fitness-for-purpose of Architecture • Ensure application of Best Practices

• Provide overview of Standards/Compliance

fitness-for-purpose of Architecture

• Provide overview of Standards/Compliance • Provide overview of Standards/Compliance

• Identify Standards which require modification It's usage ensures • Identify Standards which require modification It's usage ensuresArchitecture Contract - Phase A o/p

• Identify Standards which require modification

• Identify app specific services that could be part of

It's usage ensures

• To check Integrity, Changes, Decision Making & Architecture Contract - Phase A o/p

• Identify app specific services that could be part of • To check Integrity, Changes, Decision Making & Architecture Contract - Phase A o/p

• Identify app specific services that could be part of

Enterprise Infra

• To check Integrity, Changes, Decision Making &

AuditEnterprise Infra

• Document strategies for mult arch team collab..etc

Audit

• Adherence to principles, stds & rqmts • Document strategies for mult arch team collab..etc • Adherence to principles, stds & rqmts • Document strategies for mult arch team collab..etc

• Take advantage of advances in Technology

• Adherence to principles, stds & rqmts

• Risk identification • Take advantage of advances in Technology • Risk identification • Take advantage of advances in Technology

• Identify key criteria for procurement

• Risk identification

• Accountability, Responsibility & Discipline • Identify key criteria for procurement • Accountability, Responsibility & Discipline • Identify key criteria for procurement

• Identify significant Arch Gaps to product vendors

• Accountability, Responsibility & Discipline

• Identify significant Arch Gaps to product vendors

Establishing Architecture CapabilityEstablishing Architecture Capability

• TOGAF provides guidelines for this • TOGAF provides guidelines for this • TOGAF provides guidelines for this

• Address the 4 domain architectures • Address the 4 domain architectures • Address the 4 domain architectures

• Phase A - prominently used• Phase A - prominently usedSMART - Good Business Scenario

• Phase A - prominently used

• Phase B - Iteratively usedSMART - Good Business Scenario

• Phase B - Iteratively usedSMART - Good Business Scenario

• Phase B - Iteratively used

• Helps to identify business rqmts that the Arch • Helps to identify business rqmts that the Arch If Business Scenarios NOT available,

development must addressIf Business Scenarios NOT available,

• Requirements might not be completedevelopment must address

• Contributed By: Business Mgmt,IT Vendor & Architect • Requirements might not be complete

• Contributed By: Business Mgmt,IT Vendor & Architect • Requirements might not be complete

• Business value to solution might not be clear• Contributed By: Business Mgmt,IT Vendor & Architect

• Business value to solution might not be clear • Business value to solution might not be clear

• Relevance of potential solutions will be unclearDeveloping a Business Scenario ( 7 Steps)

• Relevance of potential solutions will be unclearDeveloping a Business Scenario ( 7 Steps)

• Relevance of potential solutions will be unclearDeveloping a Business Scenario ( 7 Steps)

• Identify, document & Rank the PROBLEM • Identify, document & Rank the PROBLEM

• Identify Buss/Tech ENVIRONMENT of the scenarioUsed to communicate with stakeholders & vendor

• Identify Buss/Tech ENVIRONMENT of the scenarioUsed to communicate with stakeholders & vendor

• Identify Buss/Tech ENVIRONMENT of the scenario

• Identify desired OBJECTIVE & result for success • Identify desired OBJECTIVE & result for successGetting it right

• Identify desired OBJECTIVE & result for success

• Identify HUMAN ACTORS & their place in business Getting it right

• Identify HUMAN ACTORS & their place in business Getting it right

• Customers KNOW what they want • Identify HUMAN ACTORS & their place in business

model • Customers KNOW what they want

model • Customers KNOW what they want

They don't write it, esp linkage to businessmodel

• Identify COMPUTING ELEMENTS & their place in They don't write it, esp linkage to business

• Identify COMPUTING ELEMENTS & their place in

technology model • Customers DON'T KNOW what they want

technology model • Customers DON'T KNOW what they want

Observe & Probe to discover the needBusiness Scenarios technology model

• Identify ROLES,RESPONSIBILITIES & METRICS for Observe & Probe to discover the need

Business Scenarios

• Identify ROLES,RESPONSIBILITIES & METRICS for Observe & Probe to discover the need

Bring out critical business rules • Identify ROLES,RESPONSIBILITIES & METRICS for

success Bring out critical business rules

success Bring out critical business rules

Focus on 'What' and not 'How'success

• Check for fitness-for-purpose & REDEFINE Focus on 'What' and not 'How'

• Check for fitness-for-purpose & REDEFINE Focus on 'What' and not 'How'

Business Scenario ModelsBusiness Scenario ModelsBusiness Scenario Models

• Capture Business & Technology views graphically Template: • Capture Business & Technology views graphically

• Relate Actors & Interactions

Template:

• Problem Description • Relate Actors & Interactions • Problem Description • Relate Actors & Interactions • Problem Description

• Detailed Objective • Detailed Objective

Business Scenario Description

• Detailed Objective

• View of EnvironmentBusiness Scenario Description • View of EnvironmentBusiness Scenario Description

• Critical steps between actors in right sequence

• View of Environment

• Actors & their roles/responsibilities • Critical steps between actors in right sequence • Actors & their roles/responsibilities • Critical steps between actors in right sequence

• Partition responsibility of actors

• Actors & their roles/responsibilities

• Principles & Business Constraints • Partition responsibility of actors

• List Pre-Condition for proper sys functionality

• Principles & Business Constraints

• Requirements • List Pre-Condition for proper sys functionality • Requirements • List Pre-Condition for proper sys functionality

• Provide Tech requirement to ensure service quality is

• Requirements

• Next Steps • Provide Tech requirement to ensure service quality is • Next Steps • Provide Tech requirement to ensure service quality is

acceptable

• Next Steps

acceptableacceptable

• Used in 'Phase A' to identify Key Players & • Used in 'Phase A' to identify Key Players & • Used in 'Phase A' to identify Key Players &

updated throughout each Phaseupdated throughout each Phaseupdated throughout each Phase

• Stakeholders - Have Key Roles in or Concerns

TOGAF Technique: ( 4 Steps )

• Stakeholders - Have Key Roles in or Concerns

about the Enterprise Architecture.Impacted by EA TOGAF Technique: ( 4 Steps ) about the Enterprise Architecture.Impacted by EA TOGAF Technique: ( 4 Steps )

• Identify Stakeholders

about the Enterprise Architecture.Impacted by EA

project • Identify Stakeholders project • Identify Stakeholders

• Classify & Record their positions in Stakeholder

project

• Classify & Record their positions in Stakeholder • Classify & Record their positions in Stakeholder

Analysis Matrix Benefits: Stakeholder Mgmt

Analysis Matrix Benefits: Stakeholder Mgmt

Analysis Matrix

• Determine approach (Power-Interest Matrix)

Benefits:

• Identifies powerful stakeholders & ensures their • Determine approach (Power-Interest Matrix)

• Tailor Engagement deliverables (Stakeholder Map)

• Identifies powerful stakeholders & ensures their

input shapes the architecture • Tailor Engagement deliverables (Stakeholder Map) input shapes the architecture • Tailor Engagement deliverables (Stakeholder Map)

(choose specific viewpoints to address their specific

input shapes the architecture

• Achieve their support to get necessary resource (choose specific viewpoints to address their specific • Achieve their support to get necessary resource (choose specific viewpoints to address their specific

stakeholder groups)

• Achieve their support to get necessary resource

• Helps them to understand Arch Processstakeholder groups) • Helps them to understand Arch Processstakeholder groups) • Helps them to understand Arch Process

• Anticipate likely reactions and able to address • Anticipate likely reactions and able to address

• Identify conflicting/competing objectives & • Identify conflicting/competing objectives &

addressaddressaddress

View - WHAT YOU SEE (Specific to the Architecture)View - WHAT YOU SEE (Specific to the Architecture)View - WHAT YOU SEE (Specific to the Architecture)

ViewPoint - FROM WHERE YOU SEE (Generic) ViewPoint - FROM WHERE YOU SEE (Generic) ViewPoint - FROM WHERE YOU SEE (Generic)

Architects Responsibility in developing Views:Architects Responsibility in developing Views:

Ensure Completeness System - Collection of components organized to Ensure Completeness System - Collection of components organized to Ensure Completeness

• Does it address all concerns of Arch Stakeholders

System - Collection of components organized to

accomplish a specific function or set of functions • Does it address all concerns of Arch Stakeholders accomplish a specific function or set of functions • Does it address all concerns of Arch Stakeholders

Integrity of the Architecture

accomplish a specific function or set of functions

Stakeholders - Have Key Roles or Key Concerns Integrity of the Architecture Stakeholders - Have Key Roles or Key Concerns Integrity of the Architecture

• Can views be connected to each other

Stakeholders - Have Key Roles or Key Concerns

Concerns - Key Interest that are crucial to • Can views be connected to each other

• Can the conflicting concerns be reconciled

Concerns - Key Interest that are crucial to

Stakeholders. Determines 'SYSTEM ACCEPTABILITY' • Can the conflicting concerns be reconciled Stakeholders. Determines 'SYSTEM ACCEPTABILITY' • Can the conflicting concerns be reconciled

• What trade-offs were made

Stakeholders. Determines 'SYSTEM ACCEPTABILITY'

View - Representation of a System from perspective • What trade-offs were made View - Representation of a System from perspective • What trade-offs were made View - Representation of a System from perspective

of related set of concernsof related set of concerns

View creation process

of related set of concerns

ViewPoint - Perspective from which view is takenViews & ViewPoints View creation process ViewPoint - Perspective from which view is takenViews & ViewPoints View creation process

• Refer for existing views in Library of Viewpoints

ViewPoint - Perspective from which view is takenViews & ViewPoints

• Refer for existing views in Library of Viewpoints

• Select Key Stakeholders • Select Key Stakeholders • Select Key Stakeholders

• Analyze their concerns & document them • Analyze their concerns & document them • Analyze their concerns & document them

• Select appropriate Viewpoints • Select appropriate Viewpoints • Select appropriate Viewpoints

• Generate views of the system using ViewPoints as • Generate views of the system using ViewPoints as

templatestemplates

3 Classes of Viewpoints are:3 Classes of Viewpoints are:

TOGAF includes example artifacts (Catalog/Matrix & TOGAF includes example artifacts (Catalog/Matrix &

Catalog - Lists BBs of similar/related types

TOGAF includes example artifacts (Catalog/Matrix &

Diagrams), which can be adopted/enhanced & Catalog - Lists BBs of similar/related types Diagrams), which can be adopted/enhanced & Catalog - Lists BBs of similar/related types

Matrix - Shows relationship between BBs

Diagrams), which can be adopted/enhanced &

combined to produce viewsMatrix - Shows relationship between BBs combined to produce viewsMatrix - Shows relationship between BBs

Diagram - Pic rep of BBs for Stakeholder Communication

combined to produce views

Diagram - Pic rep of BBs for Stakeholder CommunicationDiagram - Pic rep of BBs for Stakeholder Communication

Basic CharacteristicsBasic CharacteristicsBasic Characteristics

• Package of functionality to meet Business Needs • Package of functionality to meet Business Needs

• Has an interface to access it's functionality • Has an interface to access it's functionality • Has an interface to access it's functionality

• Inter-Operates & Inter-Dependent with other BBs • Inter-Operates & Inter-Dependent with other BBs • Inter-Operates & Inter-Dependent with other BBs

Good CharacteristicsGood CharacteristicsGood Characteristics

• Evolves to exploit Technology & Standards • Evolves to exploit Technology & Standards

• Assembled from a sub-assembly of other BBs • Assembled from a sub-assembly of other BBs

• Is Re-Usable & Replicable • Is Re-Usable & Replicable

Building Blocks

• Is Re-Usable & Replicable

Building BlocksGrouped at Functional Level - ABB

Building Blocks

Principles AppliedGrouped at Functional Level - ABB

Principles AppliedGrouped at Functional Level - ABB

Defined during Phases A,B,C & DPrinciples Applied

• Only required service's BB should be in ArchitectureDefined during Phases A,B,C & D

• Only required service's BB should be in Architecture

• Implements 1 or more or partial service • Implements 1 or more or partial serviceProducts or Custom Developments - SBB

• Implements 1 or more or partial service

• Should conform to StandardsProducts or Custom Developments - SBB

• Should conform to StandardsProducts or Custom Developments - SBB

• Should conform to Standards

PatternsPatternsPatterns

• Reusable Design solution to recurring Design problems • Reusable Design solution to recurring Design problems

• Tells how to use BBs, when, why and trade-offs made • Tells how to use BBs, when, why and trade-offs made • Tells how to use BBs, when, why and trade-offs made

Determination of Interoperability occurs in ALL Determination of Interoperability occurs in ALL Determination of Interoperability occurs in ALL

PhasesPhasesPhases

Degree of InteropManaging Interoperatability Requirements

Degree of InteropManaging Interoperatability Requirements

Degree of Interop

• Lev 1 - Unstructured DataManaging Interoperatability Requirements

• Interop - Ability to share SERVICE & INFORMATION • Lev 1 - Unstructured Data

• Interop - Ability to share SERVICE & INFORMATION • Lev 1 - Unstructured Data

• Lev 2 - Structured Data • Interop - Ability to share SERVICE & INFORMATION

• TOGAF provides technique for Define/Refine & • Lev 2 - Structured Data

• TOGAF provides technique for Define/Refine & • Lev 2 - Structured Data

• Lev 3 - Seamless Data • TOGAF provides technique for Define/Refine &

Determine interop requirements • Lev 3 - Seamless Data

Determine interop requirements • Lev 3 - Seamless Data

• Lev 4 - Seamless Info • Lev 4 - Seamless Info

Type of Info exchangedArchitect must ensure that there is NO interop conflicts

Type of Info exchangedArchitect must ensure that there is NO interop conflicts

Type of Info exchanged

• A - Formal MessageArchitect must ensure that there is NO interop conflicts

• A - Formal Message • A - Formal Message

• B - Common Message • B - Common Message • B - Common Message

• C - Complete Message • C - Complete Message

• D - Real-time Message • D - Real-time Message

Business Transformation Readiness AssessmentBusiness Transformation Readiness Assessment

• To understand Readiness of Organization for changes • To understand Readiness of Organization for changes • To understand Readiness of Organization for changes

caused by EA programcaused by EA programcaused by EA program

• Identify issues • Identify issuesInitial BTR Assessment in Phase A

• Identify issues

• Deal with issues during Phase E & FInitial BTR Assessment in Phase A

• Deal with issues during Phase E & FAddress issues during Phase E & FAddress issues during Phase E & F

Activities are:Activities are:Activities are:

• Determine the readiness factors • Determine the readiness factors • Determine the readiness factors

• Present them using Maturity Models • Present them using Maturity Models • Present them using Maturity Models

• Assess them and Determine ratings • Assess them and Determine ratings

• Assess risk on each factor & Identify Mitigation plan • Assess risk on each factor & Identify Mitigation plan • Assess risk on each factor & Identify Mitigation plan

• Work these Mitigation plans during Phase E & F • Work these Mitigation plans during Phase E & F • Work these Mitigation plans during Phase E & F

Risk Management activities Risk Management is done along with BTRARisk Management activities Risk Management is done along with BTRARisk Management activities

• Classification -> Identification -> Initial Assessment ->

Risk Management is done along with BTRA

Risk Identification is done in Phase A • Classification -> Identification -> Initial Assessment -> Risk Identification is done in Phase A • Classification -> Identification -> Initial Assessment ->

Mitigation & Residual Risk Assessment -> Monitoring

Risk Identification is done in Phase A

Risk Monitoring done in Phase GMitigation & Residual Risk Assessment -> Monitoring Risk Monitoring done in Phase G

Classification on Effect Initial Level - Risk categorization prior identifying Classification on Effect Initial Level - Risk categorization prior identifying Classification on Effect

• Catastrophic - Result in Bankruptcy

Initial Level - Risk categorization prior identifying

Mitigation Plan • Catastrophic - Result in Bankruptcy Mitigation Plan • Catastrophic - Result in Bankruptcy

• Critical - Financial Loss, No ROI in more than one

Mitigation Plan

Residue Level - Risk categorization after • Critical - Financial Loss, No ROI in more than one Residue Level - Risk categorization after • Critical - Financial Loss, No ROI in more than one

Line of Business

Residue Level - Risk categorization after

implementing Mitigation PlanLine of Business implementing Mitigation Plan

• Marginal - Financial Loss, Less ROI in one Line of • Marginal - Financial Loss, Less ROI in one Line of

Business Assessment of Effect & Frequency combined:Business Assessment of Effect & Frequency combined:Business

• Negligible - Minimal impact on services

Assessment of Effect & Frequency combined:

• Negligible - Minimal impact on services • Negligible - Minimal impact on services

Extremely High Risk - Most Likely fail with severe Extremely High Risk - Most Likely fail with severe

Classification on Frequency

Extremely High Risk - Most Likely fail with severe

consequencesClassification on Frequency

• Frequent - very often or continuously

consequences

High Risk - Significant failure resulting in certain • Frequent - very often or continuously High Risk - Significant failure resulting in certain • Frequent - very often or continuously

• Likely - occurs several times

High Risk - Significant failure resulting in certain

goals not achieved • Likely - occurs several times goals not achieved • Likely - occurs several times

• Occasional - occurs sporadically

goals not achieved

Moderate Risk - Noticeable failure threaten success • Occasional - occurs sporadically Moderate Risk - Noticeable failure threaten success • Occasional - occurs sporadically

• Seldom - remote possibility, not more than once

Moderate Risk - Noticeable failure threaten success

of some goals • Seldom - remote possibility, not more than once of some goals • Seldom - remote possibility, not more than once

• Unlikely - probably not occur

of some goals

Low Risk - Some goals will not be wholly success • Unlikely - probably not occur Low Risk - Some goals will not be wholly success

Capability Based PlanningCapability Based Planning

• Focuses on Engineering, Developing & Delivering • Focuses on Engineering, Developing & Delivering

Strategic Business CapabilitiesStrategic Business CapabilitiesStrategic Business Capabilities

• Capabilities = Derived from Corporate Strategic Plan • Capabilities = Derived from Corporate Strategic Plan • Capabilities = Derived from Corporate Strategic Plan

• All of Architecture will be expressed in terms of • All of Architecture will be expressed in terms of • All of Architecture will be expressed in terms of

Business Outcome & Value

Phase A defines Phase A defines Phase A defines

• What is In & Out of Arch work • Request for Arch Work • What is In & Out of Arch work • Request for Arch Work • What is In & Out of Arch work

• Constraints (via Principles, Goals & Drivers)

• Request for Arch Work

• Buss Principle,Goal & Driver • Approved Stmt of Arch WorkObjective:

• Constraints (via Principles, Goals & Drivers) • Buss Principle,Goal & Driver

• Org Model for EA

• Approved Stmt of Arch Work

• Refined Buss Principle,Goal&DriverObjective:

• Develop high level aspirational vision of Capabilities & • Org Model for EA • Refined Buss Principle,Goal&Driver

• Develop high level aspirational vision of Capabilities & Business Scenario technique can be used to develop

• Org Model for EA

• Tailored Arch Framework

• Refined Buss Principle,Goal&Driver

• Capability Assessment • Develop high level aspirational vision of Capabilities &

Business Value to be delivered as result of EA programBusiness Scenario technique can be used to develop • Tailored Arch Framework • Capability Assessment

Business Value to be delivered as result of EA programBusiness Scenario technique can be used to develop

Arch Vision

• Tailored Arch Framework

• Architecture Principles

• Capability Assessment

• Communications PlanBusiness Value to be delivered as result of EA program

• Get Approval for a 'Statement of Arch Work' Arch Vision • Architecture Principles • Communications Plan

• Get Approval for a 'Statement of Arch Work' Arch Vision • Architecture Principles

• Populated Arch Repo

• Communications Plan

• Additional content in Arch Repo • Get Approval for a 'Statement of Arch Work'

• Populated Arch Repo • Additional content in Arch Repo

11 Steps:11 Steps:11 Steps:

1. Establish the Project1. Establish the Project1. Establish the Project

• Conduct procedures to secure recognition • Conduct procedures to secure recognition

• Endorsement of Corp Mgmt • Endorsement of Corp Mgmt • Endorsement of Corp Mgmt

• Support & Commitment of Line Mgmt • Support & Commitment of Line Mgmt • Support & Commitment of Line Mgmt

• Refer other frameworks to how this proj relates • Refer other frameworks to how this proj relates • Refer other frameworks to how this proj relates

2. Identify Stakeholders, Concerns & Buss Rqmts2. Identify Stakeholders, Concerns & Buss Rqmts

• Identify stakeholders, their roles & responsibilities • Identify stakeholders, their roles & responsibilities

• Identify Concerns & ViewPoints relevant to project • Identify Concerns & ViewPoints relevant to project • Identify Concerns & ViewPoints relevant to project

• Stakeholder Map Matrix is developed • Stakeholder Map Matrix is developed • Stakeholder Map Matrix is developed

3. Confirm Business Goals, Drivers & Constraints3. Confirm Business Goals, Drivers & Constraints3. Confirm Business Goals, Drivers & Constraints

• Identify Buss Goals & Strategic Drivers • Identify Buss Goals & Strategic Drivers

• If existing, check it's currentness & clarify ambiguity • If existing, check it's currentness & clarify ambiguity

• Define 'Business' constraints that must be dealt • Define 'Business' constraints that must be dealt • Define 'Business' constraints that must be dealt

4. Evaluate Business Capabilities4. Evaluate Business Capabilities4. Evaluate Business Capabilities

• Understand existing capabilities & desires of Buss • Understand existing capabilities & desires of Buss • Understand existing capabilities & desires of Buss

• Find ways to realize those capabilities • Find ways to realize those capabilities

• Assess if Org has competency to build this • Assess if Org has competency to build this

• Create initial picture of required new capability • Create initial picture of required new capability • Create initial picture of required new capability

5. Business Transformation Readiness Assessment5. Business Transformation Readiness Assessment5. Business Transformation Readiness Assessment

• Determination & Rating of Readiness Factors • Determination & Rating of Readiness Factors

• Results used • Results used

• Shape the Scope of Architecture • Shape the Scope of Architecture • Shape the Scope of Architecture

• Identify activities rqd within Arch Project • Identify activities rqd within Arch Project • Identify activities rqd within Arch Project

• Identify Risk areas to be addressed • Identify Risk areas to be addressed • Identify Risk areas to be addressed

6. Define the Scope6. Define the Scope

• Breadth of Coverage, Level of Detail • Breadth of Coverage, Level of Detail • Breadth of Coverage, Level of Detail

• Domains to be covered, Partitioning Characteristics High Level definition = Version # 0.1 • Domains to be covered, Partitioning Characteristics High Level definition = Version # 0.1 • Domains to be covered, Partitioning Characteristics

7. Confirm & Elaborate Arch & Buss Principles

High Level definition = Version # 0.1

Detailed Level of definition - Version # 1.07. Confirm & Elaborate Arch & Buss Principles Detailed Level of definition - Version # 1.07. Confirm & Elaborate Arch & Buss Principles

• Ensure existing definitions are current

Detailed Level of definition - Version # 1.0

• Ensure existing definitions are current

• Clarify Ambiguity • Clarify Ambiguity

• Secure Mgmt Endorsement • Secure Mgmt Endorsement • Secure Mgmt Endorsement

8. Develop Architecture Vision8. Develop Architecture Vision8. Develop Architecture Vision

• Create high-level view of Baseline & Target Arch • Create high-level view of Baseline & Target Arch • Create high-level view of Baseline & Target Arch

• Buss Scenarios are useful here to find Buss Rqmts • Buss Scenarios are useful here to find Buss Rqmts

• Result is high level definition of Baseline & Target • Result is high level definition of Baseline & Target

EnvironmentsEnvironmentsEnvironments

9. Define Target Arch 'Value Prop' and 'KPI's9. Define Target Arch 'Value Prop' and 'KPI's9. Define Target Arch 'Value Prop' and 'KPI's

• Develop 'Business Case' with ROI • Develop 'Business Case' with ROI • Develop 'Business Case' with ROI

• Produce 'Value Proposition' for each Stakeholder • Produce 'Value Proposition' for each Stakeholder • Produce 'Value Proposition' for each Stakeholder

GroupsGroupsGroups

• Assess & Define 'Procurement Requirements' • Assess & Define 'Procurement Requirements'

• Review & Agree 'Value Props' with Sponsor & • Review & Agree 'Value Props' with Sponsor & • Review & Agree 'Value Props' with Sponsor &

StakeholdersStakeholdersStakeholders

• Define 'Performance Metrics' • Define 'Performance Metrics' • Define 'Performance Metrics'

• Assess Business Risk • Assess Business Risk

• Incorporate o/p in 'Statement of Arch Work' • Incorporate o/p in 'Statement of Arch Work'

10. Identify BTRA Risks & Mitigation Activities10. Identify BTRA Risks & Mitigation Activities10. Identify BTRA Risks & Mitigation Activities

• Identify risks with vision • Identify risks with vision • Identify risks with vision

• Assess initial level of risk & frequency • Assess initial level of risk & frequency • Assess initial level of risk & frequency

• Assign mitigation strategy for each risk • Assign mitigation strategy for each risk

• Include them all in 'Statement of Arch Work' • Include them all in 'Statement of Arch Work' • Include them all in 'Statement of Arch Work'

11. Develop 'Statement of Arch Work' & Approval11. Develop 'Statement of Arch Work' & Approval

• Assess & Estimate 'Resource Requirements' • Assess & Estimate 'Resource Requirements' • Assess & Estimate 'Resource Requirements'

• Develop Roadmap & Schedule for the proposed • Develop Roadmap & Schedule for the proposed • Develop Roadmap & Schedule for the proposed

developmentdevelopmentdevelopment

• Define Performance Metrics • Define Performance Metrics

• Develop 'Communications Plan' • Develop 'Communications Plan'

• Review & Agree plan with Sponsor & Stakeholders • Review & Agree plan with Sponsor & Stakeholders • Review & Agree plan with Sponsor & Stakeholders

• Gain Sponsor Sign-Off • Gain Sponsor Sign-Off • Gain Sponsor Sign-Off