Can togaf™ assist_implementation_of_fea_fsam_12_jul10

Improving Government Enterprise Architecture Process
Through Industry Best Practice –

Can TOGAF™ Assist Implementation of FEA/FSAM?

Presented by
John Polgreen, Ph.D.
Architecting the Enterprise

Architecting the Enterprise Limited Copyright © 2010

Welcome!


Agenda

 Introductions
 Presentation
 TOGAF for Government
 Strategic Process
 Segment and Capability Process
 TOGAF Value Proposition
 Panel Discussion / Q&A


The Situation

 FEA has well defined reference architectures
 OMB, CIO Council has provided guidance on process
 FSAM provides guidance for segment architectures

But architects need…
 More granular process information
 More templates, examples of outputs
 Common language


A Potential Solution

Augment Practice Guidance, FEA, FSAM with TOGAF

 TOGAF ADM is a well defined process
 Templates and formats for outputs available
 Accepted globally – provides common language
 Popular EA tools have FEA and TOGAF modules
 TOGAF maps well to FEA, FSAM and FEA Guidance
 TOGAF is meant to to be tailored – don’t throw anything away
 TOGAF ADM can also map to DoDAF


TOGAF 9

 The Open Group Architectural Framework, v 9
 Developed by consensus in The Open Group
 Federal roots - DoD’s TAFIM
 Architecture Development Method is well proven
 80% of Fortune 50 use TOGAF
 Wide public sector use
 UK Government
 New York State
 Well accepted among Federal contractors


TOGAF ADM
Preliminary

Recommended Approach
 Establish EA program A
 Conduct ADM projects Vision

 Manage requirements H B
 Phases are iterative Change
Business
Management

G Requirements
Management C
Implementation
Governance Information

F D
Migration
Technology
Planning
E
Opportunities
and Solutions

Each Phase is Made Up of Steps

Select Reference Models, Viewpoints

Develop Baseline Description

Develop Target Description
Preliminary

Perform Gap Analysis
A
Define Roadmap Components
H B
Business Resolve Impacts

Conduct Stakeholder Review
G Requirements
C Finalize the Architecture
Management

Create Architecture Definition Document

F D
E Each step is described in detail


Taxonomy of
Artifacts
part of the
Content
Framework


FEA Reference Architectures
Approach
Business-Driven

Performance Reference Model (PRM)

Architecture
Component-Based
Business Reference Model (BRM)
Service Component Reference Model (SRM)
Data Reference Model (DRM)
Technical Reference Model (TRM)


Mapping FEA Practice Guidance to the TOGAF ADM

ADM Phases ADM Phase ADM Phases
Preliminary E – Opportunities and F- Migration
A – Vision Solutions G – Implementation
B – Business Architecture Governance
C – Information Architecture H – Change
D – Technology Architecture Management
Requirements Management


EA Process Guidance

FEA Practice Guidance – “does not cover enterprise architecture (EA)
development and maintenance since there is already a broad body of
knowledge on these topics.”

 TOGAF – Hundreds of pages EA design and implementation
 Example - ADM Business Architecture Phase
 9 major steps, many with sub-steps
 21 described artifacts
 Based on industry best practice worldwide


USDA Case Study Conclusions

“TOGAF and the FEA provided a good combination for planning a large
government-based modernization project.”

“TOGAF’s ADM is an excellent complement to RUP, as it addresses the
development and maintenance of an Enterprise Architecture and provides
key inputs to a RUP based, project-level plan.”

Greg Lettow, Jim Odrowski


Applying TOGAF to FEA/FSAM

Strategic Architecture
 Strategic ADM iteration
 Tailor FEA reference models Preliminary

A

 Develop strategic architecture H
Architecture
Change
Management
Architecture
Vision
B
Business
Architecture

 Mile wide, inch deep Segment Architecture(s) G
Requirements
CC
Information
Information
System
Implementation System
Management Architectures
Governance Architectures

 To-be states in all domains
Preliminary F D

 Gaps Preliminary
