Updated Sep-2026 OGBA-101 Free Exam Files Downloaded Instantly [Q23-Q43]

An Information Map defines key business information concepts and their relationships. It remains independent of databases, applications, or physical storage, ensuring information architecture reflects business requirements instead of technical implementation decisions.

When creating value streams, it is recommended to start with customer-based value streams. Here’s a detailed explanation:
Value Streams:
Definition: Value streams represent the end-to-end activities that create value for customers or stakeholders. They provide a high-level view of how value is delivered within the organization.
Starting with Customer-Based Value Streams:
Customer Focus: Starting with customer-based value streams ensures that the architecture is aligned with the needs and expectations of the customers. This approach helps in identifying the most critical value-creating activities and aligning them with business goals.
Value Delivery: Customer-based value streams provide a clear understanding of how value is delivered from the customer’s perspective. This helps in designing processes and capabilities that enhance customer satisfaction and business performance.
TOGAF Reference:
Phase B: Business Architecture: In this phase, value streams are identified and modeled to ensure that the architecture supports the delivery of value to customers. Starting with customer-based value streams is a key activity in this phase.
Capability-Based Planning: TOGAF emphasizes the importance of aligning business capabilities with value streams to ensure that the architecture supports value creation and delivery.
Benefits:
Customer-Centric Design: Starting with customer-based value streams ensures that the architecture is designed with a focus on customer needs and value delivery.
Strategic Alignment: Aligning value streams with customer needs helps in ensuring that the architecture supports the strategic goals of the organization and enhances customer satisfaction.
In summary, when creating value streams, starting with customer-based value streams ensures a customer-centric design, aligning the architecture with the needs and expectations of the customers and supporting strategic goals.

TOGAF defines four core architecture domains: Business, Data, Application, and Technology. These domains collectively represent the key areas covered in enterprise architecture, where the Business Architecture defines business strategy and organizational goals; Data Architecture addresses data management and structure; Application Architecture focuses on system and software applications; and Technology Architecture outlines the IT infrastructure.
References: TOGAF Standard, Architecture Domains (Chapter 3).
TOGAF, as a comprehensive Enterprise Architecture framework, divides the architecture landscape into four interrelated domains:
* Business Architecture:This domain focuses on the organization’s strategic goals, business processes, and organizational structure. It defines how the business operates and creates value.
* Data Architecture:This domain deals with the structure, organization, and management of data assets within the enterprise. It includes logical and physical data models, data storage, and data security.
* Application Architecture:This domain describes the applications used to support the business, their interactions, and their alignment with business processes. It provides a blueprint for the application portfolio.
* Technology Architecture:This domain covers the technology infrastructure that supports the applications and data. It includes hardware, software, networks, and IT services.
These four domains provide a holistic view of the enterprise and how its different components work together.

In TOGAF, the dimensions for scoping an architecture are Breadth (coverage across the organization), Depth (level of detail), Time Period (horizon of the architecture), and Architecture Domains (the four architecture domains of Business, Data, Application, and Technology). These dimensions ensure comprehensive scoping and contextual alignment.
Reference:
According to TOGAF, defining the scope of an architecture involves considering these four key dimensions:
Breadth: This refers to how much of the enterprise is covered by the architecture. It defines the boundaries of the architecture, which could range from a single department to the entire organization, or even extending to external partners.
Depth: This dimension determines the level of detail included in the architecture. It can range from high-level conceptual models to detailed specifications of individual components.
Time Period: This specifies the timeframe for the architecture, including the intended lifespan of the architecture and any planned phases or iterations. It addresses questions like “What is the architecture for now?” and “What should the architecture look like in the future?” Architecture Domains: This dimension defines which of the four architecture domains (Business, Data, Application, Technology) are included in the scope. The selection of domains depends on the specific needs and objectives of the architecture development effort.

