You are on page 1of 40

Association of Open Group

Enterprise Architects
Ottawa-Gatineau Chapter

29th of March 2010


EA Seminar

INTEGRATING ENTERPRISE ARCHITECTURE MANAGEMENT


AND TECHNICAL FRAMEWORKS
Presented By:
Lynn Wallace
Senior Information Architect, Canada Revenue Agency
Lynn.wallace@cra-arc.gc.ca
Robert (Bob) Weisman MSc, PEng, PMP, CD
CEO/Principal Consultant, Build The Vision Inc.
Robert.weisman@buildthevision.ca
Agenda

• The Need to Integrate


– What is TOGAF
– Core concepts
• EA and Business Planning
• EA and Project Management
• EA and Software Engineering (SDLC)
• EA and Data Mgt Body of Knowledge
• EA and Service Management
• Putting it all Together
• Concluding Material
Slide 2
Stakeholders - The Management Frameworks – TOGAF 9
GOVERNANCE
Business Enterprise
Capability Architecture
Management Development
Method

Portfolio/
Project
Management
Operations /
Solution / System
Service
Development
Management
Method

Slide 3
Levels of Abstraction – Using the Zachman Framework
(An Example)
What How Where Who When Why
Data Process Network People Time Motivation
Scope/Objectives (CONTEXTUAL)
(Ballpark View)
Strategic Architecture / Architecture Principles
Model of Business
(Owner’s View) (CONCEPTUAL)

Description of IS Architecture Definition / Reference


(Designer’s View) (LOGICAL)
Technology Model
(Builder’s View) Transition Architecture
Detailed Description (PHYSICAL)
(Out-of-Context)
Baseline Architecture (PHYSICAL)
Actual System
(a.k.a. Operational / As-Is Architecture)
Slide 4
A Simplified View of the TOGAF Architecture Development
Method
Enterprise Architecture A Scalable Methodology
Preliminary Planning •Business Driven
•Managed by Requirements
Request for Architecture Work
EA Framework
IM/IT Governance

Strategic
G - Implementation A- Vision
Governance Enterprise
H - EA Change Architecture
Management Vision Strategic EA Vision
Lessons Learned (Statement Architecture Work)
Change Requests

Enterprise B-Business
Enterprise C1- Data/Information
Architecture Requirements C2 - Applications
Architecture
Implementation Management D -Technology
Definition X - Security
Management

Transition EA Foundation Architecture


Solution Building Blocks Enterprise Arch Building Blocks
Migration & Implementation Plan Architecture E- Opportunities &
Solutions
Transformation F - Migration Planning

Slide 5
© Robert Weisman 2009
Foundation Architecture
Technical Reference Model Services
S
• Model and
E
taxonomy of generic Infrastructure Business
platform services
R
V Applications Applications
• Based upon DoD
TAFIM TRM (IEEE
I
C Applications Platform Interface
POSIX 1003.0)
E Software System and Location and Data
International
Engineering Network Directory Management
Operations
Q Services Management Services Services
Data Graphics
U Security Transaction
User Interface Interchange & Image
Services Processing
A Services Services
L Operating Systems Services

I Network Services
T
I Communications Infrastructure Interface
E
S Communications Infrastructure
© Robert Weisman 2009 Slide 6
EA and Business Planning

Slide 7
Business Planning
Baseline
Scope Enterprise
State
Target
Enterprise
State
Time
Strategic Enterprise Plan 10 Years

5 Years

12 Months
Depth Segment
Segment
(Content) Business
Segment Business
Segment Plans
Segment Business Plans
Business
Segment Business Plans
Plans
Business Plans
Plans
© Robert Weisman 2009 Slide 8
Business Planning drives EA Response
Baseline
Scope Enterprise
Architecture
Target
Enterprise
Strategic Enterprise Architecture Architecture
Time
10
Years
Enterprise Architecture Enterprise Architecture
Definition #1 Definition #2
5 Years

12 Months

Depth Arch
Arch
(Content) Arch Realization
Arch Realization
Arch Realization
Arch Realization
Realization
Realization

