TOGAF 9 Methodology - pdf format

1. Summarised Approach - 2010

2.  Architecture Approach
 Architecture Development

11. 1. Objectives
2. Approach
5. Outputs
Preliminary
4. Steps 3. Inputs

12. 1.Organisational
Context
10. Architecture 2.Identify
Principles Stakeholders
Objectives
3. Stakeholder
9. Supporting Tools
Involvement
8. Governance
4. Work Requirements
Framework
7. Architectural
5. Identify Scope
Framework
6. Architecture
Footprint

13. WHERE
•The Enterprise
WHAT
•Define Organisational Context
Approach
WHY
•Requirements for Architecture Work
WHO
•Architectural Principles
HOW
•Management Frameworks

14. Management Frameworks
Determines how a company
manages its change initiatives.
Approach
Determines what business
capabilities are required to
deliver business value including
the definition of return on
investment and the requisite
control/performance measures.
Describes how a company runs its Formalizes the way that business
day-to-day operations, including IT. systems are delivered in accordance
with the structures developed in the
IT architecture
Interoperability and
Relationships between
Management Frameworks

15. Reference Materials Non-Architectural Inputs
External to the 1. IT Strategy
Enterprise
2. Governance
Inputs 1. TOGAF Frameworks, etc,
2. Other Frameworks
Architectural Inputs
1. Existing Frameworks
2. Existing Principles
3. Organisational Model
Input

16. Implement
Architecture Tools
Select and Tailor
Architecture Framework(s)
Steps
Identify and Establish Architecture
Principles
Define and Establish Enterprise Architecture Team and
Organisation
Confirm Governance and Support Frameworks
Scope the Enterprise Organisations Impacted

17. 2 3 4
1
Organisational Tailored
Architecture
Model for Architecture Restatement
Repository
Enterprise Framework
Architecture
Output
Inclusive of Inclusive of Populated with Business
additional additional framework principles, goals,
information information content and drivers
6
5
Request for Governance
Architecture Framework
Work

19. 1. Objectives
2. Approach
5. Outputs
Architecture
Vision
4. Steps 3. Inputs

20. 1.
Recognition
and
10. Endorsement
2.
Impact of
Define and
Parallel
Organise
Architectures
Objectives
9. 3.
Formal Validate
Approval to Business
Proceed KPI’s
8. 4.
Create Scope and
Comprehensi Prioritise
ve Plan Baseline
5.
7.
Define
Articulate
Stakeholders
Architecture
and their
Vision
6. concerns
Key Business
Requirements

21. •What is in, and What is outside the scope of the architecture effort
•Constraints informed by the business principles and architecture
General principles
Approach
•Architecture Vision describes how the new capability will meet the
business goals and strategic objectives and address the
Architecture stakeholder concerns when implemented.
Vision
•Identifying and articulating the business requirements implied in
new business capability to address key business drivers, and the
Business implied architecture requirements.
Scenarios

22. Non-Architectural Inputs
Reference Materials
1. Request for
External to the
Architecture Work
Enterprise
Inputs 2. Business principles,
1. Architecture
goals, and drivers
Reference Materials
Architectural Inputs
1. Organisational Model
for EA
2. Tailored Architecture
Framework
3. Populated Architecture
Repository
Input

23. SAW
Business
transformation
Target Architecture
and KPIs
Steps Develop Architecture Vision
Architecture principles, including
business principles
Define scope
Assess readiness for business transformation
Evaluate business capabilities
Business goals, drivers, and constraints
Identify stakeholders, concerns, and business requirements
Establish the Architecture Project

24. 2 3 4
1
Approved Tailored
Refined Architecture
Statement of Architecture
Statements Vision
Architecture Framework
Work
Output
Scope, Plan, Roles, Stakeholder Requirements
Business Principles, Tailored architecture
Risks, Assessment, Baseline and Target
Goals, Drivers method, and content.
Business Case and Business, Technology,
Configured and
KPI’s Data, Application
deployed tools
Architecture
6
5
Architecture
Communications Repository
Plan
Additional Content

