Download - Module 3 Overview of TOGAF 9.1 Architecture Development ... · The Architecture Development Method (ADM) Architecture Development Method ... TOGAF Capability Framework TOGAF Enterprise

Module 3

Overview of TOGAF 9.1Architecture Development Method (ADM)

TOGAF 9.1 Training – Copyright© 2012 Enterprise Architects v1.8 – Module 03 – Slide 2 of 29

TOGAF 9.1 StructureThe Architecture Development Method (ADM)

Architecture Development Method (Part II) –

14, 16, 18, 19, 22- 27 ADM Guidelines and

Techniques (Part III) – 07, 08, 12, 13, 15, 17, 28-30

Business Capabilities

Enterprise Continuum and Tools (Part V) – 05,09

TOGAF Reference Models (Part VI) – 20,21

Architecture Content

Framework (Part IV) – 04,06,07

TOGAF Capability Framework

TOGAF Enterprise Continuum and Tools

TOGAF ADM & Content Framework

Architecture Capability Framework

(Part VII) – 10, 11, 12

Sets targets, KPIs, plans, and budgets for architecture roles

Business Capability drives the need for Architecture Capability Maturity

The Architecture Capability operates a method

The method delivers new business solutions

Operational changes update the Enterprise Continuum and

Repository

The Enterprise Continuum and Repository inform the business of

current state

The method produces content to be stored in the Repository, classified

according to the Enterprise Continuum

The method refines understanding of business need

Business need feeds into the method, identifying problems to

be addressed

Effective operation of the Architecture Capability ensures

realization of the Business Vision

Business Vision and

Drivers

Informs the size, structure, and culture of the capability

Needs of the business shape non-architectural aspects of business operation

Learning from the business operation creates new business need


In this Training Module

This module provides a high-level overview of the TOGAF 9.1 ADM

We will cover each of the ADM phases in detail in subsequent modules

This module covers three topics:

1. Overview of the TOGAF ADM

2. Objectives of Each ADM Phase

3. Architecture Development


Architecture Development Method (ADM)Key Learning Points

• The ADM defines a method for developing an Enterprise Architecture

• The ADM is at the core of TOGAF

• The Architecture Repository will be populated with architecture artefacts

• As the result of multiple iterations of the ADM

Architecture Repository

Architecture Artefacts, Views, Building Blocks,

Deliverables


Overview of the ADM

• The ADM is iterative

– Over the whole ADM

– Between phases

– Within phases


Overview of the ADM

Every ADM Phase has five (5) aspects

1. Objectives– Major goals and purposes for the Phase

2. Approach– Considerations and references relevant to the Phase

3. Inputs– Deliverables, endorsements, artefacts, knowledge required to execute the Phase– May be outputs from prior Phases – or prior iterations – of ADM

4. Steps– Actions to be taken to complete the Phase – not necessarily in sequence

5. Outputs– Deliverables, endorsements necessary to complete the Phase


Output and Versioning

• Outputs– Architecture Views, Artefacts, Deliverables– Architecture outputs are created in each ADM phase– Outputs from one ADM Phase are inputs to subsequent Phases

• This numbering scheme is provided as an example only

• Version 0.1– A high-level outline (draft)– Likely to evolve through subsequent investigation and discovery

• Version 1.0– A detailed architecture that is formally reviewed and signed off by stakeholders

Refer next slide …


Overview of the ADMVersioning – 0.1s to 1.0s

Phase Deliverable Content Version

A: Architecture Vision

Architecture Vision Business ArchitectureData ArchitectureApplication ArchitectureTechnology Architecture

0.10.10.10.1

B: Business Architecture

Architecture Definition Document

Business Architecture 1.0

C: Information Systems Architecture


Data ArchitectureApplications Architecture

1.01.0

D: Technology Architecture


Technology Architecture 1.0

• Each 0.1 “Draft” Domain Architecture view that was created in Phase A …• Must be turned into a 1.0 “Final” architecture view …• In the corresponding subsequent Domain Architecture Phase• We see that Phase A is a Very Important Phase!


Overview of the ADM

Next topic:


2. Objectives of ADM Phases



Objectives of ADM PhasesPreliminary Phase

• Determine the Architecture Capability desired by the organisation:– Review the organisational context for conducting enterprise architecture– Identify and scope the elements of the enterprise organisations affected by the

Architecture Capability– Identify the established frameworks, methods, and processes that intersect with

the Architecture Capability– Establish Capability Maturity targets (for the architecture function)

• Establish the Architecture Capability:– Define and establish the Organisational Model for Enterprise Architecture– Define and establish the detailed process and resources for architecture

governance– Select and implement tools that support the Architecture Capability– Define the Architecture Principles


Objectives of ADM PhasesPhase A – Architecture Vision

