Download Latest OGBA-101 Questions

In TOGAF and business architecture practices, information mapping is a technique used to organize, visualize, and analyze key information assets within an organization. One of the primary benefits of information mapping is that it provides a structured view of information flows, dependencies, and requirements across various parts of the organization, supporting decision-making at multiple levels. By clearly mapping how information is generated, used, and shared, decision-makers can make more informed choices, ensuring alignment with strategic goals and effective use of resources.

Each option can contribute to the business architecture, but Option D is the most accurate for the benefit of information mapping:

Option A (Improved business process integration) describes a benefit of process mapping rather than information mapping, although structured information can support process integration indirectly.

Option B (Framework for effective business requirements analysis) is not the primary benefit of information mapping. While information mapping helps clarify information needs, the analysis of business requirements is more focused on requirements engineering practices.

Option C (Highlights information requirements not addressed) is incorrect because while information mapping can reveal gaps in information needs, its primary function is not to identify gaps but to provide a clear view of information assets and flows.

Therefore, Option D accurately reflects the main benefit of information mapping: supporting effective, informed decision-making across the business.

The diagram provided illustrates a Capability Map. Here's why:

Focus on "what" the organization does: The diagram depicts various functions and activities that the organization performs, such as "Program/Human Resource Matching," "Employee Supply and Demand Mgmt," "Benefits Management," etc. These represent the capabilities of the organization, or what it is able to do.

Hierarchical structure: The capabilities are organized hierarchically, with broader functions like "HR Mgmt." encompassing more specific capabilities like "Position Advertising" and "Skills Assessment." This shows how different capabilities relate to each other and contribute to higher-level functions.

No specific process flow: Unlike a process map or value stream map, this diagram doesn't show a sequence of steps or flow of activities. It focuses on the capabilities themselves, not how they are executed

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.

 The technique shown in the example is called relationship mapping. It is a technique that can be used to show how a business architecture addresses stakeholder concerns across different parts of an organization2. It can highlight gaps or overlaps in the coverage of stakeholder concerns by a business architecture. In this case, the technique is used to relate business capabilities to organization units so as to highlight duplication and redundancy.

This modeling technique is referred to as Relationship Mapping. It's used to relate business capabilities to organizational units to highlight areas of duplication and redundancy, as well as to indicate where capabilities are being performed well (green), where there are potential issues (yellow), and where there are significant problems or gaps (red). This visualization helps in understanding the alignment between organizational units and capabilities, and where improvements or changes may be needed.

5.2.1 Capability/Organization Mapping