© Robert Weisman 2008 Slide 9


Capability Concept – TOGAF 9

Capability

Capability
Capability
Capability Increment

Materiel
People Dimension Process Dimension
Dimension
Individual Training Concepts
Collective training Business Processes Infrastructure
Professional Development Information Mgt Information Technology
Equipment
Slide 10
Capability Management – TOGAF 9
5 – 10 Corporate
years Business Plan
Business Transformation
Goals and Objectives

Identifies
Horizontal Management Across
3–5 Capability Portfolios
(Outcome
years Oriented)
•Strategic Business Leadership
Is matured through
Possible Capability Dimensions
•Personnel
.25 – 1.5 Capability •R&D
years Increment
•Infrastructure/facilities
Is delivered through •Concepts/Processes
•Information Management
Building Blocks
•Materiel
(Deliverables)

Capability
Management
© Robert Weisman 2008 Slide 11
EA and Business Planning
TOGAF 9 Main EA Activities and Deliverables Business Planning Activities and Deliverables
Phase
(Using Capability or Outcome Based Planning)
P Preliminary Planning Preliminary Business Planning
• EA Framework • Planning Framework
• IM/IT Governance • Measurement & Reporting Framework, e.g. MAF
• Corporate Governance
A Vision Define Vision and Strategies
• Vision Document including Roadmap • Enterprise Vision
• Enterprise Strategic Plan
R Requirements Management N/A

B, C, D Architecture Definition Identify / Target Capabilities


• Corporate Business Plan
E, F Architecture Transformation Identify Capability Increments
• Transition Architectures • Segment Business Plans
• Implementation and Migration Plan • Implementation Plans
G Architecture Implementation N/A
Governance
H Architecture Change Management N/A
Slide 12
EA and Project Management

Project Management Institute


TB CIOB Guidance

Slide 13
Stages of the Project Lifecycle
INITIATING Project Charter
Prelim Scope Statement
Authorizing the Project

PLANNING
Plan and Schedule the
Project Work Project Mgt Plan
Subsidiary Function Plans

CLOSING
Change Requests
EXECUTING
Close the Project
Changes to Project Perform the
Formally
Project Work

MONITORING &
Deliverable Acceptance CONTROLLING
Contract Closure Project Deliverables
Monitor to detect
variance and correct
Project Knowledge Areas
Project Project
Lifecycle Phases Knowledge Areas

1. Communications Management
2. Cost Management
3. Human Resource Management
4. Integration Management
5. Procurement Management
6. Quality Management
7. Risk Management
8. Scope Management
9. Time Management
Strategic Roadmap – Phase A
Scoping Portfolios and Projects
PORTFOLIO 1

Activity 1 Activity 2 Activity 3 Activity 4

PROJECT 1 PROJECT 2

Activity 5 Activity 6
PROJECT 3

Activity 8 Activity 9 Activity 10 Activity 7 Target


Architecture

Activity 11 Activity 12 Activity 13 Activity 14

Business Capability / Value Milestones


Portfolio/Project Management – TOGAF 9
Corporate
Strategic Plan Strategic Not Business
Business Transformation
Goals and Objectives
Identifies

5 – 10 Functional
years Portfolios
(e.g. IT, HR)

Consists of

3–5 Project
Project
Project/
years Initiative

Contains

.5 – 1.5 Project/
years Initiative
Increment

Slide 17
EA and Project Management
TOGAF 9 Main EA Activities and Deliverables Project Management Phases and Deliverables
Phase
P Preliminary Planning Selection of Portfolio / Project Management
• Framework and Governance Framework
A Vision Portfolio Initiation
• Vision Document including Roadmap
R Requirements Management Portfolio Planning
Project Planning
B, C, D Architecture Definition Project Initiation
E, F Architecture Transformation Project Planning
• Transition Architectures
• Implementation and Migration Plan
G Architecture Implementation Project Execution
Governance Monitoring and Controlling
H Architecture Change Management Monitoring and Controlling

