on Apr 21, 2008 12:00 AM, last modified by The methodology for accelerated transformation to service-oriented architecture (SOA) describes the typical activities required to:
- transform to an SOA-based system landscape using the SAP Business Process Platform as a key building block.
- use the SAP Business Process Platform and build service-based solutions on top of it.
The methodology focuses on the SOA-by-evolution concept and related SAP products, services, and concepts. The target audience is people who drive, plan or execute a company's evolution toward a service-oriented architecture.
The methodology can also be considered as an SOA adoption roadmap in the context of SAP products (business applications and technology components, which form together a business process platform).
It is important to note that "SOA-based system landscape" does not mean that each and every business process of a company runs as a service-based solution (for example, as composite application). Instead, it means that there is a platform in place which:
- incorporates SOA principles
- offers companies the option to address certain requirements through individual service-based solutions.
How to Use the Methodology
The methodology distinguishes between SOA adoption initiatives at enterprise level and business solution implementations at project level. The enterprise level initiatives are mainly related to long term IT strategy planning and infrastructure setup activities. The solution implementation part is structured along the plan, build, and run cycle. The "Plan" phase describes a general business process management methodology and is actually not only relevant in the context of a SOA transformation. Instead it can be used for planning solutions in general and independent from the later technical implementation option. The "Build" phase is SOA-focused and describes a methodology for implementing user centric composite applications on top of a business process platform.
These methodology sections are not necessarily processed in a strict sequence. Companies can parallelize activities, set different emphases or even choose different entry points (different adoption patterns). For instance, some companies may have the required platform basis or infrastructure already in place and may start directly with the implementation of service-based solutions (for example, based on SAP's Enterprise Service Bundles). Other companies may not see a need to invest heavily in a long-term enterprise architecture planning, because this issue is already settled for them, and start directly with the modernization of their system landscape (for example, ERP upgrade).
Methodology Assumption
The methodology is based on the assumption that companies want and need to establish an SOA at an affordable cost. This is recognized by two aspects of the methodology: the service provisioning side, and the service consumption side.
On the service provisioning side, SAP ships a business process platform which includes a huge amount of ready-to-run enterprise services. This means that companies do not necessarily need to build their own custom enterprise services. They can leverage the services of the business process platform (and the included SAP Business Suite) and immediately start building innovative solutions on top of it.
On the service consumption side, the methodology supports a gradual (evolutionary) approach towards service-based solutions. This means that best-practice processes (for example, core processes which require a certain semantic consistency that is certified by a vendor and compliant with regulations) can stay within packaged business applications like the SAP Business Suite and run as "platform processes". At the same time, companies can build innovative processes and solutions as service-based solutions (for example, as composite applications). Typically, it makes sense to focus on areas where the advantages of service-based architectures and highly standardized interfaces can be leveraged to the largest extent: These are processes that span across functions, applications, and enterprise boundaries. Another driving force for service-based solutions can be the need for custom-tailored user interfaces.
Access the Methodology
Access the methodology online now!
After your first experiences with the methodology in your projects, we would love to hear your feedback. Send an e-mail with your comments to the SAP Field Services SOA Program at fsesoa@sap.com.