OG0-091 TOGAF 9 Part 1 Questions and Answers

Common Systems Solutions

Strategic Solutions

Industry Solutions

Organization-Specific Solutions

Foundation Solutions

defining architecture principles

defining relationships between management frameworks

defining the enterprise

evaluating the enterprise architecture maturity

identifying stakeholders and their concerns

It is used to coordinate with the other management frameworks in use

It is used to describe how an architecture addresses stakeholder concerns

It is used to identify and understand business requirements

It is used to provide a system for continuous monitoring

It is used to structure re-usable architecture and solution assets

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

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

The Architecture Repository

The Enterprise Continuum

The Integrated Information Infrastructure Model

The TOGAF Technical Reference Model

Common Systems Architectures

Foundation Architectures

Industry Architectures

Organization-Specific Architectures

Business scenario

Impact analysis

Mission statement

Requirements analysis

Solution architecture

consumer

CxOs

lead architect

sponsor

stakeholder

Architecture Capability

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Name

Statement of Principle

Rationale

Enforcement Policy

Implications

A common vocabulary

A list of recommended standards

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

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

A system development lifecycle method for software engineering

an agreement between development partners and sponsors on the architecture deliverables

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

a set of general rules and guidelines to support development of the enterprise architecture

a timeline showing progression from the Baseline Architecture to the Target Architecture

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

Architecture Change Management

Implementation governance

Migration planning

Preliminary Phase

Requirements Management

Capability Architecture

Operational Architecture

Segment Architecture

Strategic Architecture

Tactical Architecture

To create the initial version of the Architecture Roadmap

To develop a vision of the business value to be delivered by the proposed enterprise architecture

To select and implement tools to support the Architecture Capability

To obtain approval for the Statement of Architecture Work

To document the baseline 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

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

Business Scenarios

Gap Analysis

Interoperability Analysis

Requirements Management

Architecture Principles

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

Develop an Architecture Roadmap

Populate the Architecture Repository

Populate the Enterprise Continuum

Use the Architecture Development Method

Use the Implementation Governance Phase

To confirm the ability of the enterprise to undergo change

To demonstrate how stakeholder concerns are addressed in the Business Architecture

To develop a Target Technology Architecture to support the business

To finalize the Architecture Vision and Architecture Definition documents

To maximize the business value from the architecture

Architecture Roadmap

Statement of Architecture Work

Architecture Landscape

Request for Architecture Work

Architecture Vision

Architecture Road map

Architecture Requirements Specification

Communications Plan

Implementation and Migration Plan

Implementation Governance Model

Application Architecture

Business Architecture

Data Architecture

Technology Architecture

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

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

They are equivalent to software component objects or web services

They may have multiple implementations but with different, interdependent Building Blocks

They may be assembled from other Building Blocks

An architecture of a commercial organization

An architecture that consists of more than one subsidiary company

An architecture that crosses multiple systems, and multiple functional groups within the enterprise

The highest level of architecture that can be achieved in a given organization

Implications

Name

Rationale

Statement

Part I, the Enterprise Continuum, describes a model for structuring a virtual repository

Part II, the Architecture Development Method, describes the definitions of terms used in TOGAF, and the changes between versions of TOGAF

Part III, Tools and Support, describes a collection of guidelines and techniques used in the other parts of TOGAF

Part VI, TOGAF Reference Models, includes a model for release management of the TOGAF specification

Part VII, the Architecture Capability Framework, describes processes and skills to establish an enterprise function

To define and plan an enterprise architecture transformation based on Capability-Based Planning

To develop a set of general rules and guidelines for the architecture being developed

To develop a set of security guidelines for the architecture being developed

To help identify and understand the business requirements that an architecture must address

To identify and mitigate the risks when implementing an architecture project

Design a viewpoint to address all stakeholder concerns

Develop views for the target architecture first

Ensure completeness of the architecture

Refer to existing libraries of viewpoints, to identify one for re-use

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

An approach to ensure the effectiveness of an organization's architectures

An architecture of building blocks and corresponding standards, together with associated graphics

An example set of Architecture Principles

A reference model that includes information provider applications and brokering applications

A model intended to assist with the release management of the TOGAF specification itself

viewpoint, views

viewpoint, stakeholders

view, concerns

view, stakeholders

view, requirements

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

Phases E and F

Preliminary Phase

Phase B, C, and D

Phase G and H

Phase A

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

Capability

Segment

Technology

Transition

Vision

view, concerns

viewpoint, views

view, requirements

view, stakeholders

The development of requirements that deliver business value

The management of architecture requirements throughout the ADM cycle

The review of business requirements within the TOGAF ADM

The prioritization and disposal of architecture requirements

The development of requirements for ADM Phase A.