Slide 18
EA and PM Knowledge Areas
PM Knowledge Areas Project Management Phases and Deliverables
Communications Management * Preliminary Phase – Stakeholder Management
* Chapter 24 – Stakeholder Management
Scope Management • Preliminary Planning – Request for Arch Work
• A - Vision – Statement of Architecture Work
• Requirements Management
Quality Management • Requirements Management
• B-D - Architecture Definition – Service Qualities
Human Resource Management • B-D - Architecture Definition – Service/Technical Reference Models
• Chapter 52 - Architecture Related Roles
Integration Management • A - Architecture Vision – Strategic Conceptual
• B – D - Architecture Definition – Logical
• E - Opportunities and Solutions – Physical
• Chapter 29 - Interoperability
Risk Management • E - Opportunities and Solutions – Implementation Risk
• H - Architecture Change Management
• Chapter 31 – Risk Management
Cost Management • A - Vision, B-D Definition and E - Opportunities & Solutions
– Different levels of cost estimate
Time Management • A - Vision and Phase F – Migration Planning
Procurement Management •Not really addressed in TOGAF Slide 19
EA and Software Engineering

ISO 42010

Slide 20
System Development Life Cycle (SDLC)

OPERATE
PLAN ANALYZE DESIGN BUILD TEST DEPLOY &
MAINTAIN

Architecture descriptions created: Architecture descriptions used:

• guided by enterprise architecture • to ensure system/solution built and


principles delivered according to architecture

• in accordance with enterprise • as reference during operation and


standards for architecture maintenance and as baseline for future
descriptions maturation of enterprise

A standard for architecture descriptions provides benefits through


all phases of SDLC. ISO 42010 is one such standard.
© Robert Weisman 2009 Slide 21
ISO 42010 Concepts

• Many stakeholders for any system … and each


has different concerns
• Single architecture description that addresses
all stakeholder concerns will be unnecessarily
complex … architecture descriptions should be
delivered as discrete views
• Creation of views can be standardized …
viewpoints
• Some architecture quality considerations cross
views … architectural perspectives
Slide 22
ISO 42010 Concepts – some examples

• Stakeholders, and their concerns:


– Users, does the system meet their needs?
– Developers, will the system follow established development approaches,
standards? How easy/difficult will it be to repair or enhance?
– Owners, what will it cost?
• Viewpoints:
– Functional, Information, Concurrency … describe what the system does,
how it behaves
– Development, Deployment, Operational … how system (capability
increment) is realized
• Perspectives:
– Evolution (extensibility)
– Performance and scalability
– Security
Reference: Software Systems Architecture by Nick Rozanski and Eoin Woods

Slide 23
EA and Software Engineering
TOGAF 9 Main EA Activities and Deliverables ISO 42010 Deliverables
Phase

P Preliminary Planning • List of stakeholders and concerns


• Framework and Governance • Viewpoint / Perspectives Library
• Views : Perspectives mapping
• Quality review and/or governance model
A Vision • Architectural Principles
• Vision Document including Roadmap • Functional, Information views (high-level)
R Requirements Management N/A

B, C, D Architecture Definition • Functional, Information, Concurrency views


E, F Architecture Transformation • Development, Deployment, Operational views
• Transition Architectures
• Implementation and Migration Plan
G Architecture Implementation • Architectural Assessment Alignment Report
Governance
H Architecture Change Management • Architectural Assessment Alignment Report

Slide 24
EA and Data Management
Body of Knowledge
Data Management Association
TB CIOB Data Stewardship

Slide 25
DAMA-DMBOK Data Management Functions
Data Governance
Data Architecture
Management
Data Development
Database Operations
Management
Data Security Management
Reference & Master Data
Management
Data Warehousing &
Business Intelligence
Management
Document & Content
Management
Meta Data Management
Data Quality Management
© 2008 DAMA International Slide 26
EA and Data Management Body of Knowledge
TOGAF 9 Main EA Activities and Deliverables DMBOK
Phase
P Preliminary Planning Data Governance
• Framework and Governance Professional Development
A Vision Data Architecture – High Level
• Vision Document including Roadmap
R Requirements Management Relevant to all DAMA-DMBOK functions

