Exploring the SAP Enterprise Architecture Framework Methodology

The following figure outlines the methodological scope of SAP Enterprise Architecture.

The EA Artifact consists of the following:

• Typical architecture work products as diagrams, catalogs, evaluation reports, and so on.
• Statement of Architecture Work, Business Model Canvas, Business Capability Map, Solution Component Diagram, Solution Process Flow Diagram, and so on.

EA Techniques include the following:

• Set of guidelines, standards, processes, and behaviors to deliver and utilize enterprise architecture work products and manage enterprise architecture in alignment with the business goals
• Capability-based Planning, Stakeholder Management, Architecture Road Mapping, and so on.

EA Concepts consist of the following:

• Fundamental, abstract representations of entities relevant to EA. The essential building blocks of the EA Artifacts and for comprehensive modeling across all domains.
• Business Capabilities, Solution Components, Communication Channels, Data Flows, and so on.

The Shared Principles are as follows:

• Fundamental guidelines that lead to consistent and coherent decisions. They capture shared values, goals, priorities, and essential beliefs.
• Architecture Content Fluency, Reuse of Industry Standards, Transparent Change and Decisions, Appreciation of Other Disciplines, and so on.

The SAP EA Methodology enables the following:

• It defines EA artifacts: Typical architecture work products as diagrams, catalogs, reports, and so on. Examples are Stakeholder Maps, Business Context Diagrams, Solution Value Flow Diagrams, or Solution Component Diagrams.
• It introduces EA concepts: The abstract representations of objects, elements, or entities relevant to the Enterprise Architecture domain. Examples are concepts as Business Capabilities, Solution Components, Data Flows or Communication Channels.
• It also conveys proven EA techniques: Set of guidelines, standards, processes, and behaviors to deliver enterprise architecture work products and manage enterprise architecture in alignment with the business goals. Examples are Capability-based Planning, Stakeholder Mgt, Architecture Road Mapping.

The delivered concepts, artifacts, and EA techniques are based on agreed principles and the SAP EA Methodology metamodel that describes the relationship between the concepts and as well as their key attributes.

The agreed principles are fundamental guidelines that capture shared values, goals, priorities and essential beliefs that have been rail guarding the SAP EA Methodology design.

The following figure lists components of the following:

• Architecture Vision
• Strategy and Motivation
• Business Architecture
• Solutions Architecture
• Technology Architecture
• Roadmap and Transition
• Requirements and Governance

This figure lists definitions of the following domains:

• Architecture Vision
• Strategy and Motivation
• Business Architecture
• Solution Architecture
• Technology Architecture
• Roadmap and Transition
• Requirements and Governance

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, a 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 phases, between cycles, and stakeholder reviews after the phases.

Independent of the approach chosen, it is strongly recommend to run the architecture work in iterations (as also foreseen by the TOGAF ADM). A combination of different approaches has been proven as a best practice.

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)

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 combines industry standards (TOGAF) with best practices and high quality content in one framework.

We took the freedom to select the most relevant artifacts of the TOGAF ADM and augmented the theoretical definition with real content and examples. This work was featured by multiple years of architecture project experience.

The case study guides customers and partners through an end-to-end ADM cycle in a tangible approach.

In the future, the consumption of reference content will be supported by a dedicated tool chain.