26. 1. Objectives
2. Approach
5. Outputs
Business
Architecture
4. Steps 3. Inputs

27. 1.
Baseline
Business
Architecture
Objectives
5.
2.
Tools and
Techniques Target Business
Architecture
4.
Architecture 3.
Viewpoints
Gap Analysis

28. •The Business Strategy typically defines What to achieve – Business Architecture’s role is to define How
to get there
General
•The analysis of the current state often has to be done bottom-up, particularly where little or no
architecture assets exist
Approach Baseline •The goal should be to re-use existing material as much as possible
Description
•Business models should be logical extensions of the business scenarios from the Architecture Vision,
so that the architecture can be mapped from the high-level business requirements down to the more
Business detailed ones
Modelling
•Generic business models relevant to the organization’s industry sector
•Business models relevant to common high-level business domains
Architecture •Enter prise-specific building blocks
Repository •Applicable standards

29. Non-Architectural Inputs
Reference Materials • Request for Architecture Work
External to the Enterprise
• Business principles, goals, and
•Architecture Reference drivers
Materials •Capability Assessment
•Communication Plan
Inputs Architectural Inputs
•Organisational Model for EA
•Tailored Architecture Framework
•Populated Architecture
Repository
•Approved SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
Input

30. Create
Architecture
Definition
Document
Finalize the
Business
Architecture
Conduct for mal stakeholder
review
Steps
Resolve impacts across the Architecture
Landscape
Define roadmap components
Perform gap analysis
Develop Target Business Architecture Description
Develop Baseline Business Architecture Description
Select reference models, viewpoints, and tools

31. 2 3 4
1
Draft Draft
Business
Architecture Architecture
Architecture Architecture
Definition Requirements
Vision Updates Components
Document Specifications
Output
SAW, Validate
Baseline, Target and Gap Analysis, Technical
Business principles, Of an Architecture
Views for Business Requirements, Updated
drivers, Architecture Roadmap
Architecture Business Requirements
Principles

33. 1. Objectives
2. Approach
5. Outputs
Information
Systems
Architecture
4. Steps 3. Inputs

34. 1. Target
Architectures
Objectives
b.
Application
a.
System
Data System
Domain
Domain

35. • Combination of Data and Application
Architecture
Development
Approach
• implementation approach is top-down
design and bottom-up
Implementation implementation

36. Non-Architectural
Reference Materials
Inputs
External to the
Enterprise • Request for Architecture
Work
•Architecture
Inputs • Capability Assessment
Reference Materials
•Communication Plan
Architectural Inputs
•Organisational Model for EA
•Tailored Architecture Framework
•Architecture Repository
•Approved SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
•Data and Application Principles
•Draft Architecture Document
Input

37. Application Architecture
Steps
Data Architecture

38. 2 3 4
1
Draft Draft Information
Architecture Architecture System
Architecture Definition Requirements Architecture
Vision Updates Document Specifications Components
Output
Gap Analysis Results,
Statement of Baseline, Target and
Technical Requirements, Of an Architecture
Architecture Work Views for Application
Updated Business Roadmap
(SAW) and Data Architectures
Requirements

40. 1. Objectives
2. Approach
5. Outputs
Data
Architecture
4. Steps 3. Inputs

41. 1.
Data Sources
understandable by
Objectives Stakeholders
2.
3.
Data Sources that
Data Sources that
are complete and
are stable
consistent

42. • Data Management
• Data Migration
Key Considerations
for Data Architecture • Data Governance
Approach
• generic data models relevant to the
Architecture organization’s industry ‘‘vertical’’ sector
Repository

