Conducting Preliminary Phase

The SAP Enterprise Architecture Methodology is a methodology aligned with the TOGAF® standard and tailored to SAP Reference Architecture.

The SAP Enterprise Architecture Methodology has evolved from the (formerly known) Industry Reference Architecture (IndRA) framework, an SAP internal project.

It provides a comprehensive approach used by SAP and its 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.

We recommend that our customers follow a phased approach. It can be used by any enterprise to find the IT Solutions that meet their business needs. The same also holds true 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.

The aim of the preliminary phase is to set the ground for the architecture engagement by selecting the suitable Architecture Development Method, tailoring it to the specific needs, and selecting appropriate reference architectures.

The following figure outlines the means by which SAP Enterprise Architecture can be tailored to the needs of costumers. Here are some basic tips to guide this process:

• Keep it simple
• Tailor it to the needs of the stakeholder (yet define a consistent architecture across the domains)
• Apply iterations within and across the phases
• Start with / concentrate on the domain with major gravity
• Define a compelling story line between business and IT

It is important to remember the following:

• Each architecture engagement is different. Therefore, tailoring the methodology and artifacts you will use is required.
• In the most cases, architecture engagement take place in a given context (baseline architecture, principles, guidelines, and so on, already exists), which needs to be taken into consideration
• Architecture artifacts are created for the stakeholders (not for the sake of architecture work)

In this step, determine what tailoring of the TOGAF framework is required. The following image outlines terminology tailoring, process tailoring, and content tailoring in the content of method selection and adoption.

Consider the need for the following:

Terminology Tailoring

Architecture practitioners should use terminology that is generally understood across the enterprise. Tailoring should produce an agreed terminology set for the description of architectural content. Consideration should be given to the creation of an Enterprise Glossary, which will be updated throughout the architecture process.

Content Tailoring

Using the TOGAF Architecture Content Framework and Enterprise Continuum as a basis, the tailoring of content structure and classification approach allows for the adoption of third-party content frameworks and also allows for customization of the framework to support organization-specific requirements.

Process Tailoring

The TOGAF ADM provides a generic process for carrying out architecture. Process tailoring provides the opportunity to remove tasks that are already carried out elsewhere in the organization, add organization-specific tasks (such as specific checkpoints), and to align the ADM processes to external process frameworks and touch-points. Key touch-points to be addressed would include:

• Links to (project and service) portfolio management processes
• Links to project lifecycle
• Links to operations handover processes
• Links to operational management processes (including configuration management, change management, and service management)
• Links to procurement processes

During the preliminary phase, artifacts of the SAP Enterprise Architecture Methodology will be tailored in the context of a given enterprise architecture engagement.

A set of relevant artifacts will be selected and delivered as part of the engagement.

The given example in the above image highlights an architecture engagement with a business-centric focus as example.

During the preliminary phase, artifacts of the SAP Enterprise Architecture Methodology will be tailored in context of a given enterprise architecture engagement.

A set of relevant artifacts will be selected and delivered as part of the engagement.

The example in the image above highlights an architecture engagement with an IT-centric focus as example.

During the preliminary phase, artifacts of the SAP Enterprise Architecture Methodology will be tailored in the context of a given enterprise architecture engagement.

A set of relevant artifacts will be selected and delivered as part of the engagement.

The example in the image above highlights an architecture engagement with a holistic focus.