THE-OPEN-GROUP-OGB-001 Practice Questions

Phase C: Information Systems Architectures is where the detailed architecture for data and applications is developed. Specifically, during the Data Architecture portion of Phase C, high-level information concepts, often captured in an information map from Phase B (Business Architecture), are refined and translated. This process involves creating formal data models (conceptual, logical, and eventually physical) to describe the structure, relationships, and management of an organization's data assets in support of the business architecture.

A. Phase A focuses on establishing the Architecture Vision and scope, which is too high-level for detailed data modeling.

B. Phase E is concerned with identifying implementation opportunities and solutions, not developing the core data architecture.

C. The Preliminary Phase prepares the organization for architecture work; it does not involve creating architecture content like data models.

1. The Open Group Standard

TOGAF® Standard

Version 9.2

Chapter 8: Phase C: Information Systems Architectures — Data Architecture. Section 8.4

"Steps

" details the development of the Target Data Architecture

which includes creating formal data models.

2. The Open Group Standard

TOGAF® Standard

Version 9.2

Chapter 35: Architecture Content Framework. Section 35.2.4

"Data Architecture Artifacts

" lists Conceptual

Logical

and Physical Data Models as key artifacts created during Phase C.

3. The Open Group Standard

TOGAF® Standard

Version 9.2

Chapter 8: Phase C: Information Systems Architectures — Data Architecture. Section 8.5

"Outputs

" lists "Target Data Architecture" which includes these data models as key deliverables of this phase.

A business model is a conceptual framework that describes the rationale of how an organization creates, delivers, and captures value. This definition, popularized by Osterwalder and Pigneur, is explicitly adopted within The Open Group's literature. It encompasses the organization's value proposition, customer segments, channels, revenue streams, and cost structure. It serves as a high-level blueprint that connects business strategy to the enterprise architecture, explaining the fundamental logic of how the business intends to succeed and remain profitable.

B. This describes an Application Architecture, which focuses on the portfolio of applications, their interactions, and their relationships to the core business processes, not the overarching value logic.

C. This describes a business asset inventory or catalog, which is a component or an output of the Business Architecture phase, but not the complete business model itself.

D. This describes a process maturity or governance framework, such as COBIT or CMMI, which are used to assess and improve processes, rather than defining the core business logic.

1. The Open Group

TOGAF® Series Guide: Business Models (G18A)

January 2019. Section 2.1

"What is a Business Model?"

directly states: "A business model describes the rationale of how an organization creates

delivers

and captures value".

2. The Open Group

TOGAF® Standard

Version 9.2 (C182)

April 2018. Chapter 8

"Phase B: Business Architecture"

distinguishes the business model from other architectural domains. For example

Section 8.1 describes the Application Architecture (Option B) as a separate domain.

3. Osterwalder

A.

& Pigneur

Y. (2010). Business Model Generation: A Handbook for Visionaries

Game Changers

and Challengers. John Wiley & Sons. The foundational definition used by The Open Group is sourced from this peer-reviewed and widely accepted academic and professional work. (Referenced in the TOGAF® Series Guide: Business Models).

The TOGAF Business Scenario method is often executed through a series of iterative workshops. The TOGAF Series Guide on Business Scenarios explicitly states that each workshop should be treated as a mini-project. The Planning Step is crucial for this, as it involves defining the scope, objectives, participants, and schedule for the iteration. This planning activity establishes the necessary framework and controls to manage the iteration as a self-contained project with clear goals and deliverables, ensuring a structured and managed approach to its execution.

A. Documenting Step: This step focuses on recording the outputs and requirements identified during the scenario development, not on the management or planning of the iteration itself.

B. Reviewing Step: This is a quality assurance activity for validating the scenario with stakeholders. It is a part of the mini-project, not the step that manages it.

C. Gathering Step: This is the information collection phase. While a critical part of the process, it does not encompass the overall project management of the iteration.

1. The Open Group

"TOGAF® Series Guide: Business Scenarios" (G176)

January 2017. Section 3.3

"Running the Business Scenario Method"

states: "The Business Scenario method is best run as a series of workshops. Each workshop should be treated as a mini-project with a defined scope

objectives

inputs

and outputs... A plan for the workshop should be created..."

2. The Open Group

