OG0-091 TOGAF 9 Part 1 Questions and Answers

Use the same approach as with any other capability

Regard the establishment as an ongoing practice

Apply the ADM with the specific vision to establish the practice

Treat the establishment as a one-off project

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

Requirements Management

Phase E

Phase F

Phase G

Phase H

Application

Business

Data

Technology

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

determining if the organization is ready to accept change

planning the migration steps needed to achieve the transformation

ensuring that there are adequate trained developers and engineers to implement the solution

ensuring that there is sufficient financial capacity to execute the desired transformation

determining if there is adequate stakeholder support for the implementation process

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

Capability, Segment, Enterprise, Federated

Business, Data, Application, Technology

Application, Data, Information, Knowledge

Process, Organization, Strategic, Requirements

Baseline, Candidate, Transition, Target

Phase A

Phase B

Phase C

Phase D

Phase E

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

A detailed description of the interfaces between building blocks

A way to identify combinations of building blocks that have been proven to deliver solutions

A package of functionality defined to meet the business needs the organization

A work product describing an aspect of an architecture

An implementation specific solution building block

To define the Baseline Architecture for this cycle of the ADM

To define the application systems for the Target Architecture

To define the framework and methodologies to be used

To define the relevant stakeholders and their concerns

To define and prioritise work packages

Catalog

Matrix

Diagram

View

Viewpoint

Capability Architecture

Operational Architecture

Segment Architecture

Strategic Architecture

Tactical Architecture

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Develop an Architecture Roadmap

Populate the Architecture Repository

Populate the Enterprise Continuum

Use the Architecture Development Method

Use the Implementation Governance Phase

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

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

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 Board

Architecture Review Co-ordinator

CIO

Lead Enterprise Architect

Project Leader

It contains an assessment of the current architecture requirements

It defines the scope and approach to complete an architecture project

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

It provides a high-level aspirational view of the end architecture project

It provides a schedule for implementation of the target architecture

To build a top-down, all inclusive architecture description

To enable development of reference architectures

To enable the architecture domains to be integrated

To ensure that the method is being applied correctly

Develop a Target Technology Architecture

Consolidate the Gap Analysis results from Phases B through D

Generate and gain consensus on an initial Architecture Roadmap

Coordinate the Implementation and Migration Plan with other frameworks

Operate the governance framework and manage an architecture contract

Implications

Name

Rationale

Statement

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

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Gap Analysis

robustness

consistency

completeness

stability

understandability

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

To ensure that the results of a Compliance Assessment are distributed to the Architecture Board

To request a dispensation or to kick-start a further cycle of architecture work

The ensure that information is communicated to the right stakeholders at the right time

To review project progress and ensure the implementation is inline with the objectives

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

Requirements Management

Phase D: Technology Architecture

Preliminary Phase

Phase A: Architecture Vision

Phase B: Business Architecture

Phase A

Phase E

Phase F

Phase G

Phase H

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

Business Transformation Readiness Assessment

Business Value Assessment Technique

Capability-Based Planning

Communications and Stakeholder Management

Gap Analysis

In the Integrated Information Infrastructure Reference Model

In the Standards Information Base

In the Foundation Architecture

In the Architecture Repository

Requirements Management

Phase D

Phase F

Phase G

Phase H

Architecture Landscape

Architecture Vision

Enterprise Continuum

Governance Log

Standards Information Base

Architecture governance

Corporate governance

IT governance

Technology governance

The program management office

They are most effective when they are embraced and used across the organization

They are based on enterprise principles

They are detailed policies that prescribe behaviors and requirements

Even though they may appear generic, they should be tailored to reflect an organization's culture and goals

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

addresses and resolves requirements between ADM phases

is a central process that prioritizes requirements for all ADM phases

is used to dispose of resolved requirements for all ADM phases

generates new requirements and passes them to all ADM phases

stores requirements and manages their flow into relevant ADM phases