IBM Rational SOMA 2.9: Origins and Overview
The SOMA (Service Oriented Modeling and Architecture) method was developed as an engagement model within IBM's
Global Business Services group. While public papers and descriptions are available, SOMA is an
IBM-proprietary method that generally is not available to IBM customers. On the other hand, the IBM Practice
Library, along with the Rational Method Composer authoring environment, is a commercial product offering from
IBM. Customers use the IBM Practice Library and Rational Method Composer to:
-
Publish pre-configured processes, which are based upon IBM Practice Library content
-
Develop their own processes, incorporating selected IBM Practice Library content
-
Author totally original processes
We have integrated select content from SOMA with other service-development-related best practices, and then
incorporated the content into the IBM Practice Library, to create this commercially-available approach for service
solution design.
As is discussed in Welcome to IBM Rational's Rational SOMA 2.9, Rational SOMA 2.9 comprises four
practices. One practice, Use-Case Driven Business Modeling, provides some of the business-oriented inputs
needed to initiate service design. The other three practices:
collectively provide best practices for performing service solution design.
The image below illustrates the "design and implementation" lifecycle of services. This shows the three
service-related practices of Rational SOMA 2.9, including the influences driving each practice and the major
artifacts produced. Implementation of services is assisted by other practices in the IBM Practice Library, including Test-Driven Development and
Design-Driven Development.
The key artifact manipulated by the service practices is the Service Model. Considerations for creating this artifact are provided in Guideline: Evolving the Service Model.
Service Identification
Service Identification is focused on the identification of candidate services from the set of assets from both business
and IT. This is performed using:
Service Specification
Service Specification is performed to specify the services and the realizing components that are needed to provide a solution to a
business problem. This discipline is performed using:
Service Realization
Service Realization focuses on ensuring that the service component implementations and overall architecture
satisfy the specified functional and non-functional requirements. These objectives are achieved using:
|