43. Reference Materials
Non-Architectural
External to the Inputs
Enterprise • Request for
•Architecture Architecture Work
Reference • Capability Assessment
Architectural Inputs
Inputs Materials •Communication Plan
•Organisational Model for EA
•Tailored Architecture Framework
•Architecture Repository
•SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
•Data Principles
•Draft Architecture Document
•Draft Arch. Req. Spec
•Bus Arch. Road Map
Input

44. Definition
Document
Finalize the Data
Architecture
Conduct for mal stakeholder
review
Steps
Resolve impacts across the Architecture
Landscape
Define roadmap components
Perform gap analysis
Develop Target Data Architecture Description
Develop Baseline Data Architecture Description
Select reference models, viewpoints, and tools

45. 2 3 4
1
Draft Draft
Data
Architecture Architecture
Architecture Architecture
Definition Requirements
Vision Updates Components
Document Specifications
Output
Statement of Gap Analysis Results,
Baseline, Target and
Architecture Work Technical Requirements, Of an Architecture
Views for Data
(SAW), Validated Data Updated Business Roadmap
Architectures
Principles Requirements

47. 1. Objectives
2. Approach
5. Outputs
Application
Architecture
4. Steps 3. Inputs

48. 1.
Define the
application
system to
process data
and support
business
Objectives 5. 2.
applications Define what
that are stable application
and relatively systems are
unchanging relevant to the
organisation
4. 3.
Technology Logical groups
agnostic of Capabilities
that manage
data objects

49. • Generic business models relevant to the
Architecture
Repository
organization’s industry sector
Approach

50. Non-Architectural
Reference Materials Inputs
External to the
Enterprise • Request for Architecture
Work
•Architecture • Capability Assessment
Inputs Reference Materials Architectural Inputs •Communication Plan
•Organisational Model for EA
•Tailored Architecture Framework
•Architecture Repository
•Approved SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
•Application Principles
•Draft Architecture Document
•Draft Architecture Req. Spec.
•Bus and Data Components
Input

51. Create
Architecture
Definition
Document
Finalize the
Application
Architecture
Conduct for mal stakeholder
review
Steps
Resolve impacts across the Architecture
Landscape
Define roadmap components
Perform gap analysis
Develop Target Application Architecture Description
Develop Baseline Application Architecture Description
Select reference models, viewpoints, and tools

52. 2 3 4
1
Draft Draft
Application
Architecture Architecture
Architecture Architecture
Definition Requirements
Vision Updates Components
Document Specifications
Output
Gap Analysis Results,
Statement of Baseline, Target and
Technical Requirements, Of an Architecture
Architecture Work Views for Application
Updated Business Roadmap
(SAW) Architectures
Requirements

54. 1. Objectives
2. Approach
5. Outputs
Technology
Architecture
4. Steps 3. Inputs

55. 1.
To map
Application
Components into
Technology
Components
Objectives
4.
Supports costs
assessments for
particular 2.
migration
Strong links to
scenarios
implementation
and migration
planning
3.
Logical groups of
Capabilities that
manage data
objects

56. •Existing IT services as documented in the IT repository
•TOGAF Reference Model
Architecture •Generic Technology Models
Approach Repository •Technology Models relevant to Common Systems Architecture

57. Non-Architectural
Reference Materials Inputs
External to the
Enterprise • Request for Architecture
Work
•Architecture • Capability Assessment
Inputs Reference Materials Architectural Inputs •Communication Plan
•Organisational Model for EA
•Tailored Architecture Framework
•Architecture Repository
•Approved SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
•Technology Principles
•Draft Architecture Document
•Draft Architecture Req. Spec.
•Bus, Application and Data Components
Input

58. Definition
Document
Finalize the
Technology
Architecture
Conduct for mal stakeholder
review
Steps
Resolve impacts across the Architecture
Landscape
Define roadmap components
Perform gap analysis
Develop Target Technology Architecture Description
Develop Baseline Technology Architecture Description
Select reference models, viewpoints, and tools

