Describing SAP Enterprise Architecture Methodology

Objectives

After completing this lesson, you will be able to:

  • Describing the development process of SAP Enterprise Architecture Methodology
  • Describing the different phases and artifacts of SAP Enterprise Architecture Methodology

Introduction to the Lesson: Describing SAP Enterprise Architecture Methodology

This lesson introduces the SAP Enterprise Architecture Methodology and explains the steps to develop an effective architecture.

Lesson 3 contains the following topics:

  • Step: Architecture Development Method (ADM)
  • Step: Define the Use Case
  • Step: Start with Architecture Phase - Preliminary
  • Step: Use Requirements Management
  • Step: Implement an Architecture Vision
  • Step: Create a Business Target Architecture
  • Step: Design Application and Data Architecture
  • Step: Design the Technology Architecture

The Architecture Development Method (ADM)

Summary

The ADM provides a detailed plan for developing and implementing an enterprise architecture.

Introduction

In the last lesson, you learned, that SAP provides a framework based on TOGAF as well as reference architectures and the SAP Reference Solution Architecture, including mapping.

The aim now is to map the company-specific requirements to the SAP reference structures as far as possible. If, for example, it is possible to map a specific functional requirement to the reference business architecture, you already have the corresponding solution architecture, which you can then implement.

The SAP Enterprise Architecture Framework, the SAP Reference Business Architecture and the SAP Reference Solution Architecture are technology agnostic, that is, the Solution Process Flow Diagram can be implemented in any technology. If SAP technology is used, the processes are already implemented and only need to be customized.

The next information is given along the Metro Map, which in turn is based on the TOGAF framework. The individual areas are color-coded to provide you with better orientation. The color scheme means you always know exactly where you are.

TOGAF Framework

The TOGAF framework describes the individual areas from A to H.

TOGAF Framework.

The individual steps are:

  • 0: Preliminary
  • A: Architecture Vision
  • B: Business Architecture
  • C: Information Systems Architectures
  • D: Technology Architecture
  • E: Opportunities and Solutions
  • F: Migration Planning
  • G: Implementation Governance
  • H: Architecture Change Management

Metro map

The individual steps of the TOGAF framework are mapped onto the metro map. The individual artifacts to be created are named in the metro map.

Color coding:

  • The blue area belongs to the business architecture domain.
  • The yellow area belongs to the IT Architecture Domain.
  • The green area is overarching.
Example of a Metro map.

Definition of the Use Case

Summary

The use case is defined to clearly outline the requirements and objectives of the architecture project.

Introduction

The procedure is briefly described below. The illustration is a simplified version of the TOGAF framework.

The procedure can be roughly divided into four areas. These areas are briefly outlined and provided in an overview.

The entire use case is worked on in detail in the course IEA10 as a case study in the exercises. This course also offers certification as an Enterprise Architect.

The four areas are:

  • Stakeholder Wants and Needs
  • Business Assessment/Scoping
  • SAP Solution Mapping
  • Fit-Gap-Analysis
Solution concept

Sample company N3C- North Carolina Chemicals Corporation

Facts

  • Worldwide activities
  • 43 billion sales/year

Vision and purpose

  • Chemistry for the world
  • Decarbonization

Challenge

The oil and gas business is obsolete.

Goal

Establish a lithium-based battery industry as a market leader.

Value drivers

  • A subsidiary in Germany
  • Pay per use model for the batteries
  • Recycling of the batteries

Architecture principles

  • Cloud First
  • Modular & Agile
  • Compliance with Law
  • Devolution of the core

Start with the Preliminary Architecture Phase

Summary

The preliminary architecture phase is used to plan and prepare the detailed architecture development.

Introduction

You are in the preliminary phase. This belongs to Cross Over (green).

Preliminary phase.

The following topics should be dealt within this phase:

  • Define why, where, who, and how architecture is done.
  • Adapt ADM to your needs (method adoption.)
  • Select ADM phases, deliverables and architecture artifacts.
  • Identify reference architectures.

In the Metro Map, this is the starting point.

Metro map - Preliminary.

Result / tasks

In this step, all the facts about the required artifacts, reference architectures, patterns, blueprints, and much more are compiled.

Below are two lists of questions to be clarified.

Method adoption: Selected ADM phases and artifacts / deliverables

Business target architecture
  • Architectural most relevant capabilities.
  • Architectural most relevant value flows, business processes and business models.
  • Product Map
Application and data architecture
  • Application architecture overview, application use-case(s) diagram(s).
  • SAP Solution Component Model(s), SAP Solution Value / Process Flow, Software Distribution Diagram.
  • SAP Data Flow Diagram, Conceptual Data Diagram / Logical Data Model.
Opportunities and solutions
  • Architecture roadmap.
  • Project plan and deliverables.

List of selected Reference Aachitectures, patterns, and blueprints

Preliminary

