The Open Group OGBA-101 Practice Test - Questions Answers, Page 6

The Architecture Development Method (ADM) is the core process of TOGAF which outlines a method for developing and managing the lifecycle of enterprise architecture. Considering the phases of the ADM, the item labeled as '2' in the provided architecture development cycle diagram likely corresponds to the 'Architecture Change Management' phase, which is responsible for providing ongoing architectural oversight and guidance to ensure that the implementation remains aligned with the architecture defined in the previous phases. This includes managing changes to the architecture in a controlled manner as the implementation progresses and ensuring that the architecture continues to meet the business needs.

A business model is a high-level conceptual representation that explains how an organization creates, delivers, and captures value. This encompasses the organization's core logic for creating value, and may include its intended customer segments, the value propositions it offers, the channels through which it reaches customers, customer relationships it establishes, key activities, resources, and partnerships, as well as the revenue streams and cost structures. Thus, it is a visual and strategic representation of how a business operates and competes in the marketplace.

In the context of TOGAF's business scenarios, business capabilities and value streams are typically modeled during the phase of identifying and documenting the desired outcomes. This is because desired outcomes are directly related to what the business intends to achieve, and therefore, it makes sense to model the capabilities (what the business can do) and the value streams (the series of steps the business undertakes to create value) at this stage. This helps in understanding the required changes or enhancements to business capabilities and processes to achieve those outcomes.

A key principle of value streams is that value is always defined from the perspective of the stakeholder2.A stakeholder is any person or group who has an interest in or influence on an enterprise or its activities5. A stakeholder can be internal or external to the enterprise.A stakeholder can also be a customer, end user, partner, supplier, regulator, employee, or any other role that interacts with or benefits from the enterprise's products or services5.Value streams should reflect how stakeholders perceive and measure value in terms of outcomes, benefits, costs, risks, and satisfaction2.

The segments labeled A, D and I in the Business Model Canvas are Key Partners, Customer Relationships, and Revenue Streams respectively1.The Business Model Canvas is a tool that can be used to describe how an organization creates, delivers, and captures value for its stakeholders1.The Business Model Canvas consists of nine segments that cover four main areas: customers (segments B,C,D), offer (segment E), infrastructure (segments A,F,G), and financial viability (segments H,I)1. The segments are defined as follows:

Key Partners (segment A): The network of suppliers and partners that make the business model work1.Key partners can provide resources, activities, or support that enable the organization to offer its value proposition1.

Customer Relationships (segment D): The type of relationship that the organization establishes with its customer segments1.Customer relationships can be driven by customer acquisition, retention, or loyalty objectives1.Customer relationships can also influence the customer experience and satisfaction1.

Revenue Streams (segment I): The sources of income that the organization generates from each customer segment1.Revenue streams can be derived from different pricing mechanisms, such as asset sale, subscription, fee, commission, or advertising1.Revenue streams can also reflect the value that customers are willing to pay for the organization's offer1.

The process used to decompose a set of business capabilities to communicate more detail is leveling6.Leveling is a technique that can be used to break down a business capability into sub-capabilities at lower levels of granularity6.Leveling can help to provide more clarity and specificity about what a business capability entails and how it supports the business goals and objectives6.Leveling can also help to identify dependencies, gaps, overlaps, or redundancies among business capabilities6.

According to the TOGAF Series Guide: Business Capabilities, after documenting all of the business capabilities, the next step is to organize them in a logical manner1.This can be done by using techniques such as layering, sorting, mapping, and leveling1.These techniques can help to classify, group, and align capabilities into categories for a deeper understanding of how they support the business goals and objectives1.Organizing the business capabilities can also help to identify dependencies, gaps, overlaps, or redundancies among them1.

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.

The diagram of an architecture development cycle shows three phases of the TOGAF ADM.The correct phase names corresponding to the labels 1, 2 and 3 are Requirements Management, Implementation Governance, and Preliminary respectively3. These phases are described as follows:

Requirements Management (label 1): This phase provides a process for managing architecture requirements throughout the ADM cycle3.It ensures that requirements are captured, stored, prioritized, and addressed by relevant ADM phases3.It also ensures that requirements are validated and updated as necessary3.

Implementation Governance (label 2): This phase provides a process for ensuring that the implementation projects conform to the defined architecture3.It involves establishing an implementation governance model, defining architecture contracts and compliance reviews, and monitoring and supporting the implementation projects3.

Preliminary (label 3): This phase provides a process for preparing and planning the architecture project3.It involves defining the scope and vision of the project, customizing the ADM process and content framework, defining principles and governance structures, and evaluating the enterprise architecture maturity and readiness3.