59. 2 3 4
1
Draft Draft
Technology
Architecture Architecture
Architecture Architecture
Definition Requirements
Vision Updates Components
Document Specifications
Output
Gap Analysis Results,
Statement of Baseline, Target and Outputs from Phase B
Of an Architecture
Architecture Work Views for Application and C, Updated
Roadmap
(SAW) Architectures Technology
Requirements

61. 1. Objectives
2. Approach
5. Outputs
Opportunities
and Solutions
4. Steps 3. Inputs

62. 1.
Review Business
Objectives and
Consolidate Gaps
4.
Consensus on
Objectives Implementation 2.
and Migration
Review and
Strategy
confirm the
enterprise
current
parameters
3.
Derive Transition
Architectures for
continuous value

63. •Concentrates on how to deliver the Architecture
•Logical Grouping within a IT Portfolio
•Assess the organization’s business transformation readiness
Target Architecture
Implementation •Identify all implementation constraints
•Opportunities and solutions is done in a top-down fashion or is approached in a
tactical opportunistic way
Enterprise Strategic •Phased deliver y working towards the Target Architecture
Change Perspective
Approach
•Architecture artefacts (especially the gap analysis results) are consolidated and their
inter-dependencies closely assessed to derive an initial critical path
Consolidation and •A high-level Implementation and Migration Strategy is developed
Integration
•Transition Architectures consist of a set of co-ordinated and well-defined building
blocks grouped into work packages that define the scope of deliver y vehicles
•Transition Architecture delivers discrete business value based upon the overall
Transition
Architectures enterprise capabilities

64. Non-Architectural
Reference Materials Inputs
External to the
•Request for Architecture
Enterprise Work
•Architecture Reference •Capability Assessment
Materials
Architectural Inputs
•Communication Plan
•Product Information •Organisational Model for EA •Planning Methodologies
•Governance Models & Frameworks
•Tailored Architecture Framework
•Architecture Repository
•SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
Inputs •Draft Architecture Document
•Draft Architecture Req. Spec.
•Change Requests
Input

65. Portfolio
and Project
charters
Transition
Architectures
work packages
Implementation and Migration
Strategy
Steps Confirm readiness and risk for business
transformation
Refine and validate dependencies
Consolidate and reconcile interoperability requirements
Review IT requirements from a functional perspective
Review and consolidate gap analysis results from Phases B to D
Determine business constraints for implementation
Deter mine/confirm key corporate change attributes

66. 2 3 4
1
Updates of Consolidate and
Architecture Validated Capability Transition
Vision and Architecture Assessment Architecture
other Road Map
architectures
Consolidated Gaps, Risk
Enterprise Architecture
(SAW), Draft Register, Impact Analysis,
Maturity Profile,
Architecture Dependency analysis
Output Transformation
Definition Doc Report, Implementation
5 Readiness Report
Factor and Deduction
Matrix
Implementation
and Migration
Plan
including the high-level
Implementation and
Migration Strategy

68. 1. Objectives
2. Approach
5. Outputs
Migration
Planning
4. Steps 3. Inputs

69. 1.
Coordination
with
Management
Frameworks
5.
2.
Create, evolve
and monitor Assigning
implementation Business Value
Objectives and migration and conduct
plan cost/business
analysis
4. 3.
Confirm Finalise
Transition Architecture
Architectures Vision and
Definition
Documents

70. •Creation of plan in cooperation with project and portfolio managers
Implementation and
Migration Plan
•Assessing the dependencies, costs, and benefits of the various migration projects.
•Prioritized list of projects will for m the basis of the detailed Implementation and
Prioritised Projects Migration Plan
Approach
•Co-ordination to ensure that business value is delivered and that the resources are
made available to complete the necessary work.
Enterprise
Management •Agencies outside of the enterprise architecture world are aware of the scope
Frameworks
•Ensure that the architecture stays relevant, and lessons learned should be documented
to enable continuous process improvement
Architecture
Evolution Cycle