In TOGAF and other enterprise architecture practices, analyzing a value stream often involves understanding the various stages of the value stream and assessing how each stage contributes to business value. Heat mapping is a commonly used technique to visualize and analyze these stages, making it the most appropriate choice in this context.
* Understanding Value Streams in TOGAFA value stream represents a high-level view of how value is delivered to customers or stakeholders. It encompasses all the activities necessary to achieve a specific outcome, often broken down into stages. In TOGAF’s Business Architecture, value stream mapping is a key activity for analyzing and understanding these value stages, enabling architects to identify areas for improvement.
* Heat Mapping as an Analysis TechniqueHeat mapping by value stream stages is a visualization technique that highlights the effectiveness or performance of each stage in the value stream. By applying a heat map, architects can easily see which stages are performing well (often marked in “cool” colors) and which stages may need improvement (often marked in “hot” colors). This is particularly useful for identifying bottlenecks, redundancies, or inefficiencies within the value stream, which is essential for project analysis.
* Why Other Options are Incorrect:
* Option A (Converting value stream stages to entities and building a logical data model):Building a logical data model involves defining data entities and their relationships, which is more relevant for data architecture. It does not directly contribute to analyzing a value stream’s stages or performance within a project scope.
* Option C (An organization chart showing business units and their value):An organization chart shows hierarchical relationships and roles within the enterprise, which does not specifically address value stream stages. While it may help understand which units are responsible for different parts of the value stream, it doesn’t provide insight into the performance or effectiveness of each stage.
* Option D (Combining information mapping with a business process model):Information mapping with a business process model is more suited for detailed process analysis. It involves mapping information flows within processes but doesn’t directly address analyzing value stream stages.
Value streams are typically at a higher level than detailed business processes, focusing more on outcomes than specific activities.
* Conclusion: Heat mapping by value stream stages (Option B) is the most effective tool for analyzing a new value stream within the project scope, as it provides a visual assessment of each stage’s performance and identifies areas for improvement.
References:
TOGAF Standard, Version 9.2, Value Stream Mapping Techniques

The examples given (a whole corporation, a division of a corporation, a government agency, a single government department, partnerships, and alliances) are considered “Enterprises” according to the TOGAF Standard. Here’s a detailed explanation:
Definition of an Enterprise:
Enterprise: According to TOGAF, an enterprise is any collection of organizations that share a common set of goals. It can be a whole corporation, a division of a corporation, a government agency, or a consortium of businesses.
Examples of Enterprises:
Corporation or Division: An enterprise can be a whole corporation or just a division within a larger organization.
Government Entities: It includes government agencies or individual departments within the government.
Partnerships and Alliances: Enterprises can also be partnerships and alliances of businesses, such as consortia or supply chains.
TOGAF Reference:
Scope of Enterprise Architecture: TOGAF defines enterprise architecture as encompassing the entire scope of the enterprise, including all its sub-units and external partnerships.
Enterprise Continuum: TOGAF’s Enterprise Continuum provides a framework for understanding and organizing the artifacts that make up the enterprise architecture.
In summary, the examples provided are considered “Enterprises” according to the TOGAF Standard, as they represent collections of organizations with shared goals.

In a business scenario, business capabilities and value streams are modeled when identifying the business and technology environment. Here’s a detailed explanation:
Business Scenarios in TOGAF:
Business scenarios are used to capture and describe the business requirements, providing a context for the architecture development. They help in understanding the business environment, identifying problems, and defining desired outcomes.
Identifying the Business and Technology Environment:
Business Capabilities: During this phase, the architect identifies the key business capabilities required to achieve the business objectives. These capabilities represent what the organization needs to be able to do.
Value Streams: Value streams are also identified and modeled to understand how value is delivered to customers and stakeholders. They provide a high-level view of the end-to-end processes that create value.
TOGAF ADM Reference:
Phase A: Architecture Vision: In this phase, understanding the business and technology environment is crucial for defining the architecture vision. Modeling business capabilities and value streams provides a foundation for this understanding.
Phase B: Business Architecture: This phase involves a detailed analysis of business capabilities and value streams to ensure that the architecture supports the business strategy and objectives.
Importance:
Contextual Understanding: By modeling business capabilities and value streams, architects gain a comprehensive understanding of the business and technology environment. This helps in aligning the architecture with business needs and ensuring that it supports value creation.
Strategic Alignment: Identifying and modeling these elements ensures that the architecture is aligned with the strategic goals of the organization and supports its key business activities.
In summary, business capabilities and value streams are modeled when identifying the business and technology environment, providing a comprehensive understanding of how the organization operates and how the architecture can support its objectives.