"The TOGAF® Standard

Version 9.2

" Van Haren Publishing

2018. Chapter 26

"Business Scenarios"

Section 26.4

mentions the need for "careful planning" for Business Scenario workshops

reinforcing the importance of a dedicated planning activity.

This model is a business capability heat map, which visually represents the maturity level or performance of different business capabilities against a desired target. According to the provided key:

Red (R) signifies a gap of two or more levels, indicating areas needing immediate attention. These are Market Planning, Government Relations Management, and HR Management.

Yellow (Y) signifies a gap of one level, indicating issues of a lower priority. These are Partner Management, Customer Management, and Training Management.

Purple (P) signifies a missing capability. This applies to Agent Management, which does not exist.

Option B is the only statement that accurately aligns with this analysis of the heat map.

A: This option is incorrect because it wrongly identifies Policy Management and Account Management (both Green, meaning 'level achieved') as needing attention.

C: This option incorrectly assigns "immediate attention" to the Yellow capabilities and misinterprets Purple as "not yet assessed" instead of "missing".

D: This option is incorrect because it claims Training Management (Yellow) needs the most attention among Supporting capabilities, whereas HR Management is Red.

1. The TOGAF® Series Guide: Business Capabilities (G189)

Section 4.3

Assess Business Capabilities. This section describes the process of assessing capabilities

stating

"The results of the assessment are often visualized in the form of a heat map...". Figure 6 in the guide provides a direct example of a heat-mapped capability map where colors like Red

Amber (Yellow)

and Green are used to denote the assessment status

validating the technique used in the question.

2. The TOGAF® Standard

Version 9.2

Chapter 8

Phase B: Business Architecture. Section 8.2.4

"Approach

" discusses identifying required capabilities and performing a gap analysis between the baseline and target. The heat map in the question is a standard output of such a gap analysis

visually representing the gaps that need to be addressed.

3. The Open Group Guide: Open Business Architecture (O-BA) Part I

A Pocket Guide (G171)

Section 3.3.2

Capability Maps. This guide explains that capability maps can be "adorned with additional information" such as maturity assessments. It notes that heat-mapping is a common technique to "highlight capabilities that are performing well versus those that are under-performing

" which is precisely what the model in the question illustrates.

In TOGAF value stream notation, element 7 typically represents the Outcome - the final result or benefit delivered to the stakeholder at the end of the value stream. This aligns with TOGAF's definition where outcomes represent the tangible or intangible results that create value for stakeholders through the execution of value stream stages.

B. Viewpoint - Refers to perspective frameworks in architecture views, not value stream elements.

C. Value - Represents what flows through the stream, typically shown earlier in the diagram.

D. Concern - Relates to stakeholder interests in architecture development, not value stream notation.

d in the URL

I must rely on standard TOGAF and Open Group definitions of value stream elements. In TOGAF's value stream methodology

the typical elements include:

- Value items (what flows through the stream)

- Stakeholders (who participates)

- Value-adding stages (transformation steps)

- Outcomes (results delivered)

Element position 7 in standard value stream diagrams typically represents the final deliverable or result.

Correct Answer: A

Explanation: In TOGAF value stream notation

element 7 typically represents the Outcome - the final result or benefit delivered to the stakeholder at the end of the value stream. This aligns with TOGAF's definition where outcomes represent the tangible or intangible results that create value for stakeholders through the execution of value stream stages.

Why Incorrect Options are Wrong:

B. Viewpoint - Refers to perspective frameworks in architecture views

not value stream elements.

C. Value - Represents what flows through the stream

typically shown earlier in the diagram.

D. Concern - Relates to stakeholder interests in architecture development

not value stream notation.

References:

1. The Open Group

"TOGAF® Standard

Version 9.2

" Section 6.3.8 Value Streams

pp. 89-92

2. The Open Group

"TOGAF® Series Guide: Value Streams

" Document Number: G187

Section 2.2

pp. 15-18

3. The Open Group Architecture Framework documentation on Business Architecture

Chapter 8: Value Stream Mapping