71. Non-
Reference Architectural
Materials Inputs
External to the
Architectural Inputs •Request for
Enterprise
•Organisational Model for EA Architecture Work
•Architecture •Capability
•Governance Models & Frameworks
Reference Assessment
•Tailored Architecture Framework
Materials •Communication Plan
•Architecture Repository
•SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision
•Draft Architecture Document
•Draft Architecture Req. Spec.
Inputs •Change Requests
•Transition Architecture
•Capability Assessment
•Implementation and Migration Plan
Input

72. architecture
evolution cycle
Generate the Architecture
Implementation Roadmap
Confirm Transition Architecture
increments/phases
Steps
conduct of a cost/benefit assessment and risk
validation
Estimate resource requirements, project timings, and
availability/deliver y vehicle
Assign a business value to each project
Confirm management framework interactions for Implementation and Migration Plan

73. 2 3 4
1
Finalised Finalised
Finalised
Implementation Architecture Architecture
Architecture
and Migration Definition Requirement
Roadmap
Plan Document Specification
5 6 7 8
Output
Architecture
Finalised Re-Usable Request for
Contracts for
Transition Architecture Architecture
Implementation
Architecture Building Blocks Work
projects
9 10
Change
Implementation
Request arising
Governance
for Lessons
Model
Learned

75. 1. Objectives
2. Approach
5. Outputs
Implementation
Governance
4. Steps 3. Inputs

76. 1.
Recommenda
tions for each
implementati 2.
on project
7. Govern
Architecture
Mobilise
Contract
Supporting
Operations
Objectives
6.
Ensure 3.
Conformance Appropriate
with Governance
deployed Functions
solution
5. 4.
Successful Ensure
Deployment Conformance
with defined
architecture

77. •Establish an implementation program that will enable the deliver y of the
Transition Architectures agreed for implementation during the Migration
Planning phase
Implementation
Programme
•Adopt a phased deployment schedule that reflects the business priorities
Phased Deployment embodied in the Architecture Roadmap
Schedule
Approach
•Follow the organization’s standard for corporate, IT, and architecture
Organisation Standard
governance
•Use the organization’s established portfolio/program management
Management approach, where this exists
Approach
•Define an operations framework to ensure the effective long life of the
Operations Framework
deployed solution

78. Non-
Reference Architectural
Materials Inputs
External to the
Architectural Inputs •Request for
Enterprise
•Organisational Model for EA Architecture Work
•Architecture •Capability
•Governance Models & Frameworks
Reference Assessment
•Tailored Architecture Framework
Materials •Communication Plan
•Architecture Repository
•SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision and Contract
•Draft Architecture Document
•Draft Architecture Req. Spec.
Inputs •Change Requests
•Transition Architecture
•Capability Assessment
•Implementation and Migration Plan
Input

79. post-implementation
review
Implement business and IT
operations
Steps Perform enter prise architecture compliance
reviews
Guide development of solutions deployment
Identify deployment resources and skills
Confirm scope and priorities for deployment with development management

80. 2 3 4
1
Architecture –
Compliance Change compliant
Architecture Assessment Requests solutions
Contract deployed
Output

82. 1. Objectives
2. Approach
5. Outputs
Architecture
Change
Management
4. Steps 3. Inputs

83. 1.
Baseline Fit-
for-purpose
2.
6. Assess
Performance
Operate
and Make
Governance
recommendati
Framework
ons
Objectives
5.
Maximise 3.
Business Value
Assess
Changes
4.
Architecture
Change
Management
Process

84. •Strategic, top-down directed change to enhance or create new capability (capital)
•Bottom-up changes to correct or enhance capability (operations and maintenance) for
infrastructure under operations management
Drivers for Change •Experiences with the previously delivered project increments
•Simplification change: A simplification change can normally be handled via change
management techniques.
Approach •Incremental change: An incremental change may be capable of being handled via change
management techniques
EA Change
Management •Re-architecting change: A re-architecting change requires putting the whole architecture
through the architecture development cycle again
Process
•If the change impacts two stakeholders or more, then it is likely to require an architecture
redesign and re-entry to the ADM.
•If the change impacts only one stakeholder, then it is more likely to be a candidate for
change management
Guidelines for
Maintenance vs. Re- •If the change can be allowed under a dispensation, then it is more likely to be a candidate
for change management.
Design