Preliminary
Migration
Planning E
Opportunities
Technology
Architecture

A & Solutions
Architecture

 Transition Strategy H
Architecture
Change
H
Architecture
Management H
Vision
A
Architecture
Vision
A B
Architecture BusinessB
Vision Architecture
Change
Architecture Business B
Management Architecture

 Subsequent ADM iterations
Change Business
Management C
Architecture
C
G Information
Information
C
Requirements System C
Implementation
G
Governance
Implementation
G
Management
Requirements
System
Information
Architectures C
Information
Architectures C
System
Information
System
Information
Capability Architectures
Management
Requirements Architectures
Governance System
Architectures

 Describe segments
F D
Migration Technology
F D
Planning Architecture Preliminary
Migration
F E TechnologyD

 Describe other enterprise projects Migration Opportunities
Planning Architecture
Technology Preliminary
E
Planning & Solutions Architecture Preliminary
Opportunities
E
& Solutions
Opportunities A
& Solutions Architecture
H A
Vision

 Collectively describe rich EA
Architecture Architecture
A B
H
Change Vision
Architecture Business
Architecture
H B
Management
Change Vision Architecture
Business
Architecture B
Management
Change Architecture
Business
Management C
Architecture
C
G Information
Information
C
Implementation
Requirements System C
System
Information
G
Governance
Management
Requirements Architectures C
Information
Architectures C
Information
System
G Management Information
Governance Requirements Architectures
System
Architectures
F D
Migration TechnologyD
F
Planning E Architecture
Technology
Migration
F D
Migration Opportunities
Planning E Architecture
Technology
Planning & Solutions E
Opportunities Architecture
& Solutions
Opportunities
& Solutions


Strategic Iteration of TOGAF ADM for FEA

Preliminary

A Preliminary Phase
• Establish EA Program
• Define Principles
H B • Define Framework
• Define, Prioritize Segments
• Choose Tools
• Develop Governance
• Obtain Approval

G Requirements
Management C

F D
E


Preliminary

Architecture Vision
• Establish Project
A • Identify Stakeholders
• Define Scope
H B • Define Vision
• Obtain Sponsor Approval

G Requirements C
Management

F D
E


Preliminary

A Business Architecture
• Define Agency PRM
• Define Agency BRM
H B • Populate As-is BRM
• Populate To-be BRM
• Conduct Gap Analysis
• Conduct Impact Analysis
• Populate PRM Indicators

G Requirements C
Management

F D
E


Preliminary

A
H B
Information Systems
Architecture
• Define Agency SRM
• Populate As-is SRM
G Requirements C • Populate To-be SRM
Management • Conduct Gap Analysis
• Define Agency DRM
• Populate As-is DRM
• Populate To-be DRM
F D • Conduct Impact Analysis
E


Preliminary

A
H B

G Requirements
Management C
Technology Architecture
• Define Agency TRM
• Populate As-is TRM
• Populate To-be TRM
F D • Conduct Impact Analysis
E


Preliminary

A
H B

G Requirements C
Management

Opportunities and Solutions
• Review gap analyses
• Create Line of Sight
• Identify solutions
F D • Identify buy/build options
• Identify portfolio options
E • Define funding strategy


Preliminary

A
H B

G Requirements C
Management
Migration Planning
• Project Impact Analysis
• Costs
• Benefits
• Value
• Risks F D
• Transition Strategy
E


Preliminary

A

Implementation Governance
H B
• Not done for initial iteration

G Requirements C
Management

F D
E


Preliminary

Architecture Change Mgt
• Not done for initial iteration
A
H B

G Requirements C
Management

F D
E


Preliminary

A
H B
• All phases input, revise, output
• Enter into repository
• Evaluate traceability

G Requirements C
Management

F D
E


Subsequent ADM iterations

 Describe segments – use
 FSAM
 TOGAF
 FSAM Tailored with TOGAF
 Describe other enterprise significant projects
 Collectively describe rich EA


