Togaf 9 Foundation Study Guide - Chapter 5

Front 1

How does the ADM support the concept of iteration?

Back 1

1. Cycling around the ADM
2. Iterating between phases
3. Cycling around a single phase

Front 2

Describe "Cycling around the ADM".

Back 2

The ADM is presented in a circular manner indicating that the completion of one phase of architecture work directly feeds into subsequent phases of architecture work.

Front 3

Describe "Iterating between phases"

Back 3

TOGAF describes the concept of iterating across phases (e.g., returning to Business Architecture on completion of Technology Architecture).

Front 4

Describe "Cycling around a single phase"

Back 4

TOGAF supports repeated execution of the activities within a single ADM phase as a technique for elaborating architectural content.

Front 5

Summarize the architecture development method activities for the preliminary phase

Back 5

Prepare the organization for successful TOGAF architecture projects.

Undertake the preparation and initiation activities required to create an Architecture Capability, including the customization of TOGAF, selection of tools, and the definition of Architecture Principles.

Front 6

What phase of the ADM can be summarized as:

Prepare the organization for successful TOGAF architecture projects.

Undertake the preparation and initiation activities required to create an Architecture Capability, including the customization of TOGAF, selection of tools, and the definition of Architecture Principles.

Back 6

Preliminary phase

Front 7

Summarize the architecture development method activities for Requirements Management

Back 7

Every stage of a TOGAF project is based on and validates business requirements.

Requirements are identified, stored, and fed into and out of the relevant ADM phases, which dispose of, address, and prioritize requirements.

Front 8

What phase of the ADM can be summarized as:

Every stage of a TOGAF project is based on and validates business requirements.

Requirements are identified, stored, and fed into and out of the relevant ADM phases, which dispose of, address, and prioritize requirements.

Back 8

Requirements Management

Front 9

Summarize the architecture development method activities for Phase A

Back 9

- Set the scope, constraints, and expectations for a TOGAF project.
- Create the Architecture Vision.
- Identify stakeholders.
- Validate the business context and create the Statement of Architecture Work.
- Obtain approvals.

Front 10

What phase of the ADM can be summarized as:

- Set the scope, constraints, and expectations for a TOGAF project.
- Create the Architecture Vision.
- Identify stakeholders.
- Validate the business context and create the Statement of Architecture Work.
- Obtain approvals.

Back 10

Phase A: Architecture Vision

Front 11

Summarize the architecture development method activities for Phase B, C, & D

Back 11

Develop architectures in four domains:
1) Business
2) Information Systems – Application
3) Information Systems – Data
4) Technology
In each case, develop the Baseline and Target Architecture and analyze gaps.

Front 12

What phase of the ADM can be summarized as:

Develop architectures in four domains:
1) Business
2) Information Systems – Application
3) Information Systems – Data
4) Technology
In each case, develop the Baseline and Target Architecture and analyze gaps.

Back 12

Phase B: Business Architecture; Phase C: Information Systems; Architectures (Application & Data); Phase D: Technology Architecture

Front 13

Summarize the architecture development method activities for Phase E

Back 13

- Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases.

- Determine whether an incremental approach is required, and if so identify Transition Architectures.

Front 14

What phase of the ADM can be summarized as:

- Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases.

- Determine whether an incremental approach is required, and if so identify Transition Architectures.

Back 14

Phase E: Opportunities & Solutions

Front 15

Summarize the architecture development method activities for Phase F

Back 15

Develop detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.

Front 16

What phase of the ADM can be summarized as:

Develop detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.

Back 16

Phase F: Migration Planning

Front 17

Summarize the architecture development method activities for Phase G

Back 17

- Provide architectural oversight for the implementation.
- Prepare and issue Architecture Contracts.
- Ensure that the implementation project conforms to the architecture.

Front 18

What phase of the ADM can be summarized as:

- Provide architectural oversight for the implementation.
- Prepare and issue Architecture Contracts.
- Ensure that the implementation project conforms to the architecture.

Back 18

Phase G: Implementation Governance

Front 19

Summarize the architecture development method activities for Phase H

Back 19

Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise and maximizes the value of the architecture to the business

Front 20

What phase of the ADM can be summarized as:

Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise and maximizes the value of the architecture to the business

Back 20

Phase H: Architecture Change Management

Front 21

The Enterprise Continuum is an approach for...

Back 21

The Enterprise Continuum is an approach for categorizing architectural source material – both the contents of the organization's own Architecture Repository, and the set of relevant, available reference models in the industry.

Front 22

What are ADM Guidelines and Techniques?

Back 22

ADM Guidelines and Techniques is a set of resources – guidelines, templates, checklists, and other detailed materials – that directly support application of the TOGAF ADM. Described in TOGAF 9 Part III

Front 23

What is the difference between Guidelines vs. Techniques?

Back 23

Guidelines describe how the ADM process can be adapted to deal with a number of different usage scenarios, including different process styles (e.g., the use of iteration) and also specific specialty architectures (such as security).

Techniques support specific tasks within the ADM (e.g., the gap analysis technique, principles, etc.).

Front 24

True or False, It will often be necessary to modify or extend the ADM to suit specific needs.

Back 24

True

Front 25

What are some of the reasons for wanting to tailor the ADM to an individual Enterprise

Back 25

1 - The order of the phases in the ADM are dependent on the maturity of the architecture discipline within the enterprise concerned.
2 - The order of phases may also be defined by the business and architecture principles of an enterprise.
3 - To work with another enterprise architecture framework specific to a particular vertical sector: Government, Defense, e-Business, Telecommunications, etc.
4 - To tailor the ADM to reflect the relationships with, and dependencies on, the other management processes.
5 - To compromise between existing practices and the enterprise's requirements.
6 - A small-to-medium enterprise that wishes to use a “cut-down” version of the ADM.
7 - A very large and complex enterprise comprising many separate but interlinked “enterprises” where a more federated approach is required.