The primary purpose of the Gap Analysis technique, as defined within the TOGAF framework, is to compare the Baseline (current state) Architecture with the Target (future state) Architecture. This comparison highlights the differences, or "gaps", between the two states. These gaps often manifest as functions, processes, components, or capabilities that need to be created, developed, or procured to realize the Target Architecture. Therefore, identifying these missing elements is a core objective of the technique, forming the basis for the subsequent implementation and migration planning.

A. Validating non-functional requirements is a requirements management activity, not the primary purpose of comparing two architectural states.
B. Quality metrics are established during the Architecture Vision phase to define the target state, not as a result of the gap analysis.
C. Service levels are requirements that are defined for the Target Architecture; gap analysis checks if they are met, but does not determine them.

1. The Open Group. (2022). The TOGAF® Standard

10th Edition. Van Haren Publishing.

Part III

Chapter 25

Gap Analysis: This chapter explicitly defines the technique. Section 25.1 states

"Gap analysis is a technique used to compare two states of an architecture... The gaps identified form the basis for the definition of a roadmap...".

Part II

Chapter 8

Phase B: Business Architecture

Section 8.5

Step 5: This step involves performing a gap analysis to identify missing business capabilities

functions

and processes between the baseline and target.

Part II

Chapter 10

Phase C: Information Systems Architectures — Application Architecture

Section 10.5

Step 5: This step details using gap analysis to identify "Application components to be developed or procured"

which are essentially missing functions.