Mind mapping Your Way Through 'SAP Enterprise Architecture' - Part 1 : Overview, Methodology

This is part 1 of the series of articles simplifying the SAP Enterprise Architecture. This article covers the overall Methodology behind the SAP Enterprise Architecture Framework. I present the topics in mind map format for easy visualization and understanding.

The SAP Enterprise Architecture Framework consists of 4 building blocks or pillars:

1. Methodology: TOGAF and industry standards-based EA methodology
2. Reference Architecture Content: SAP Reference Business and Solution Architecture mapping Business and SAP IT Solutions
3. Tooling: Set of SAP-internal and customer - facing architecture tools
4. Services: Standardized SAP EA Services to support customer transformation

TOGAF and SAP EA , how are they related?

The TOGAF Architecture Development Method (ADM) cycle 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.

The TOGAF ADM is a method for architecture development, which is designed to deal with most system and organizational requirements. It covers the following ADM Phases on a broad definition;

1. Architecture Context
2. Architecture Delivery
3. Transition Planning (Architecture Realization )
4. Architecture Governance

In the SAP EA Framework, Architecture Context, Architecture Planning & Architecture Delivery phases are adapted to suit the SAP specific usage point of view. The SAP Enterprise Architecture Framework defines a tailored approach, with a set of core artifacts geared towards SAP focused architecture projects. This approach is in line with the TOGAF? standard from The Open Group, a proven EA methodology used by the world's leading organizations.

What are the deliverables in a typical EA projects & how are they classified?

When you undertake a Architecture project, you produce a number of outputs as a result of your efforts, such as process flows, architectural requirements, project plans, project compliance assessments, etc. These outputs are termed as Work Products. The content framework provides a structural model for architectural content that allows the major work products that an architect creates to be consistently defined, structured, and to be presented.

The Architecture Content Framework uses the following 3 categories to describe the type of architectural work product within the context of use:

A deliverable is a work product that is contractually specified and in turn formally reviewed, agreed, and signed off by the stakeholders.

An artifact is an architectural work product that describes an aspect of the architecture.

A building block represents a (potentially re-usable) component of enterprise capability that can be combined with other building blocks to deliver architectures and solutions.

To Be Continued.....

Next Part : Mind mapping Your Way Through 'SAP Enterprise Architecture' - Part 2 : Architecture Context