FSAM to TOGAF ADM Mapping
Phase A
Vision Phase B
Business
Architecture
Phases C-D
Data,
Application,
Technology Phases E-F
Architectures Opportunities
and Solution,
Migration
Planning

2 TOGAF ADM Phase FSAM Step

Subsequent Iterations of ADM for the FEA

Preliminary

Preliminary Phase
A • Validate previous iteration

H B

G Requirements C
Management

F D
E


Preliminary

Architecture Vision
• Establish Project
• Identify Stakeholders
A • Identify Risks
• Define Scope, including
H B • Segments
• Cross agency initiatives
• Define Vision
• Plan Communications
• Obtain Approval

G Requirements C
Management

F D
E


Preliminary

A Business Architecture
• Populate As-is BRM
H B • Populate To-be BRM

G Requirements C
Management

F D
E


Preliminary

A
H B

Information Systems
Architecture
• Populate As-is SRM
• Populate To-be SRM
G Requirements C • Conduct Gap Analysis
Management
• Populate As-is DRM
• Populate To-be DRM
F D • Populate PRM Indicators

E


Preliminary

A
H B

G Requirements C
Management
Technology Architecture
• Populate As-is TRM
• Populate To-be TRM
F D • Populate PRM Indicators

E


Preliminary

A
H B

G Requirements C
Management
Opportunities and Solutions
• Review gap analyses
• Create Line of Sight
• Identify solutions
• Make reuse/buy/build decisions
F D • Make portfolio decisions
• Create business case
E • Define funding strategy



Preliminary

A
H B

G Requirements C
Management
Migration Planning
• Project Impact Analysis
• Costs
• Benefits
• Value
• Risks F D
• Migration Plan
E


Preliminary

A

Implementation Governance
H B
• Establish Contracts
• Launch implementation
• Conduct compliance reviews
• Measure performance

G Requirements C
Management

F D
E


Preliminary

Architecture Change
Management A
• Monitor change
• Determine response
• none H B
• SDLC
• ADM Cycle
• Manage framework
• Maintain Segment Architectures
• Measure EA program value

G Requirements C
Management

F D
E


Preliminary

A

H B
• All phases input, revise, output
• Enter into repository
• Evaluate traceability

G Requirements C
Management

F D
E

TOGAF Architectural Domains

 TOGAF, FEA both driven by Business domain
 TOGAF completes four FEA domains
 Business
 Service Component (called Application in TOGAF)
 Data
 Technology
 Through tailoring
 Can accommodate fifth FEA domain – Performance
 Can be tailored for future domains - e.g. Security


TOGAF Templates and Examples

 All ADM phases have suggested inputs and outputs
 Most outputs have templates and examples
 Most can be mapped to FEA/FSAM


Value Proposition: TOGAF and FEA/FSAM

 ADM maps well to FEA, FSAM, CIO Guidance
 provides a repeatable process
 provides needed process detail
 Certified Tools can provide templates and outlines
 TOGAF is an open standard
 technology and vendor neutral
 intended to be tailored
 Inexpensive to use


Value Proposition: TOGAF and FEA/FSAM

 TOGAF is industry standard
 Consulting resources are available
 10,000+ TOGAF Certified Architects globally
 Many among large Federal contractors
 Small firms also available
 TOGAF simplifies communication with
 Architecture teams
 Vendors
 Consultants


Next Steps

 For the Community
 Study federal EA process problems – is TOGAF a fit?
 For Agencies
 Visit www.opengroup.org – download TOGAF
 Visit www.GTRA.org/blog (TOGAF for Feds)
 Get someone on your EA team trained/certified
 Tailor the FEA/FSAM using TOGAF
 Develop, implement and manage your architecture


Can togaf™ assist_implementation_of_fea_fsam_12_jul10

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Can togaf™ assist_implementation_of_fea_fsam_12_jul10

Similar to Can togaf™ assist_implementation_of_fea_fsam_12_jul10 (20)

Recently uploaded

Recently uploaded (20)

Can togaf™ assist_implementation_of_fea_fsam_12_jul10