The Open Group OGEA-10B Exam Dumps

The purpose of the Gap Analysis technique is similar to the previous question, but with a focus on the Target Architecture. The technique helps to identify the items that are not included or specified in the Target Architecture, such as capabilities, services, components, standards, or technologies. These items may be essential for achieving the vision and goals of the enterprise, or for addressing the stakeholder concerns and requirements. By identifying the items omitted from the Target Architecture, the technique helps to ensure that the architecture is comprehensive, feasible, and realistic.

Architecture Principles are general rules and guidelines that inform and support the way in which an organization sets about fulfilling its mission. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions.One of the purposes of Architecture Principles is to establish a common understanding of how to control the business in pursuit of strategic objectives, by providing a framework for evaluating and agreeing on the changes that affect the enterprise's architecture3Reference:3: The TOGAF Standard, Version 9.2, Part III: ADM Guidelines and Techniques, Chapter 23: Architecture Principles : The TOGAF Standard, Version 9.2, Part IV: Architecture Content Framework, Chapter 31: Architecture Principles

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.

The Enterprise Continuum consists of two complementary concepts: the Architecture Continuum and the Solutions Continuum1. The Architecture Continuum provides a consistent way to describe and understand the generic and reusable architecture building blocks, such as models, patterns, and standards, that can be applied and tailored to specific situations2. The Solutions Continuum provides a consistent way to describe and understand the specific and implemented solution building blocks, such as products, services, and components, that realize the architecture building blocks3. The Enterprise Continuum enables the reuse and integration of architecture and solution assets across different levels of abstraction, scope, and detail, ranging from foundation architectures to organization-specific architectures1.

The Enterprise Continuum is used when developing an enterprise architecture to support the following activities1:

* Selecting relevant architecture and solution assets from the Architecture Repository or other sources, based on the business drivers, goals, and requirements

* Adapting and customizing the architecture and solution assets to suit the specific needs and context of the enterprise

* Defining and developing the target architecture and the architecture roadmap, based on the gaps and opportunities identified between the baseline and the target states

* Defining and developing the implementation and migration plan, based on the architecture roadmap and the solution building blocks

* Governing and managing the architecture and solution assets throughout the architecture lifecycle, ensuring their quality, consistency, and compliance

The illustration shows the relationship between the Enterprise Continuum, the Architecture Continuum, and the Solutions Continuum, which are key concepts in the TOGAF framework. The Enterprise Continuum is a view of the Architecture Repository that shows how generic foundation architectures can be leveraged and specialized to support the requirements of an individual organization. The Architecture Continuum specifies a structured classification for architectural artifacts, such as models, patterns, and descriptions, that can be reused and adapted across different domains and levels of abstraction. The Solutions Continuum identifies implemented solutions that support various stages of business and IT capability evolution, such as common systems, industry solutions, and organization-specific solutions. The illustration also shows how the architecture context and requirements are influenced by external factors, such as business drivers, stakeholders, and standards, and how they shape the generic and specific architectures and solutions. The illustration also shows how the deployed solutions become part of the architecture context for future iterations of the architecture development cycle. Reference:

* TOGAF Standard, 10th Edition, Part II: Architecture Development Method, Chapter 6: Architecture Repository, Section 6.2 Enterprise Continuum.

* TOGAF Standard, 10th Edition, Part IV: Architecture Content Framework, Chapter 35: Enterprise Continuum and Tools, Section 35.1 Introduction.