The SAP Enterprise Architecture Methodology combines industry standards, such as the Open Group Architecture Framework® (TOGAF), with best practices and high-quality content in one framework.
The SAP Enterprise Architecture Methodology provides the following value to customers and partners:
- Proven, TOGAF, and industry standards-based EA methodology, widely adopted throughout SAP
- Pretailored approach and selection of core artifacts based on many years of enterprise architecture experience
- Detailed description of individual artifacts and step-by-step instructions for creation and usage
- Templates and examples for each artifact
- Integrated tool support to accelerate business transformation
The following image outlines the methodological scope of SAP Enterprise Architecture.
The EA Artifact consists of the following:
- Typical architecture work products such 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 use 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, which are typical architecture work products such as diagrams, catalogs, reports, and so on. Examples are Stakeholder Maps, Business Context Diagrams, Solution Value Flow Diagrams, and 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, and Architecture Road Mapping.
The delivered concepts, artifacts, and EA techniques are based on agreed principles and the SAP EA Methodology metamodel, which describes the relationship between the concepts and 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.