The Open Group OG0-091 Dumps

Boundaryless Information Flow

Interoperability

Portability

Service Oriented Architecture

Semantic Web

Application

Business

Data

Technology

activity model, perspective

viewpoint, requirements

view, concerns

Node Connectivity Diagram, interconnections

Architecture trade-off analysis, constraints

Architecture governance

Corporate governance

IT governance

Technology governance

The program management office

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

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

Risk analysis is best conducted in the Architecture Vision phase so that the risk is eliminated in subsequent phases

Risk analysis should be carried out first in the Migration Planning phase

Risk analysis is outside the scope of enterprise architecture projects

Risk is pervasive in all enterprise architecture activity and should be managed in all phases of the ADM

The only risks that are within the scope of enterprise architecture are technological risks

Application, Business, Data, Technology

Capability, Segment, Strategic

Context, Definition, Governance, Transformation

Definition, Realization, Transition, Vision

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

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

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

To align it closer to the business

To make the use more realistic

To move through the cycle faster

To suit the specific needs of the enterprise

To show the evolution of deliverables

To permit adaptation as required

To enable use with the Architecture Content Framework

To support change management

Business scenario

Impact analysis

Mission statement

Requirements analysis

Solution architecture

TOGAF Core

TOGAF Extension

TOGAF Mandatory

TOGAF Recommended

TOGAF Supporting

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

Architecture Change Management

Implementation governance

Migration planning

Preliminary Phase

Requirements Management

The ARTS data model

The Integrated Information Infrastructure Reference Model

The Resource-Event-Agent model

The STEP framework

The TOGAF Technical Reference Model

are assembled; are single function components

are single function components; are groups of architecture building blocks

are reusable; are not reusable

define the architecture; provide the existing legacy system

define functionality; define the implementation of functionality

is an example and should be tailored to the needs of an organization

must be used "as is" for developing comprehensive architecture models

contains several industry specific frameworks

is intended to contain the Enterprise Continuum

contains only solution building blocks

Phase D

Phase E

Phase F

Phase G

Phase H

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 Landscape

Architecture Metamodel

Governance Log

Reference Library

Standards Information Base

To determine if the organization is ready to undergo change

To determine if the stakeholders support the implementation plan

To ensure that there are adequate trained engineers to develop the solution

To ensure that there is sufficient funding to execute the transformation

To plan the migration steps needed to achieve the transformation

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

Enabling the vision of an integrated information infrastructure

Getting information to the right people at the right time in a secure, reliable and timely manner

Enabling effective global communications between countries

Enabling the flow of information to all stakeholders

Providing a visual representation of information provider, consumer and brokering applications

A detailed description of the interfaces between building blocks

An implementation specific solution building block

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

A way to put building blocks together into context

A work product describing an aspect of an architecture

Foundation, Common Systems, Industry, Organization-Specific

Industry, Foundation, Common Systems, Organization-Specific

Organization-Specific, Industry, Common Systems, Foundation

Organization-Specific, Industry, Foundation, Common Systems

Architecture Board

Architecture Review Co-ordinator

CIO

Lead Enterprise Architect

Project Leader

A repository area that lists the set of specifications to which architectures must conform

A repository area that describes the organization specific architecture framework and method.

A repository area that defines the parameters, structures, and processes to support governance

A repository area that provides guidelines, templates, and patterns used to create new architectures

A repository area that provides a record of the governance activity across the enterprise

deliverable

matrix

building block

diagram

catalog

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

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

stability

robustness

understandability

completeness

consistency

Preliminary Phase

Phase A

Phase D

Phase G

Phase H

Procurement policies

Business scenarios

Functional Requirements

Stakeholder concerns

Architecture principles

A high-level outline architecture

A formally reviewed, preliminary architecture

A draft, detailed architecture

A formally reviewed, detailed architecture

A preliminary outline architecture

Agile,

Dynamic

Comprehensive

Robust

Strategic

A change to re-align with the business strategy.

A change to derive additional value from the existing investment.

A change to reduce costs.

A change to increase investment in order to create new value for exploitation.

Conduct formal stakeholder review

Create Architecture Definition Document

Define Roadmap components

Perform gap analysis

Select reference models, viewpoints and tools

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

Implications

Name

Rationale

Statement

An application

An architecture viewpoint

A building block

A deliverable

A solution architecture

To build a top-down, all inclusive architecture description

To enable a fast response to market changes

To verify that the method is being applied correctly

To permit the architecture domains to be integrated

To enable development of reference architectures