85. Non-
Reference Architectural
Materials Inputs
External to the
Architectural Inputs •Request for
Enterprise
•Organisational Model for EA Architecture Work
•Architecture •Capability
•Governance Models & Frameworks
Reference Assessment
•Tailored Architecture Framework
Materials •Communication Plan
•Architecture Repository
•SAW
•Enterprise Continuum
•Architecture Repository
•Architecture Vision and Contract
•Draft Architecture Document
•Draft Architecture Req. Spec.
Inputs •Change Requests
•Transition Architecture
•Capability Assessment
•Implementation and Migration Plan
Input

86. Activate process
Manage governance
process
Develop change requirements to meet
performance targets
Steps
Provide analysis for architecture change
management
Manage risks
Deploy monitoring tools
Establish value realization process

87. 2 3 4
1
Changes to
New Request Statement of
Architecture
Architecture for Architecture Architecture
Framework and
Updates Work Work
Principles
5 6
Output
Updated Updated
Architecture Compliance
Contract Assessments

89. 1. Objectives
2. Approach
5. Outputs
Requirements
Management
4. Steps 3. Inputs

90. 1.
Define an EA Process:
requirements are
identified
Objectives
3.
2.
Define an EA Process:
Define an EA Process:
requirements are
requirements are
synched with ADM
stored
Phases

91. •Dynamic process whereby requirements for enterprise
architecture and subsequent changes to those
requirements are identified
•Process for managing requirements throughout the
General overall ADM.
Approach
•Business Scenarios
•Volere Requirements Specification
•Requirements Tools
Resources

92. Tailored Requirements
Architecture Impact
A populated Assessment Architecture
Framework
Architecture Vision
Repository
Architecture
Tailored Requirements
Architecture
Framework
Statement of
Inputs Architecture
Work
Input

93. Requirements Management Steps ADM Phase Steps
Step 1 Identify/document requirements — use business
scenarios, or an analogous technique
Step 2 Baseline requirements:
a. Determine priorities arising from
current phase of ADM
b. Confirm stakeholder buy-in to
resultant priorities
c. Record requirements priorities and
place in requirements repository
Step 3 Monitor baseline requirements
Steps Step 4 Identify changed requirements:
a. Remove or re-assess priorities
b. Add requirements and reassess priorities
c. Modify existing requirements
Step 5 Identify changed requirements and
record priorities:
Step 6 a. Assess impact of changed requirements on current
(active) phase
b. Assess impact of changed requirements on
previous phases
c. Determine whether to implement change, or defer
to later ADM cycle; if decision is to implement,
assess timescale for change management
implementation
d. Issue Requirements Impact Statement, Version n+1
Step 7 Implement requirements arising from
Phase H

94. Requirements Management Steps ADM Phase Steps
Step 8 Update the requirements repository with
information relating to the changes
requested, including stakeholder views
affected
Step 9 Implement change in the current phase
Step 10 Assess and revise gap analysis for past phases
The gap analysis in the ADM Phases B through D
identifies the gaps between Baseline and Target
Architectures.
Certain types of gap can give rise to gap requirements.
The ADM describes two kinds of gap:
Steps •Something that is present in the baseline, but
not in the target (i.e., eliminated — by accident
or design)
• Something not in the baseline, but present in
the target (i.e., new)

95. 2
1
Updated
Requirements Architecture
Impact Requirements
Assessment Specification
Output

96.  TOGAF Version 9, The Open Group
Architecture Framework (TOGAF), 2009

98. If you have one last breath
use it to say...