• Objectives of Phase A

– Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture

– Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision


Objectives of ADM PhasesPhase B – Business Architecture

• Objectives of Phase B

– Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns

– Identify candidate Architecture Roadmap components


Objectives of ADM PhasesPhase C – Information Systems Architectures

• Objectives of Phase C

– Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns

– Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures


Objectives of ADM PhasesPhase D – Technology Architecture

• Objectives of Phase D

– Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns

– Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

Phases B, C and D are the ‘Domain Architecture’ Phases


Objectives of ADM PhasesPhase E – Opportunities and Solutions

• Objectives of Phase E

– Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D

– Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value


Objectives of ADM PhasesPhase F – Migration Planning

• Objectives of Phase F

– Finalise the Architecture Roadmap and the supporting Implementation and Migration Plan

– Ensure that the Implementation and Migration Plan is coordinated with the enterprise’s approach to managing and implementing change in the enterprise’s overall change portfolio

– Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

Phase F marks the end of architecture development –and the beginning of implementation


Objectives of ADM PhasesPhase G – Implementation Governance

• Objectives of Phase G

– Ensure conformance with the Target Architecture by implementation projects

– Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests


Objectives of ADM PhasesPhase H – Architecture Change Management

• Objectives of Phase H

– Ensure that the architecture lifecycle is maintained– Ensure that the Architecture Governance Framework is executed– Ensure that the enterprise Architecture Capability meets current requirements


Objectives of ADM PhasesArchitecture Requirements Management

• The objectives of the Requirements Management Phase

– Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases

– Manage architecture requirements identified during any execution of the ADM cycle or a phase

– Ensure that relevant architecture requirements are available for use by each phase as the phase is executed


Overview of the ADM

Next topic


2. Objectives of ADM Phases



Architecture DevelopmentAdapting the ADM

• The ADM is a generic method for architecture development:

• It is expected that you will modify the ADM– To suit your needs, resources, maturity

• In the Preliminary Phase you will consider whether you need to modify the ADM, and how you will do this

– Fundamental, permanent modification of the ADM for all future iterations must be understood and approved by the Architecture Review Board

– Further modifications to specific iterations of the ADM must be understood and approved by sponsors, stakeholders (and possible the ARB again)

• Adapt the ADM on a “need to” basis– If you modify the ADM excessively, you may defeat a key benefit of adopting an

‘open standard’ architecture method in the first place– What is that benefit?


Architecture Development Scoping the Architecture

• There are many reasons to constrain (or restrict) the scope of architectural activity

– Organisational authority of the team producing the architecture

– Stakeholder concerns and objectives

– Availability of people, finance, time

– To ensure architects are not working on duplicate or conflicting activities


Architecture Development Scoping the Architecture

Four considerations will determine the scope of architecture

1. Scope of the Enterprise• Many enterprises are very large – “Federated Architecture”• Modern enterprises may span external suppliers, customers, and partners

2. Architecture Domains• Which of the four Architecture Domains is most important to your sponsors

and stakeholders?– Business, Data, Application, Technology

3. Vertical Scope or Level of Detail• To what level of detail (depth) should the architecting effort go?

4. Time Period• How much time have you got?



• The order of phases in the ADM may be varied according to the maturity of the enterprise architecture discipline

– Especially when establishing an Enterprise Architecture Capability

– First, your sponsors may have an urgent need to create anEnterprise-Level Baseline Technology Inventory and Roadmap(Phase D)

– Then: your sponsors may want anEnterprise-Level Baseline Business Application Inventory and Roadmap(Phase C)

– Then: you might create anEnterprise-Level Business Function Decomposition(Phase B)



• … many good reasons to modify the ADM (continued)

– You may need to modify the ADM to integrate with existing corporate governance processes or System Development Life Cycle (SDLC) methods

– To accommodate Request for Proposal (RFP) processes

– To accommodate implementation of an Enterprise Resource Planning (ERP) package, where the business has decided to adopt the business processes implemented in the package

• However, Preliminary Phase and Phase A: Architecture Vision are probably always required


Architecture Development Architecture Governance Framework (Conceptual)

The Architecture Governance Framework is integral to the Enterprise Continuum, and manages all content relevant to architecture itself and

architecture governance processes.


Architecture DevelopmentGovernance and the ADM

• The ADM is a core competency for the architecture function– The ADM process must be continuously managed – and measured – in

accordance with a defined governance strategy

• The Architecture Board must endorse the ADM and any modifications


Summary

This training module provided a high-level overview of the

TOGAF 9.1 Architecture Development Method (ADM)

Time for Review!


Review

• What one word describes the ADM?

• What five things describe every ADM Phase?

• What are the ‘Architecture Domains’?

• Is it possible to modify the ADM?