Comprehensive Guide to Applying Gap Analysis in TOGAF ADM

Introduction

Gap analysis is a crucial technique used in the TOGAF Architecture Development Method (ADM) to validate an architecture that is being developed. The primary goal of gap analysis is to identify discrepancies between the Baseline Architecture and the Target Architecture, ensuring that all essential information processing needs of the organization are addressed. This guide provides a detailed explanation of how to apply gap analysis in TOGAF ADM, including steps, examples, and interpretations of the associated images.

Objectives of Gap Analysis in TOGAF ADM

The main objectives of gap analysis in TOGAF ADM are:

Identify Gaps: Highlight shortfalls between the Baseline Architecture and the Target Architecture.
Address Stakeholder Concerns: Ensure that all stakeholder concerns are addressed.
Validate Architecture: Confirm that the architecture supports all essential information processing needs of the organization.
Improve Architecture: Identify and rectify accidental omissions or deliberate exclusions in the architecture.

Potential Sources of Gaps

Potential sources of gaps in the architecture can include:

Business Domain Gaps:
- People gaps (e.g., cross-training requirements)
- Process gaps (e.g., process inefficiencies)
- Tools gaps (e.g., duplicate or missing tool functionality)
- Information gaps
- Measurement gaps
- Financial gaps
- Facilities gaps (buildings, office space, etc.)
Data Domain Gaps:
- Data not of sufficient currency
- Data not located where it is needed
- Not the data that is needed
- Data not available when needed
- Data not created
- Data not consumed
- Data relationship gaps
Applications Impacted, Eliminated, or Created
Technologies Impacted, Eliminated, or Created

Suggested Steps for Gap Analysis

Step 1: Create a Matrix

Draw up a matrix with all the Architecture Building Blocks (ABBs) of the Baseline Architecture on the vertical axis and all the ABBs of the Target Architecture on the horizontal axis. Add a final row labeled “New” to the Baseline Architecture axis and a final column labeled “Eliminated” to the Target Architecture axis.

Step 2: Record ABBs

Included: Where an ABB is available in both the Baseline and Target Architectures, record this with “Included” at the intersecting cell.
Eliminated: Where an ABB from the Baseline Architecture is missing in the Target Architecture, review each one. If it was correctly eliminated, mark it as such in the appropriate “Eliminated” cell. If it was not, mark it as an accidental omission in the Target Architecture that must be addressed by reinstating the ABB in the next iteration of the architecture design.
New: Where an ABB from the Target Architecture cannot be found in the Baseline Architecture, mark it at the intersection with the “New” row as a gap that needs to be filled, either by developing or procuring the building block.

Step 3: Review and Address Gaps

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 function.

Example of Gap Analysis

Example 1: Network Services Gap Analysis

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

Target Architecture → Architecture Baseline Architecture ↓	Video Conferencing Services	Enhanced Telephony Services	Mailing List Services	Eliminated Services ↓
Broadcast Services				Intentionally eliminated
Video Conferencing Services	Included
Enhanced Telephony Services		Potential match
Shared Screen Services				Unintentionally excluded – a gap in Target Architecture
New →		Gap: Enhanced services to be developed or produced	Gap: To be developed or produced

Figure 1: Gap Analysis Example

Interpretation of Example 1

Broadcast Services: Intentionally eliminated from the Target Architecture.
Video Conferencing Services: Included in both the Baseline and Target Architectures.
Enhanced Telephony Services: A potential match, indicating it might need further review.
Shared Screen Services: Unintentionally excluded from the Target Architecture, marking it as a gap that needs to be addressed.
New Services: Gaps identified for Enhanced Telephony Services and Mailing List Services, which need to be developed or produced.

Example 2: Data Management Services Gap Analysis

Figure 2 shows an example analysis for ABBs that are services from the Data Management category of the Technical Reference Model (TRM). It highlights a number of services from the Baseline Architecture missing from the Target Architecture.

Target Architecture → Architecture Baseline Architecture ↓	Data Integration Services	Data Quality Services	Data Security Services	Eliminated Services ↓
Data Warehousing Services				Intentionally eliminated
Data Integration Services	Included
Data Quality Services		Potential match
Data Archiving Services				Unintentionally excluded – a gap in Target Architecture
New →		Gap: Data Quality services to be developed or produced	Gap: To be developed or produced

Figure 2: Gap Analysis Example

Interpretation of Example 2

Data Warehousing Services: Intentionally eliminated from the Target Architecture.
Data Integration Services: Included in both the Baseline and Target Architectures.
Data Quality Services: A potential match, indicating it might need further review.
Data Archiving Services: Unintentionally excluded from the Target Architecture, marking it as a gap that needs to be addressed.
New Services: Gaps identified for Data Quality Services and Data Security Services, which need to be developed or produced.

Conclusion

Gap analysis is a vital technique in TOGAF ADM for validating the architecture and ensuring that all essential information processing needs of the organization are addressed. By following the suggested steps and interpreting the results, organizations can identify and rectify gaps in their architecture, ensuring a robust and comprehensive architecture design.