SAHM

This site uses cookies to improve your experience and analyze visits.

Accept
Decline
Learn more about cookies
SAHM logo
  • Home
  • About
  • Pricing
  • Knowledge Hub
  • Support
  • Book a Meeting
  • Customer Portal
  • Employee Portal
  • Contact
Menu

Language

Services

Digital TransformationEnterprise ArchitectureNORA ComplianceEA Tool ImplementationPricing

Expertise

TOGAF FrameworkDGA NORAAvolution ABACUSIT Strategy

Company

About UsContact Us

Resources

Schedule ConsultationRequest DemoCustomer SupportSubmit Ticket

Get in touch

info@sahm.sa+966 53 113 0434

2023 - 2026 © SAHM Information Technology. All Rights Reserved. | Riyadh, Saudi Arabia

Back to Guides

EA Gap Analysis

Methodology for analyzing gaps between current and target EA components, and identifying solutions to close those gaps in line with the entity's strategic objectives.

In Brief

  • Identify the gap between the target future state and the current state of the EA.
  • Two main steps: identify gaps, then propose and approve solutions.
  • Results feed the EA implementation roadmap development phase.
  • Final output: a single document with gap details, solutions, and project cards.

Current State vs Target State

Current StateTarget State
Documented current EA componentsDesigned target EA components
Components to retain or retireNew components to create
Components needing updateFuture architectures and designs
Current domain viewsTarget domain views

Gap Analysis Steps

  1. Identify EA gaps

    Review and analyse current and target state components per domain; identify components to retain, retire, update, or create; then discuss, refine, and finalize the gap list.

  2. Propose initial solutions

    Document proposed solutions to close gaps (new application, restructuring, external provider) and discuss merging similar solutions for efficiency.

  3. Evaluate solutions

    Evaluate by impact and ease of implementation: quick wins (short duration, high impact), medium-term, and long-term solutions.

  4. Prepare final list

    Define scope per solution and linked gaps; discuss with business and IT stakeholders and update as needed.

The entity must document gap analysis for all EA domains in a single document containing: gap details list, proposed solutions list, and gap-to-project card linkage. This document feeds the roadmap development phase.

Related topics

National methodology

Six domains

EA requirements management

EA Gap Analysis | NORA Guide | SAHM