OGB-001 Sample Questions & Answers

The TOGAF Business Scenario technique is designed specifically for this situation. It provides a structured method for documenting the business problem, environment, and stakeholder concerns in a narrative format. This allows for the exploration of different viewpoints (marketing, logistics, etc.) and facilitates consensus-building, leading to a well-understood and agreed-upon set of architecture requirements, which directly addresses the sponsor's concerns.

An Organization Map is a key artifact in TOGAF Business Architecture that depicts the relationships between business units, actors, and roles. A crucial part of this artifact is mapping these organizational elements to the business processes they execute. This provides a clear line of sight from the organizational structure to the work being performed.

An Information Map is a TOGAF artifact that models business information concepts and their relationships. It provides a business-centric view of information, independent of technology, showing how key information entities like 'Policy' and 'Claim' are used by and flow between different parts of the business. This directly addresses the company's need to understand information flow before system design.

This is a core component of managing customer relationships, representing a distinct sub-ability.

This is a specific sub-capability focused on marketing and outreach within the broader CRM context.

This represents the service and support aspect of the customer relationship, a logical decomposition of the parent capability.

The Value Propositions building block describes the products and services that create value for a specific Customer Segment. It is the reason why customers turn to one company over another; it solves a customer problem or satisfies a customer need.

In TOGAF terminology, a value stream is composed of a sequence of 'value stream stages'. Each stage contributes to the incremental delivery of value from the triggering event to the final value proposition for a stakeholder. 'Receive Order' and 'Process Payment' are classic examples of such stages.

This statement is false. While Business Scenarios are a key technique for developing the Architecture Vision in Phase A, they are also a valuable tool throughout the ADM. They can be used in later phases (like B, C, and D) to test architecture designs against business requirements and to help communicate the value and implications of the architecture to stakeholders.

Information mapping focuses on defining information from a business perspective. By creating a common, technology-agnostic vocabulary for key concepts like 'Purchase Order', the organization establishes a stable reference point. This business-level model persists even if the underlying databases, applications, or technologies change, ensuring long-term alignment between business and IT.

An Application/Business Function Matrix (often realized through Capability-to-Application mapping) is the standard TOGAF artifact for showing which applications support which business functions or capabilities. By creating this matrix, the architect can clearly identify where multiple applications support the same function, highlighting prime candidates for rationalization and cost savings.

A core activity within Phase B (and other architecture development phases) is Gap Analysis. This involves comparing the Baseline ('as-is') Business Architecture with the Target ('to-be') Business Architecture. The output is a Gap Analysis report that identifies the capabilities, processes, and other elements that need to be created, changed, or retired to reach the target state.