The table describes the steps involved in Phase B (Business Architecture), Phase C (Information Systems Architectures), and Phase D (Technology Architecture) of the TOGAF ADM5. These phases are responsible for developing the target architectures for each domain and identifying the gaps between the baseline and target architectures. The table shows the outputs and outcomes of each phase, as well as the essential knowledge required for each phase.

In the context of value stream stages, a gating stage is the element that describes the specific state change which triggers the next stage of the value stream to begin. It acts as a checkpoint that ensures that certain criteria are met before the process can proceed to the next phase.

In a business scenario, business capabilities and value streams are modeled when identifying the business and technology environment. Here’s a detailed explanation:
* Business Scenarios in TOGAF:
* Business scenarios are used to capture and describe the business requirements, providing a context for the architecture development. They help in understanding the business environment, identifying problems, and defining desired outcomes.
* Identifying the Business and Technology Environment:
* Business Capabilities: During this phase, the architect identifies the key business capabilities required to achieve the business objectives. These capabilities represent what the organization needs to be able to do.
* Value Streams: Value streams are also identified and modeled to understand how value is delivered to customers and stakeholders. They provide a high-level view of the end-to-end processes that create value.
* TOGAF ADM References:
* Phase A: Architecture Vision: In this phase, understanding the business and technology environment is crucial for defining the architecture vision. Modeling business capabilities and value streams provides a foundation for this understanding.
* Phase B: Business Architecture: This phase involves a detailed analysis of business capabilities and value streams to ensure that the architecture supports the business strategy and objectives.
* Importance:
* Contextual Understanding: By modeling business capabilities and value streams, architects gain a comprehensive understanding of the business and technology environment. This helps in aligning the architecture with business needs and ensuring that it supports value creation.
* Strategic Alignment: Identifying and modeling these elements ensures that the architecture is aligned with the strategic goals of the organization and supports its key business activities.
In summary, business capabilities and value streams are modeled when identifying the business and technology environment, providing a comprehensive understanding of how the organization operates and how the architecture can support its objectives.

Phase B focuses on developing the Business Architecture by defining baseline and target business architectures, analyzing gaps, and identifying opportunities to support the organization’s strategic objectives and transformation initiatives.

A Capability Map enables architects to assess how strategic changes affect business abilities. By mapping capabilities to strategic objectives, organizations can prioritize transformation initiatives and evaluate potential impacts across the enterprise.

When developing a Business Architecture, TOGAF provides guidance on how to leverage existing architecture descriptions to build a comprehensive and accurate Baseline Description.
Existing Architecture Descriptions:
Existing architecture descriptions provide valuable insights into the current state of the enterprise’s architecture. These descriptions can include documentation of processes, systems, technologies, and organizational structures.
Baseline Description:
The Baseline Description represents the current state of the enterprise architecture. It serves as the starting point for developing the Target Architecture and planning the transition from the current state to the future state.
Using Existing Descriptions:
Review and Analyze: Existing architecture descriptions should be reviewed and analyzed to understand the current state accurately. This involves identifying all relevant artifacts, documents, and data.
Integration into Baseline: The information from the existing descriptions should be integrated into the Baseline Description. This ensures that the Baseline accurately reflects the current state, providing a solid foundation for future planning.
Gaps and Opportunities: By using existing descriptions, architects can identify gaps in the current architecture and opportunities for improvement. This helps in formulating a more effective Target Architecture.

