OG0-091 Questions and Answers

Architecture Roadmap

Statement of Architecture Work

Architecture Landscape

Request for Architecture Work

Architecture Vision

Architecture Contract

Architecture Definition Document

Architecture Vision

Request for Architecture Work

Statement of Architecture Work

Phase D

Phase E

Phase F

Phase G

Phase H

It can be used to determine the capability level of an enterprise

It is a deliverable from Phase A

It is an Application Architecture Reference Mode!

It provides a conceptual structure for architecture governance

It supports all the Common Systems Architectures

Procurement policies

Business scenarios

Functional Requirements

Stakeholder concerns

Architecture principles

It is sent form the sponsor and triggers the start of an architecture development cycle

It provides a list of work packages and a schedule for implementation of the target architecture

It defines the scope and approach to complete an architecture project

It provides a set of statements that outline what a project must do to comply with the architecture

It contains an assessment of the current architecture requirements.

Foundation Architecture

Common Systems Architecture

Industry Architecture

Organization Specific Architecture

Product Line Architecture

Requirements Management

Phase D

Phase F

Phase G

Phase H

The TOGAF Architecture Development Method mandates the use of the Technical Reference Model for large complex architecture projects

The Technical Reference Model is an integral part of the TOGAF Architecture Development Method

The Technical Reference Model should not be modified

The Technical Reference Model includes a set of graphical models and a corresponding taxonomy

The Technical Reference Model provides a direct mapping to the Zachman Framework

To review the validity of a project's Architecture Vision

To review a project for compliance to external laws and regulations

To review a project against established architecture criteria and business objectives

To ensure that stakeholder concerns are being addressed by a project

Marginal

Residual

Low

Initial

Critical

Building Block

Catalog

Diagram

Matrix

Deliverable

Capability Assessment

Change Request

Requirements Impact Analysis

Statement of Architecture Work

It contains a high level description of the business strategy for the organization

It is the key document describing how the new architecture capability will meet the business goals

It provides prerequisite knowledge for undertaking work in the other architecture domains

It mobilizes operations to support the ongoing business architecture development

It includes preparation activities such as customization of the method

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 optimise 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

Business requirements

Cultural aspirations

Forecast financial requirements

Strategic Intent

Technical elegance

Existing application models

Generic business models relevant to the organization’s industry sector

Existing IT services

Generic data models relevant to the organization’s industry sector

The Capability Maturity Model

The Document Categorization Model

The Integrated Infrastructure Information Model

The Organizational Model for Enterprise Architecture

The Technical Reference Model

Develop the Architecture Vision document

Draft the Implementation and Migration Plan

Ensure conformance requirements for the target architecture are defined

Establish the Organizational Model for enterprise architecture

Operate the governance framework

Preliminary Phase and Phase A

Phases B, C, and D

Phase E

Phase F

Phases G and H

All requirements fed into the phase are prioritized, and those of low priority are deferred until the next iteration of the ADM cycle

The phase generates the requirements for a given ADM cycle using the Business Scenario technique

The phase manages the flow of requirements, storing them, and feeding them in and out of the relevant ADM phases

The phase operates like a waiting room, and all requirements fed in to the phase must be resolved by the end of the current ADM cycle

The phase resolves the requirements that are fed into it from the other ADM phases

Version 0.5

Version 0.7

Version 1.0

Version 0.1

Version 0.9

ADM Guidelines and Techniques

Architecture Capability Framework

Architecture Development Method

Enterprise Continuum & Tools

viewpoint, views

viewpoint, stakeholders

view, concerns

view, stakeholders

view, requirements

To catch errors in a project architecture early

To guide decision making throughout the enterprise

To help identify and understand business requirements

To highlight shortfalls between the baseline and target architectures

To mitigate risk when implementing an architecture project

Resolve impacts across the Architecture Landscape

Define candidate roadmap components

Conduct formal stakeholder review

Create Architecture Definition Document

Develop Architecture Definition Document

Develop Baseline Architecture

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

To evangelize the architecture to the end user community

To govern the architecture through to implementation

To keep the Architecture Review Board informed of changes to the architecture

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

Requirements

Principles

Concerns

Architecture viewpoints

Architecture views

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 govern the architecture throughout its implementation process

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

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

It contains only solution building blocks

It contains business functions and processes specific to a particular industry sector

It contains building blocks and their corresponding standards

It includes a model of application components and application services software, including brokering applications

It includes models for common high-level business functions, such as supply chain management

Develop an Architecture Roadmap

Populate the Architecture Repository

Populate the Enterprise Continuum

Use the Architecture Development Method

Use the Implementation Governance Phase

Content

Context

Process Flow Control

Repository

Vision

Architecture Building Blocks

Components

Patterns

Re-usable Building Blocks

Solution Building Blocks

They should not be reused in other enterprise architecture projects

They should have stable, published interfaces that allow other building block to interoperate with them

They are packages of functionality intended to meet the business needs across the organization

They have defined boundaries

Addressing requirements

Disposal of resolved requirements

Generating requirements

Managing the flow of requirements

Prioritizing requirements

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

Business scenario

Impact analysis

Mission statement

Requirements analysis

Solution architecture

Organizational Metamodel, Architecture Capability, Architecture Landscape, Best Practices, Reference Library, Compliance Strategy

Architecture Metamodel, Organizational Capability Model, Application Landscape, SIB, Reference Library, Governance Model

Business Metamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log

Architecture Metamodel, Architecture Capability, Architecture Landscape, SIB, Reference Library, Governance Log

Architecture governance

Business imperatives

Solution architecture

Service level agreements

Time horizon