OG0-091 TOGAF 9 Part 1 Questions and Answers

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

A document that triggers the start of an architecture development cycle

A qualitative view of the solution to communicate the intent of the architect

A quantitative view of the solution to measure the implementation

A record of deviations from the planned architectural approach

Architecture

Metamodel

Model

Ontology

Pattern

Addressing requirements

Disposal of resolved requirements

Generating requirements

Managing the flow of requirements

Prioritizing requirements

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 keep the Architecture Review Board informed of changes to the architecture

To ensure that the outcomes of a Compliance Assessment are distributed to the members of the Architecture Review Board

Architecture governance

Business imperatives

Solution architecture

Service level agreements

Time horizon

Architecture Repository

Architecture Requirements

Implementation and Migration plan

Standards Information Base

Strategic Architecture

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

They are used to define the framework and detailed methodologies

They are used to define stakeholders and their concerns

They are used to determine the readiness factors impacting the organization

They are used to guide decision making within the enterprise

They are used to resolve and dispose of requirements

Capability, Segment, Enterprise, Federated

Business, Data, Application, Technology

Application, Data, Information, Knowledge

Process, Organization, Strategic, Requirements

Baseline, Candidate, Transition, Target

Reviewing business requirements

Addressing and prioritizing architecture requirements

Developing requirements that deliver business value

Validating requirements between ADM phases

Managing architecture requirements throughout the ADM cycle

Preliminary Phase and Phase A

Phases B, C, and D

Phase E

Phase F

Phases G and H

Phase A

Phase E

Phase F

Phase G

Phase H

Architecture viewpoint

Diagram

Catalog

Matrix

Architecture view

Architecture Road map

Architecture Requirements Specification

Communications Plan

Implementation and Migration Plan

Implementation Governance Model

To aid communication and understanding between architects

To coordinate with the other management frameworks in use

To describe how an architecture addresses stakeholder concerns

To evaluate how best to develop and implement an architecture

To help identify and understand business requirements

robustness

consistency

completeness

stability

understandability

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Finalize the Implementation and Migration Plan

Establish the recourses for architecture governance

Ensure conformance for the target architecture

Operate the governance framework

Develop the Target Technology Architecture

Phase A

Phase B

Phase H

Preliminary Phase

Requirements Management

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Standards Information Base

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

Data

Capability

Segment

Transition

Vision

viewpoint, views

viewpoint, stakeholders

view, concerns

view, stakeholders

view, requirements

view, concerns

viewpoint, views

view, requirements

view, stakeholders

An agreement between development partners and the sponsor on architecture deliverables

A description of how the new capability will address stakeholder concerns

A description of the scope and approach for completion of the architecture project

A set of quantitative statements outlining requirements on the implementation

A set of rules and guidelines to support fulfilling the mission of the organization

A business planning technique that focuses on business outcomes

A business planning technique that focuses on horizontal capabilities

A business planning technique that focuses on vertical capabilities

A human resource planning technique that focuses on capable architects

TOGAF Core

TOGAF Extension

TOGAF Mandatory

TOGAF Recommended

TOGAF Supporting

The organization must utilize an architecture tool in order to tailor the templates for use

It must be adapted to satisfy organization specific requirements

It can be utilized by most enterprises without further customization

It can only be used for enterprise level architecture projects

It should only be employed under the supervision of highly trained consultants

Application Architecture

Business Architecture

Data Architecture

Technology Architecture

Rational, Explained, Precise, Stated, Identifiable

Comprehensive, Future proof, Short, Concise, Consistent

Open, Enabling, Flexible, Agile, Dynamic

Stable, Understandable, Complete, Robust, Consistent

ensuring consistency between sub-architectures

approving the strategic business plans proposed by individual organization units within the enterprise

enforcement of architecture compliance

identifying and approving components for reuse

providing the basis for all decision-making with regard to changes to the architecture

A checklist for compliance reviews

An evaluation tool to select vendors to conduct a proof of concept demonstration

A tool for calculating detailed cost estimates

A tool for project planning the implementation activities

A tool for selling the benefits of the proposed capability to stakeholders

a complete ADM cycle

a complete re-architecting change

a full revision of the enterprise architecture

an incremental change

a simplification change

Part I describes the TOGAF approach to Enterprise Architecture

Part II describes the definitions of terms used and the changes between versions of TOGAF

Part III describes requirements management and is considered to be the core of TOGAF

Part IV describes the ADM: a collection of guidelines and techniques used in TOGAF 9

An agreement between development partners and sponsors on the deliverables

A description to allow measurement of the compliance of the implementation

A description to communicate the intent of the architect

A document that triggers the start of an architecture development cycle

A set of general rules and guidelines

Application, Business, Data, Technology

Capability, Segment, Strategic

Context, Definition, Governance, Transformation

Definition, Realization, Transition, Vision

Architecture Maturity Models

Business Scenarios

Gap Analysis

Mind Maps

SWOT Analysis

Architecture Capability

Architecture Landscape

Architecture Metamodel

Governance Log

Reference Library

Boundaryless Information Flow

Interoperability

Portability

Service Oriented Architecture

Semantic Web

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