Selected reference architectures for this project:
  • SAP Enterprise Architecture Framework (incl Enterprise Architecture Methodology) which provides methodology for using the SAP reference content, for example: Business Value Flows, Processes and Capabilities and mapped SAP Building Blocks.
  • Artifacts used in the SAP Enterprise Architecture Framework reference content (see https://api.sap.com/themes/BusinessProcesses).
Documentation is done mainly in MS PowerPoint (Architecture Definition Document – ADD).

Architecture models are created with:

These BTP Application and Service icons are currently being refreshed and will be officially available in Q4/2023.

Steps within Metro Map

The path to be processed in the Metro Map is defined, as shown in the following example.

SAP Enterprise Architecture Methodology Metro Map.

Step: Use Requirements Management

Summary

Requirements management ensures that all requirements are recorded and taken into account in the architecture process.

Introduction

The following topics are dealt with in the requirements phase. The requirements are compiled:

  • Capture customer requirements (customer wants and needs)
  • Non-functional requirements
  • General constraints
Requirements management.

Functional and nonfunctional requirements are compiled.

Customer wants & needs.

Result

The following is an example of a possible result. The results are collected in World, Power Point or similar. Below is a simple summary of the results.

In reality, these documents can be very extensive.

Result - Customer requirements, wants and needs.

Step: Implement An Architecture Vision

Summary

The architectural vision provides a long-term perspective and orientation for the development of architecture.

Introduction

The following topics are dealt with in the architecture vision phase:

  • Stakeholders and concerns (Stakeholder Map)
  • Statement of work
  • Business drivers, business goals, objectives (strategy map)
  • Scope (Solution Context)
  • Strategy and principles
  • Capability assessment
  • Architecture vision (high-level architecture / solution concept)
  • Architectural decisions and business risk analysis
A: Architecure vision step

Result

The first result is a strategy map that brings together various aspects.

Business drivers, goals and objectives.

Ultimately, a solution concept could be created from this, as shown in the following diagram:

Solution Concept Diagram.

Step: Create A Business Target Architecture

Summary

The business target architecture defines the structure and processes required to achieve the business objectives.

Introduction

Once the general part (green area) has been completed and the necessary artifacts, such as the solution concept and others, have been created, the next step is to create the business target architecture with its artifacts.

In the procedure, you find this in the area of business assessment and scoping.

Business assessment / scoping.

This is the blue area in the Metro Map.

Metro Map for business target architecture.

Results

Mapping, a requirement to the business domain

First, the requirement, for example, Offer Pay per uses model fort battery business, is mapped to a business domain depending on the enterprise domain.

  • Request: Offer Pay per uses model fort battery business (1)
  • Enterprise domain: customer
  • Business domain: sales (2)
Business Capability Map.

Mapping the requirement to one of the eight generic business processes

In the next step, the preceding requirement is mapped to one of the eight generic business processes. In this case, to the Lead to Cash business process.

Mapping to business process.

Step: Design Application And Data Architecture

Summary

The application and data architecture is designed to define the technical solutions and data flows.

Introduction

Once the SAP Reference Business Architecture has been created (blue area), the next step is to map this to a solution architecture (yellow area). The SAP Reference Solution Architecture is mapped in the SAP Business Accelerator Hub.

SAP Solution Map step.

This is the yellow area in the Metro Map.

Detail in the Metro Map.

Results

Step 1

First, the solution concept diagram is mapped to a target architecture overview architecture, as shown in the following screenshot. The focus is again on the Offer Pay per uses model fort battery business requirement.

Solution Concept Diagram towards Target Application Architecture Overview.

Step 2

In the second step, the sales scenario application architecture is created, as shown in the following screenshot.

Sales scenario application architecture.

Step 3

The application architecture is then created with the help of the SAP Reference Solution Architecture.

In our example, the business process is Lead to Cash, its application architecture for a solution variant, here the Lead to Cash for Cloud Deployment.

Solution components

This can be used to identify the necessary systems/capabilities that are required according to this process.

In this case these are:

  • SAP Integration Suite
  • SAP Commerce Cloud
  • SAP S/4HANA Cloud
  • SAP Filed Management Service
  • SAP Subscription Billing
  • SAP CPQ
  • SAP Emarsys Customer Engagement
  • SAP Customer Identity B2B Add-On
  • SAP Cloud for Customer core applications
  • SAP Cloud for Customer core applications
  • SAP Master Data Integration

In this case, the SAP Integration Suite is listed very often. Later on in the topic of integration, you will see that there are many ready-made scenarios that are already available out of the box.

Step 4

In this step, the components from the previous step are mapped to a rough target architecture. The following example includes more than just the one requirement that the training has focused on so far.

Target solution architecture.

Step: Design The Technology Architecture

Summary

The technology architecture comprises the selection and implementation of the technological components required to support the application and data architecture.

Introduction

In this step, a concrete technology architecture is created. This is then implemented by solution and software architects.

SAP Solution Map step.

In the Metro Map

Detail in the Metro Map.

Result

The draft architecture is now converted into a reliable, detailed target architecture. The more detailed the better.

Target solution architecture.

Further artifacts according to the Metro Map are:

  • Architectural decisions
  • Executive summary
  • Risk management

are not considered further below.

Involvement of the solution architect

The solution architects are already involved in this phase. From this point onwards, they assume further responsibility through to successful implementation.

Log in to track your progress & complete quizzes