The primary purpose of mapping business capabilities to value stream stages is to establish a clear line of sight between what an organization does (its capabilities) and how it delivers value to stakeholders (its value streams). This cross-mapping is a critical analytical technique that reveals which capabilities are essential to execute each stage of a value stream. By understanding these dependencies, architects and planners can identify and prioritize the most critical capabilities for investment, improvement, or transformation, ensuring that resources are focused on the areas that most directly impact value creation.

A. This describes a fundamental characteristic of a business capability (being independent of organizational structure), not the purpose of mapping it to a value stream.

C. This describes a service-oriented view of the business, which is a different architectural perspective from the specific goal of capability-to-value-stream mapping.

D. This describes the purpose of creating a business capability map itself (i.e., organizing capabilities), not the specific act of cross-mapping them to value streams.

1. The Open Group

TOGAF® Series Guide: Value Streams (Document No. G178)

January 2017.

Section 4.4

"Value Stream and Business Capability Cross-Mapping

" Page 13: "Cross-mapping value streams to business capabilities identifies which capabilities the business needs to support a given value stream. This cross-mapping provides the context for defining which business capabilities are most critical to the business..." This directly supports the chosen answer.

2. The Open Group

TOGAF® Series Guide: Business Capabilities

2nd Edition (Document No. G211)

October 2021.

Section 4.3

"Using Business Capabilities with Other Business Architecture Disciplines

" Page 16: "Mapping business capabilities to value streams helps an organization understand what it needs to be able to do to deliver value to its stakeholders. This provides the basis for IT investment decisions by showing which business capabilities are most important."

3. The Open Group

The TOGAF® Standard

10th Edition

Content Framework

April 2022.

Section 30.3.2

"Business Architecture Catalog

Diagram

and Matrix Content

" Value Stream/Capability Matrix: The description of this matrix states its purpose is to show "the relationship between value streams and business capabilities" and is used to "determine the business capabilities required to support a value stream." This aligns with identifying critical capabilities for value delivery.

The detailed assessment of business capability gaps occurs in Phase B: Business Architecture. The primary objective of this phase is to develop the Target Business Architecture that shows how the enterprise will realize the Architecture Vision. A critical step within Phase B is to conduct a formal gap analysis between the Baseline and Target Business Architectures. This analysis identifies the specific business capabilities that need to be created, augmented, or retired to achieve the target state, thus forming the basis for subsequent architecture and implementation work.

A. Preliminary Phase: This phase focuses on establishing the architecture capability and tailoring the TOGAF framework; it does not involve detailed content-specific gap analysis.

B. Phase A: This phase, Architecture Vision, establishes the scope and high-level vision. While it may identify high-level business challenges, it does not perform a detailed capability gap assessment.

C. Phase C: This phase, Information Systems Architectures, conducts gap analysis for Data and Application architectures, not for business capabilities, which are an input from Phase B.

---

1. The Open Group. (2018). The TOGAF® Standard

Version 9.2. Van Haren Publishing.

Section 7.1

"Phase B: Business Architecture - Objectives": States an objective is to "develop Target Business Architectures... identifying candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures".

Section 7.5

"Phase B: Business Architecture - Steps": Step 6 is "Conduct formal gap analysis". This step explicitly details the process of comparing the Baseline and Target Business Architectures to identify gaps

which are foundational to defining the required business capabilities.

2. The Open Group. (2022). The TOGAF® Standard

10th Edition

ADM Guide.

Chapter 7

"Phase B: Business Architecture": Reaffirms the role of Phase B. Section 7.5

Step 6

"Conduct formal gap analysis"

describes using the gap analysis technique to compare the baseline and target states

with a focus on business-level items such as capabilities

processes

and roles. The output is a clear understanding of the capabilities to be addressed.

The Architecture Vision (Phase A) establishes a high-level view of the target architecture to address business goals and stakeholder concerns. To create this vision, it is essential to understand the fundamental structure and strategic context of the business. Business capabilities define what the business does, value streams describe how it delivers value to stakeholders, and organization maps show who is involved. These three concepts provide the strategic, high-level business context necessary to scope the architecture effort and create a compelling vision that aligns with business strategy, making them the most appropriate considerations for this initial ADM phase.

A. Business use-cases, event diagrams, and class models are detailed artifacts typically developed in later ADM phases (Phase B and C) to describe specific behaviors and data structures, not the high-level strategic vision.

