Identifying Opportunities and Solution

The SAP Enterprise Architecture Methodology - Metro Map outlines the following:

• The full set of architecture artifacts (recommended and optional)
• Input from the SAP Reference Architecture to define the target architecture both in terms of business and IT domains
• References to existing architecture work products such as principles, standards and guidelines as well as existing baseline business and solution architectures

The selection of artifacts again very much depends on the nature of the architecture project and the stakeholders involved. These should be selected for the sake of the stakeholders (not for the sake of architecture).

Take note that there will be iterations within and across the individual phases (the intention of the visualization is not to give the impression of a waterfall-based approach).

The SAP Enterprise Architecture Methodology is a methodology aligned with the TOGAF standard and tailored to the SAP Reference Architecture.

The SAP Enterprise Architecture Methodology has evolved from the formerly known Industry Reference Architecture (IndRA) framework, an SAP internal project.

It provides a comprehensive approach used by SAP and customers to systematically map IT Solutions to business needs. Internally SAP uses the framework to build enterprise architecture content. Customers apply the framework to define their desired future business scope and desired target architecture.

The recommendation for our customers is to follow a phased approach. It can be used by any enterprise to find the IT Solutions that meet their business need. Same holds true also for SAP's own IT.

This approach is in line with the TOGAF® standard from The Open Group, a proven EA methodology used by the world’s leading organizations to improve their business efficiency.

The TOGAF Architecture Development Method (ADM) cycle is the result of continuous contributions from a large number of architecture practitioners. It describes a method for developing and managing the lifecycle of an Enterprise Architecture.

The ADM is highly iterative: Within phases, between phase, between cycles, stakeholder reviews after the phases.

Our focus during the opportunities and solutions phase will be on the creation of the architecture roadmap for business and IT stakeholders.

Key architectural work products are the finalized Target Business, Application / Data and Technology Architectures including Transition Architectures in the Architecture Definition Document with these artefacts:

• Architecture Roadmap (incl. Transition Architectures)
• Prepare Migration Planning: Drafts for Implementation / Migration Plan and Work Breakdown Structure
• Benefits Diagram (linked to Business Drivers, Goals and Objectives - for example, update Business Footprint Diagram)

Generate the initial complete version of the Architecture Roadmap based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D.

Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value.

The steps enable the following tasks:

• Determine/Confirm Key Corporate Change Attributes
• Determine Business Constraints for Implementation
• Review and Consolidate Gap Analysis Results from Phases B to D
• Review Consolidated Requirements Across Related Business Functions
• Consolidate and Reconcile Interoperability Requirements
• Refine and Validate Dependencies
• Confirm Readiness and Risk for Business Transformation
• Formulate Implementation and Migration Strategy
• Identify and Group Major Work Packages
• Identify Transition Architectures
• Create the Architecture Roadmap and Implementation and Migration Plan

The Architecture Roadmap consists of two artifacts, the business stakeholder related Business Architecture Roadmap and the solution-centric Application Architecture Roadmap. Both roadmaps are closely integrated and provide two viewpoints on the same content.

The Business Architecture Roadmap is a visual representation of business outcomes across time horizons and functional clusters.

The Application Architecture Roadmap depicts the solutions required to realize a company's goals within a given time.

The Transition Architecture(s) define the order of the implementation steps and show EA teams how to move from a Baseline Architecture to an established Target Architecture.