Free The Open Group OGBA-101 Practice Exam with Questions & Answers

Phase A (Architecture Vision) of the TOGAF ADM builds out initial organizational maps to understand high-level organizational needs and link them to architecture goals. This step provides foundational insight that informs subsequent phases, particularly for stakeholder alignment.

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.

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.

https://pubs.opengroup.org/togaf-standard/business-architecture/business-models.html Figure 8: The Business Model Canvas[6]

The chart depicted is a Gantt chart, which typically represents the schedule for project activities. In the context of TOGAF's ADM, it is used to illustrate the sequence and interdependencies of tasks across different phases of architecture development. The ADM is an iterative cycle that includes various phases, from the preliminary phase, through architecture vision, business, information systems, and technology architectures, to opportunities and solutions, migration planning, implementation governance, and architecture change management. Each phase must be conducted in a sequence to ensure that the outputs of one phase feed into the next, thereby producing a coherent and structured architecture.

In TOGAF, the relationship labeled "Y" as "Enables" typically refers to how one element of the architecture facilitates or supports the functioning of another element. Here’s a detailed explanation:

Relationship Definition:

Enables: This relationship indicates that one component (e.g., a business capability, process, or technology) enables or supports another component to function or achieve its objectives. It shows a dependency where the presence or effectiveness of one element is necessary for the other to perform effectively.

Examples in TOGAF:

Business Capabilities and Processes: A business capability may enable specific business processes. For instance, the capability of "Customer Relationship Management" enables processes like "Customer Support" and "Sales".

Technology and Applications: A particular technology infrastructure may enable the operation of various business applications, ensuring they can deliver the required functionalities.

TOGAF ADM Phases:

Phase B: Business Architecture: Identifying how different business capabilities enable business processes helps in understanding the interdependencies and ensuring that all necessary capabilities are developed and supported.

Phase C: Information Systems Architectures: In this phase, identifying how technology enables business applications and data flows is crucial for designing a coherent and efficient architecture.

Importance:

Understanding enabling relationships helps in ensuring that all necessary components are in place and functioning correctly to support the overall architecture. It also helps in identifying critical dependencies that need to be managed during implementation.

In summary, the relationship labeled "Enables" describes how one component facilitates or supports the functioning of another, ensuring that the architecture is coherent and all dependencies are managed effectively.

Risk is defined as the effect of uncertainty on objectives. It can be positive or negative depending on whether it enhances or hinders the achievement of objectives. Threat is a potential cause of risk that could have a negative impact on objectives. Continuity is the ability to maintain or resume normal operations after a disruption or disaster. Vulnerability is a weakness or exposure that could be exploited by a threat to cause harm or damage.

 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.

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.

TOGAF's ADM (Architecture Development Method) is designed to be iterative at multiple levels: over the whole process, between phases, and within phases. This iterative approach allows for continuous refinement and improvement of the architecture, ensuring it remains aligned with changing business needs and technological advancements. Iteration helps in managing complexity and facilitates incremental development, enabling architects to revisit and adjust their work as new information and insights emerge.