C. Business data models, roles, and detailed business processes are granular components of a full Business Architecture (Phase B) and Data Architecture (Phase C), developed after the high-level vision is established.

D. An information exchange matrix, class models, and node connectivity diagrams are technical artifacts belonging to the Application and Technology Architecture domains (Phase C and D), not the business-focused Architecture Vision phase.

1. The TOGAF® Standard

Version 9.2

Section 6.3 (Phase A: Architecture Vision

Inputs): This section lists "Business capability maps" and "Value stream maps" as key inputs from the business strategy that inform the Architecture Vision. This directly supports the inclusion of business capabilities and value streams.

2. The TOGAF® Series Guide: Value Streams

Section 1.2 (Introduction): States

"Value streams provide a critical contribution to the Business Architecture. They are a key element of the TOGAF Architecture Vision and the primary mechanism for decomposing the business to a level that is relevant to the architecture."

3. The TOGAF® Series Guide: Business Capabilities

Section 2.2 (Business Capabilities and the TOGAF ADM): Explains that capability-based planning is a core technique used in the Preliminary Phase and Phase A (Architecture Vision) to focus on business outcomes. It notes

"Capability-based planning is a powerful mechanism for creating the Architecture Vision..."

4. The TOGAF® Standard

Version 9.2

Section 35.2.3 (Business Architecture Artifacts): Lists "Organization Map

" "Value Stream Map

" and "Capability Map" as core artifacts of the Business Architecture. Understanding these at a high level is fundamental to establishing the scope and context in Phase A.

Business capability modeling is the practice of identifying, defining, and structuring what a business does to achieve its objectives. The primary and definitive end product of this activity is a business capability map. This map provides a complete, stable, and visual representation of the enterprise's capabilities, organized hierarchically. It serves as a foundational artifact in business architecture, enabling strategic planning, investment analysis, and transformation efforts by showing what the business does, independent of how (processes) or who (organization) does it.

A. A value stream stages catalog is an output of value stream mapping, which focuses on how an organization delivers value to stakeholders, not on its inherent abilities.

B. A business process model is an output of business process analysis and describes the sequence of activities (the "how") used to execute work, which is distinct from a capability (the "what").

C. An organizational map (or org chart) illustrates the formal reporting structure of the business (the "who") and is intentionally decoupled from business capabilities to ensure stability.

1. The Open Group

TOGAF® Series Guide: Business Capabilities (G189)

January 2019. In Section 3.1

"What is a Business Capability Map?"

it states

"A business capability map is a visual representation of all the business capabilities of an enterprise. It is the primary artifact created during business capability modeling." (Page 10).

2. The Open Group Standard

TOGAF® Standard

Version 9.2

April 2018. In Part IV

Section 35.2.10

"Business Capability Map"

the standard defines this artifact as a key part of the Architecture Content Framework

describing it as a diagram that represents the business capabilities of an organization.

3. The Open Group

TOGAF® Series Guide: Business Scenarios (G175)

October 2017. Section 3.3 discusses using business capabilities as a technique within business scenarios

reinforcing that the map of these capabilities is the central artifact for analysis.

An information map provides a business-level view of the information assets used within an enterprise. According to the TOGAF® Standard, its fundamental definition is a collection of information concepts and the relationships between them. This artifact is crucial in the Business Architecture phase for understanding the key information entities that the business uses, such as customer, product, or order, and how they are interconnected, independent of any specific technology or application implementation. It helps stakeholders to visualize and agree upon the information landscape.

A. This describes a target information architecture view, which is a potential use of an information map, but not its core definition.

C. This describes an organization map, which links business units to other architectural elements like capabilities, not an information map.

D. This describes a data distribution map or a system/data matrix, which focuses on the physical or logical location of data, not the conceptual business view.

1. The Open Group Standard

TOGAF® Standard

Version 9.2 (Document No. C182)

Chapter 23

"Architecture Content Framework"

Section 23.4.1

"Information Map Catalog". The text states

"An Information Map is a collection of information concepts and their relationships to one another."

2. The Open Group

TOGAF® Business Architecture Level 1 Study Guide

2nd Edition (Document No. G183)

Section 3.4.2

"Information Map". This guide reiterates the definition: "An information map is a collection of information concepts and their relationships to one another."