B, C, D Architecture Definition – Logical B,C,D and E,F


E, F Architecture Transformation - Physical Data Architecture
• Transition Architectures B,C,D and E,F and G and H
• Implementation and Migration Plan Meta-Data Management
Data Security Management
G Architecture Implementation
Reference and Master Data Management
Governance
Data Warehousing and Bus. Intelligence Management
H Architecture Change Management Document and Content Management
E,F and G and H
Data Development
Database Operations Management
Data Quality Management

Slide 27
EA and Service Management

ISO 20000
Information Technology
Infrastructure Library (ITIL)
What is a Service ?
• Service
– a means of delivering value to customers by
facilitating outcomes customers want to achieve
without the ownership of specific costs and risks
• Service Management
– a set of specialized organizational capabilities for
providing value to customers in the form of
services.
ITIL Service Lifecycle
ITIL Service Phases
Service Service Design Service Transition Service Continuous Service
Strategy Operation Improvement
1. Financial Mgt 1. Service 1. Change Mgt 1. Event Mgt 1. Service
2. Service Portfolio Catalogue Mgt 2. Service Asset and 2. Incident Mgt Improvement
Mgt 2. Service Level Configuration Mgt 3. Request 2. Service
3. Demand Mgt Mgt 3. Knowledge Mgt Fulfilment Measurement
3. Capacity Mgt 4. Release and 4. Access Mgt 3. Service Reporting
4. Availability Mgt Deployment Mgt 5. Problem Mgt
5. IT Service 5. Service Validation
Continuity Mgt and Testing Functions
6. Information 6. Evaluation • Service Desk
Security Mgt • Technical Mgt
7. Transition Planning
• Application Mgt
7. Supplier Mgt and Support
• IT Ops Mgt

Deliverables
• Strategies • Solution Design • Transition Plans • Operational Plans • Improvement Actions
• Policies • Architectures • Tested Solutions • Operational and Plans
• Resource • Standards • Service Knowledge Services
Constraints • Service Design Management
• Service Level Package (SDP) System (SKMS)
Packages (SLP)
Change Management
Service Change
– the addition, modification or removal of an authorised, planned or supported service or
service component and its associated documentation.
Continual Service Improvement Model
Service Portfolio Concept

Target Architecture Baseline Architecture

TOGAF V9

ITIL V3 Pipeline Services Service Catalogue Retired Services

Service Portfolio
Enterprise Architecture Enables Strategic Planning

Strategic
Business Needs
EA enables proactive
Strategic Project Generation Strategic
Enterprise Tech Arch
Strategic
Tactical Project IT Project
Governance
Generation (Change Advisory
Board) Tactical
Tactical
IT Project IT Project

Tactical Tactical
IT Need IT Need

Tactical Tactical
Business Need Business Need

© Robert Weisman 2008 Slide 36


EA and Service Management
TOGAF 9 Main EA Activities and Deliverables Service Management Phases and Deliverables
Phase
P Preliminary Planning ITIL Framework
• Framework and Governance
A Vision Service Strategy
• Vision Document including Roadmap
R Requirements Management Service Knowledge Management System (SKMS)

B, C, D Architecture Definition Service Design


E, F Architecture Transformation Service Transition
• Transition Architectures
• Implementation and Migration Plan
G Architecture Implementation Service Transition
Governance
H Architecture Change Management Service Operation
Continual Service Improvement
Concluding Material
Putting it All Together

Slide 38
Concluding Material
• There is much work to do; no need to
duplicate
• Cooperatively the frameworks do match
• EA in isolation is rarely successful

Slide 39
QUESTIONS ?
Presented By:
Lynn Wallace, Canada Revenue Agency
Lynn.wallace@cra-arc.gc.ca
Mr. Robert (Bob) Weisman Build The Vision Inc.
Robert.weisman@buildthevision.ca

INTEGRATING ENTERPRISE ARCHITECTURE, MANAGEMENT


AND TECHNICAL FRAMEWORKS

Slide 40

You might also like