The Open Group OGEA-101 Exam With Confidence Using Practice Dumps

Gap analysis is a technique that is used to validate an architecture by highlighting the shortfall between the Baseline Architecture and the Target Architecture. One of the purposes of gap analysis is to identify missing functions that are either deliberately omitted, accidentally left out, or not yet defined in the Target Architecture. Missing functions are marked as gaps that need to be filled by developing or procuring the building blocks. 

 According to the TOGAF template for Architecture Principles, the Rationale section should describe the relationship to other principles, as well as the business benefits and the intentions of adhering to the principle. The Rationale section should use business terminology and point to the similarity of information and technology principles to the principles governing business operations. The Rationale section should also explain how the principle supports the achievement of the business objectives and key architecture drivers. References:

Architecture Principles Template

The TOGAF Standard, Version 9.2 - Architecture Principles

The Open Group Exam OGEA-103 Topic 1 Question 4 Discussion

The image shows a diagram that illustrates the basic concepts of architecture description as defined by the ISO/IEC/IEEE 42010:2011 standard1, which is also adopted by the TOGAF standard2.

According to the ISO/IEC/IEEE 42010:2011 standard, an architecture description is a work product used to express an architecture, and it consists of one or more architecture views1.

An architecture view is a representation of a system from the perspective of a related set of concerns, and it conforms to an architecture viewpoint1.

An architecture viewpoint is a specification of the conventions for constructing and using an architecture view to address specific stakeholder concerns1.

Therefore, the correct answer is option A, which identifies the items labeled as “A” and “B” in the image as an architecture viewpoint and an architecture view, respectively. References:

1: ISO/IEC/IEEE 42010:2011 - Systems and software engineering — Architecture description1

2: TOGAF Standard, Version 9.2 - Part IV: Architecture Content Framework - 31. Architectural Artifacts2