The business capability map provided uses color coding to represent the maturity levels of various business capabilities in strategic, core, and supporting functions. The colors indicate the current state or priority for development, with red indicating capabilities that are significantly below desired maturity levels and thus require immediate attention. In this case, Policy Management, Government Relations Management, and HR Management are marked as red, signaling the need for urgent improvement. Yellow indicates capabilities that are closer to the desired state but still need attention, while green shows capabilities that have achieved the desired maturity level. Purple indicates a missing capability that does not currently exist in the enterprise, which is the case for Agent Management.

The relationship between business models and business architecture in TOGAF can be described as follows:
* Business Models:
* Definition: Business models describe how an organization creates, delivers, and captures value.
They provide a high-level overview of the business, including elements such as value propositions, customer segments, channels, and revenue streams.
* Purpose: Business models are used to understand and analyze the core elements of the business and how they interact to create value.
* Business Architecture:
* Definition: Business architecture provides a detailed view of the business, including its structure, capabilities, processes, and information. It articulates how the business operates and supports the business model.
* Purpose: Business architecture translates the high-level view of the business model into detailed architectural views and artifacts. It ensures that the architecture aligns with the business strategy and supports the execution of the business model.
* Relationship:
* Articulation of Perspectives: Business architecture articulates the different perspectives and impacts of the business model by providing detailed views of the business components that support the model. This includes defining the necessary capabilities, processes, and organizational structures.
* Alignment and Execution: Business architecture ensures that the architecture aligns with the business model and supports its execution. It translates the strategic intent of the business model into actionable and implementable architectural components.
* TOGAF References:
* Phase B: Business Architecture: This phase involves developing a detailed business architecture that aligns with and supports the business model. It includes identifying and defining business capabilities, processes, and organizational structures.
* Strategic Planning: TOGAF emphasizes the importance of aligning business architecture with business strategy and models to ensure that the architecture supports the overall business goals.
* Benefits:
* Comprehensive Understanding: By articulating the different perspectives and impacts of the business model, business architecture provides a comprehensive understanding of how the business operates and delivers value.
* Strategic Alignment: Ensures that the architecture is aligned with the business strategy and supports the execution of the business model, leading to better business outcomes.
In summary, business architecture articulates the different perspectives and impacts of the business model by providing detailed views of the business components that support the model, ensuring alignment and effective execution of the business strategy.

Phase A focuses on developing the Architecture Vision and engaging stakeholders. Discussions primarily address desired business outcomes, objectives, and value instead of detailed technical implementation or infrastructure concerns.

According to the TOGAF Series Guide: Organization Mapping, one of the derived relationships in an organization map is value flow. A value flow is a relationship that shows how value is exchanged between business units or other entities in an organization map. A value flow can be expressed as a verb phrase that indicates what type of value is transferred or shared between entities. For example, in an organization map for an online retailer, a possible value flow could be
“Delivers products” between the Warehouse business unit and the Customer entity.

In the context of TOGAF and Business Architecture, the diagram depicts the relationship between a Value Stream, Value Stage, and Value.
* Value Stream: Represents the end-to-end set of activities that create and deliver value to a stakeholder.
* Value Stage: A distinct step or phase within the Value Stream.
* Value: The benefit delivered to the stakeholder.
The relationship “X” indicates that a Value Stream is composed of multiple Value Stages.
Think of it like a journey (Value Stream) with multiple stops along the way (Value Stages). Each stage contributes to the overall value delivered at the end of the journey.

Heat mapping is an analysis technique used in TOGAF to show a range of different perspectives on the same set of business capabilities. This technique involves visually representing data to highlight areas of importance or concern, such as performance levels, resource allocation, or risk exposure. Heat maps provide a clear and intuitive way to identify strengths, weaknesses, opportunities, and threats within the business capabilities, facilitating better decision-making and prioritization of improvement efforts.