Home The TOGAF® Standard
Word Search | Search Index

Advanced Search
Provide feedback on this page

TOGAF® Fundamental Content

Extended Guidance

General How-To

Establishing an EA Team

Agile Methods
Business Architecture
Data/Information Architecture
Security Architecture

Reference Models & Method

5. Gap Analysis

The technique known as gap analysis is widely used in the TOGAF Architecture Development Method (ADM) to validate an architecture that is being developed. The basic premise is to highlight a shortfall between the Baseline Architecture and the Target Architecture; that is, items that have been deliberately omitted, accidentally left out, or not yet defined.

5.1 Introduction

A key step in validating an architecture is to consider what may have been forgotten. The architecture must support all of the essential information processing needs of the organization. The most critical source of gaps that should be considered is stakeholder concerns that have not been addressed in prior architectural work.

Potential sources of gaps include:

5.2 Suggested Steps

The suggested steps are as follows:

When the exercise is complete, anything under "Eliminated" or "New" is a gap, which should either be explained as correctly eliminated, or marked as to be addressed by reinstating or developing/procuring the building block.

5.3 Example

Figure 5-1 shows an example analysis for ABBs that are services from the Network Services category of the TOGAF Technical Reference Model (TRM), and shows a number of services from the Baseline Architecture missing from the Target Architecture.

Figure 5-1: Gap Analysis Example
return to top of page