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, and existing baseline business and solution architectures
The selection of artifacts depends on the nature of the architecture project and the stakeholders involved. They are to be selected for the sake of the stakeholders (not for the sake of architecture).
Note
There are iterations within and across the individual phases (the visualization does not intend to give the impression of a waterfall-based approach).
The Value of Architecture Principles, RBAs, and RSAs in SAP Enterprise Architecture
As you explore the SAP Enterprise Architecture (EA) methodology, it's important to highlight three foundational elements. These components play a critical role in guiding architectural work, ensuring alignment with business goals, and accelerating transformation within SAP environments.
- Architecture Principles: These high-level guidelines serve as the foundation for consistent and informed architectural decisions. They provide clarity, support governance, and ensure that architecture efforts remain aligned with business priorities across the enterprise.
- SAP Reference Business Architectures (RBAs): RBAs deliver standardized, industry-specific business capability maps and value chains. They help organizations understand their current business architecture and define target states using SAP’s best practices, making strategic planning more efficient and effective.
- SAP Reference Solution Architectures (RSAs): RSAs offer proven solution blueprints that map business needs to SAP technologies. By using RSAs, architects can accelerate solution design, reduce implementation risks, and ensure alignment with SAP’s product vision and road map.