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

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 ActualTests.com

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

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

In the next iteration of Architecture development, you would describe the Baseline Business Architecture with a Value Chain diagram and a Baseline Business Process catalog. You would describe the Baseline Data Architecture with a Data diagram. You would describe the Baseline Application Architecture with an Environment and Location diagram.

In the next iteration of Architecture development, you would describe the Target Business Architecture with an Organization/Actor catalog, a Business Service/Function catalog and Data Lifecycle diagrams. You would describe the Target Application Architecture with an Application Interaction matrix and Application Communications diagrams.

You would describe the Baseline Business Architecture with a Business Service/Function catalog, an Organization/Actor catalog and a Data Entity/Business Function matrix. You would describe the Baseline Data Architecture using a Data Entity/Data Component catalog. You would describe the Baseline Application Architecture with an Application/Function matrix.

You would describe the Target Business Architecture with a Business Service/Function catalog, and a Business Interaction matrix. You would describe the Target Data Architecture with a Data Entity/Business Function matrix and an Application/Data matrix. You would describe the Target Application Architecture with Application Communication diagrams and an Application Interaction matrix.

Capability Architecture

Operational Architecture

Segment Architecture

Strategic Architecture

Tactical Architecture

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

Sponsor

Consumer

Lead architect

Stakeholder

It lists work packages on a timeline showing progress towards the Target Architecture

It contains an assessment of the current architecture requirements

It provides for effective communication of the end architecture project to the stakeholders

It forms the basis of a contractual agreement between the sponsor and the architecture organization

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

Architecture governance

Portfolio management

IT governance

Technology governance

Corporate governance

Architecture Viewpoint

Work Package

Metamodel

Architecture Framework

Deliverable

Business scenario

Impact analysis

Mission statement

Requirements analysis

Solution architecture

Phase A: Architecture Vision

Phase E: Opportunities and Solutions

Phase B: Business Architecture

Phase D: Technology Architecture

Phase F: Migration Planning

To create a roadmap that describes the evolution of the architecture over time

To prepare a Solution Architecture for the enterprise

To define an IT Strategy that maps out the technology infrastructure

To allocate the resources needed to implement the architecture project

To articulate an Architecture Vision

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

Preliminary Phase

Phase A

Phase B

Phase H

Requirements Management Phase

Enterprise Architecture Capability

IT Governing Board

Program Management Office

Quality Assurance department

Service Management department

An architecture of a commercial organization

An architecture that consists of more than one subsidiary company ActualTests.com

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

The Capability Maturity Model

The Document Categorization Model

The Integrated Infrastructure Information Model

The Organizational Model for Enterprise Architecture

The Technical Reference Model

To define the solution architecture needed to support the Application Architecture

To define technology components into a set of technology platforms

To define the Transition Architectures needed to achieve the Target Architecture

To develop a migration plan to deliver incremental capabilities

To select a set of technology products that will form the basis of a solution architecture

Capability

Segment

Technology

Transition

Vision

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

is used to store different classes of architectural output created by the ADM

is a categorization mechanism for classifying architecture and solution artifacts

is a detailed model of architectural work products, including deliverables and artifacts

is an architecture of generic functions and services

is a set of resources to help establish an architecture capability within an organization

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

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

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

To inform the Architecture Board of changes to the architecture

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

A description of individual change increments showing progression from the baseline to target architecture

A detailed schedule for implementation of the target architecture

A high level description of the baseline and target architectures

A joint agreement between the development team and sponsor on the deliverables and quality of an architecture

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

Foundation, Common Systems, Industry, Organization-Specific

Industry, Foundation, Common Systems, Organization-Specific

Organization-Specific, Industry, Common Systems, Foundation

Organization-Specific, Industry, Foundation, Common Systems

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

Implications

Name

Rationale

Statement

A Common Systems Architecture

A Foundation Architecture

An Industry-Specific Architecture

An Organization-Specific Architecture

A Solution Architecture

Preliminary Phase

Phase A

Phase E

Phase G

Phase H

Phase A

Phase E

Phase F

Phase G

Phase H

develop requirements for Transition Architectures that deliver business value

dispose of, address and prioritize architecture requirements

organize architecture requirements throughout the ADM cycle

review business requirements

validate requirements between ADM phases

Catalog

Matrix

Diagram

View

Viewpoint

Architecture Principles

Business Scenarios

Interoperability Analysis

Migration Planning Techniques

Risk Management Techniques

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

Agile

Dynamic

Comprehensive

Rational

Stable

Catalog

Matrix

Diagram

View

Viewpoint

Application Architecture should be developed first, then Data Architecture

Application Architecture should be developed concurrently with Data Architecture

Data Architecture should be developed first, then Application Architecture

Application Architecture and Data Architecture may be developed in either sequence

Creating the Statement of Architecture Work

Allocating resources for architecture projects

Identifying the Lead Enterprise Architect to manage an architecture compliance review

Establishing targets for re-use of components

Conducting assessments of the maturity level of architecture discipline within the organization

It highlights areas of stakeholder concern

It highlights the impacts of change

It highlights services that are yet to be developed

It highlights services that are available

It highlights different viewpoints

The organization specific architecture framework, including a method for architecture development and a metamodel for architecture content

A record of the governance activity across the enterprise

Parameters, structures, and processes to support governance of the repository

Specifications to which architecture must conform

Patterns, templates, and guidelines used to create new architectures.

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

Ensure that the enterprise’s Architecture Capability meets current requirements

Establish the value realization process

Ensure that implementation projects conform with the Target Architecture

Prioritize the projects trough risk validation

Assess the performance of the architecture and make recommendation for change

completeness

robustness

stability

consistency

understandability

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

The Architecture Repository

The Enterprise Continuum

The Integrated Information Infrastructure Model

The TOGAF Technical Reference Model