OG0-093 TOGAF 9 Combined Part 1 and Part 2 Questions and Answers

Phase A

Phase B

Phase H

Preliminary Phase

Requirements Management

Business and Technology

Information and Knowledge

Baseline and Transition

Vision and Requirements

Capability and Segment

a list of responsibilities for running an Architecture Board

a model for governance including process, content and context

guidance for establishing an Architecture Capability using the ADM

the Architecture Compliance review process and checklists

Preliminary Phase

Phase A

Phase D

Phase G

Phase H

Phase D: Technology Architecture

Phase A: Architecture Vision

Requirements Management

Phase B: Business Architecture

Preliminary Phase

Creating the Architecture Vision deliverable

Preparing a consolidated Gap Analysis

Developing the Architecture Contract

Defining a set of Architecture Principles

Version 0.1

Version 0.7

Version 1.0

Version 0.9

Version 0.5

To allow an enterprise to exploit the latest trends in technology

To enable the CIO to take effective control of the business units across an enterprise

To ensure compliance in an enterprise to corporate auditing standards

To optimize an enterprise into an environment that is responsive to business needs

To provide a set of standards that all actors must adhere to within an enterprise

Preliminary Phase

Phase A

Phase E

Phase G

Phase H

Identifying relationships between management frameworks

Identifying stakeholders and their concerns

Identifying the business transformation risks for an architecture project

Identifying criteria for procurement activities

Identifying work packages for inclusion in the Architecture Roadmap

To describe how an architecture addresses stakeholder concerns

To identify and understand business requirements

To classify architecture and solution assets

To coordinate with the other management frameworks in use

Requirements Management

Phase D

Phase F

Phase G

Phase H

architecture view, stakeholders

architecture viewpoint, stakeholders

architecture viewpoint, architecture views

architecture view, requirements

architecture view, concerns

Architecture

Artifact

Deliverable

Model

View

Phase A

Phase E

Phase F

Phase G

Phase H

An application

An architecture viewpoint

A building block

A deliverable

A solution architecture

Phase E

Phase F

Phase G

Phase H

Preliminary Phase

A change driven by a requirement to derive additional value from the existing investment

A change driven by a requirement to increase investment in order to create new value for exploitation

A change driven by a requirement to reduce investment

A change driven by a requirement to re-align with the business strategy

A change driven by a requirement to simplify communication between stakeholders

Application Platform Interface

Artifact

Building Block

Deliverable

Framework

To determine if the organization is ready to undergo change

To determine if the stakeholders support the implementation plan

To ensure that there are adequate trained engineers to develop the solution

To ensure that there is sufficient funding to execute the transformation

To plan the migration steps needed to achieve the transformation

The artifacts are transformed into solution architectures

The artifacts become increasingly product focused

The artifacts become increasingly generic and re-usable

The artifacts evolve from generic architectures to organization-specific architectures

The artifacts evolve from common systems architectures to foundation architectures

Application Architecture

Business Architecture

Data Architecture

Technology Architecture

Transition Architecture

To determine service levels for the architecture

To establish quality metrics for the architecture

To identify commercial building blocks to be purchased

To identify missing functionality

To validate nonfunctional requirements

Building blocks at a functional level are known as Solutions Building Blocks

Solutions Building Blocks are selected in Phases A, B, C and D

The specification of a building block should be loosely coupled to its implementation

The gap analysis technique should be used to identify building blocks for re-use

Architecture Landscape

Architecture Vision

Enterprise Continuum

Governance Log

Standards Information Base

A common vocabulary

A list of recommended standards

A method for designing an information system in terms of building blocks

A set of structures which can be used to develop a broad range of architectures

A system development lifecycle method for software engineering

Building Blocks

Frameworks

Application Platform Interfaces

Deliverables

Artifacts

Architecture Requirements Specification

Implementation Governance Model

Architecture Roadmap

Implementation and Migration Plan

Communications Plan

The review of business requirements within the TOGAF ADM

The prioritization and disposal of architecture requirements

The management of architecture requirements throughput the ADM cycle

The development of requirements that deliver business value

The development of requirements for ADM Phase A

Business Scenarios

Capacity Measurement

Change Management

Measuring Business Growth

Defining an architecture that can be understood by the stakeholders

Defining an architecture that is complete and consistent

Defining an architecture that is stable

Defining data entities that are normalized to minimize update anomalies

Defining data entities relevant to the enterprise

TOGAF Core

TOGAF Mandated

TOGAF Recommended

TOGAF Referenced

TOGAF Supporting

TOGAF Guidelines and Techniques

TOGAF Recommended

TOGAF Supporting

TOGAF Extension

Establish the resources for architecture governance

Develop the Target Technology Architecture

Ensure conformance for the target architecture

Operate the governance framework

Finalize the Implementation and Migration Plan

Name

Statement of Principle

Rationale

Enforcement Policy

Implications

A log of the governance activity related to architecture requirements.

The parameters and structures to support governance of architecture requirements.

A set of guidelines, templates, and patterns to support the development of architecture requirements.

The architecture requirements which have been agreed with the Architecture Board.

establish quality parameters for the architecture

identify potential missing or overlapping functions

validate nonfunctional requirements

identify commercial building blocks to be purchased

determine the required service levels for the architecture

nonconformant solution building blocks

an error has occurred and the architecture must be re-evaluated

requirements have not been properly documented

functionality that should be eliminated

a new function that must be built or procured

The Capability Maturity Model

The Document Categorization Model

The Integrated Infrastructure Information Model

The Organizational Model for Enterprise Architecture

The Technical Reference Model

Phase A: Architecture Vision

Phase E: Opportunities and Solutions

Phase B: Business Architecture

Phase D: Technology Architecture

Phase F: Migration Planning

OrganizationalMetamodel, Architecture Capability, Architecture Landscape, Best Practices, Reference Library, Compliance Strategy.

ArchitectureMetamodel, Organizational Capability Model, Application Landscape, SIB, Reference Library, Governance Model.

BusinessMetamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log.

ArchitectureMetamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log.

Defining the Strategic Business Plan

Describing the Baseline Business Architecture

Developing the Target Business Architecture

Selecting relevant viewpoints for key stakeholders "Pass Any Exam. Any Time."

Common Systems Architecture

Foundation Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Ensure conformance requirements for the target architecture are defined

Develop the Implementation and Migration Plan

Operate the governance framework

Establish the architecture governance processes

Develop the Architecture Vision document

Part II: Architecture Development Method

Part III: ADM Guidelines and Techniques

Part IV: Architecture Content Framework

Part VI: TOGAF Reference Models

Part VII: Architecture Capability Framework

Segment Architectures, and Capability Architectures

Solution Architectures, and Corporate Architectures

Gap Architectures, and Target Architectures

Transitional Architectures, and Incremental Architectures

Baseline Architectures, and To Be Architectures

To define the capabilities of the organization

To communicate the technical readiness of the project

To evaluate the readiness of the organization to undergo change

To produce a new Request for Architecture Work

A method for controlling change at an enterprise-wide level

A method for developing an organization-specific architecture

A method for managing architecture requirements

A method for classifying architectures and solutions

A method for creating an Architecture Repository

To act as a deliverable container for artifacts created during a project

To ensure that architecture information is communicated to the right stakeholders at the right time

To provide a high-level view of the end architecture product

To govern the architecture throughout its implementation process

To show progression of change from the Baseline Architecture to the Target Architecture