A work Map to Service-Oriented Business and IT authored by Janne J. Korhonen on August 17, 2010, is a brilliant work and it is a pity that I missed it that time. I highly recommend reading it. In this post, I'll try to draw concepts of OASIS SOA RAF 2012 onto the Jannne's map that I'll refer as MSOBIT.
I start with the comment that MSOBIT utilises two dimensions that preserve a 'status quo' of current enterprise and tries to squash service orientation into it. These dimension axes are: business vs. IT and 'internal' vs. 'external'. OASIS SOA RAF in its latest draft merges mentioned axes and does not confront business to IT as well as 'internal' to 'external' in Service-Oriented Ecosystem (SO Ecosystem). This key difference in an approach requires rethinking of the meanings of the majority of MSOBIT's Strata.
Thus, the content of Starum Business-External is equally applied to the Starum Business-Internal and vice versa. In SO Ecosystem ALL participants are independent and can play both roles of consumers and services/service-providers at the same time. If an internal business team provides a service to another internal team, this service may be used by an external consumer as well (if it is a real SOA service).
Therefore, Service Ecosystem ("a space in which people, processes and machines act together to deliver business capabilities as services in order to further both their own objectives and the objectives of the larger community") interferes with Service Economy, which can spread across several Service Ecosystems and this includes crossing an enterprise boundary if needed (see Figure 1).
Inside an enterprise, it is the business that defines a Business Model , related Vision and Value Proposition. The latter is delivered by an Offering of Service Portfolio comprised Product/Service Mix. Each Service is a means that a consumer can engage to reach the results (Real World Effect) of utilising enterprise business Capabilities that may be realised (among others) via Business Process and Activities.
Altogether, the described structure constitutes an 'offering' part of SO Ecosystem.
In the 'construction' part of SO Ecosystem, we recognise a Strategy of Service Portfolio that is realised via current state of Service Architecture and related transition paths into the strategic or target architectural state. Service Architecture assumes that realised Services are available to potential consumers via announcements of the Service Descriptions that reflect Service Definition while interactions between consumers and services are based on Service Contracts.
A notion of Service Analysis belongs to both consumers and service creators but appears differently. Service consumers analyse Service, i.e. Service Description, in order to decide whether the Service can satisfy the consumer needs with its business functionality and Real World Effect. Service creators analyse services and business needs in the service market or in the offering realm to improve existing services and design the new ones.
Service design is supposed to follow DOSOM and start with defining the business/functional scope of future service, its boundaries and interfaces. The service implementation for both interfaces and body fills the service boundaries with executable entities that can mix manual and automated activities/actions.
Summarising, we have explained how shown inideas of SOA RAF are transforming the 4-Quadrant model of MSOBIT into 2- Quadrant model of Offering Realm and Construction Realm in SO Ecosystem Figure 2.