Proposal Business Driven SOA

1
Proposal Business Driven SOA

• Harry Hendrickx,
• Capgemini Nederland NV
• Utrecht, The Netherlands

2
Problem Statement

• Based on the recommendation of the Unique value
  of SOA working group
• Description
• There is a lot of emphasis on the technical
  characteristics of SOA. This effort will focus
  on the managed evolution of business
  needs/potential and IT needs/potential.
• Value
• Help capture common, cross-vendor understanding
  of business driver behind SOA.
• Possible Deliverable
• Guide explaining business concepts underlying SOA
• Scenarios for business-driven SOA

3
The Industry Context
User Needs
Service Aggregators
Specialized Search Engines
Service Directories
Xmethods.net Salcentral Componentsource
Services Platform Providers
CRM Services
Procurement Services
Financial Services
Process Management
Planning Scheduling
Production Services
Infrastructure Servicest
IInformation Services
Security Services
4
Customer Need and Service

• The market Need is defined as the customers
  problem to be resolved.
• A Service can be evoked to fulfil the Need. It is
  implementation independent.
• Capability is the configuration of the solution
  that provides the Service
• The vision and business strategy clarify the
  nature and composition of the Real World Effect.
• The Real World Effect is determined by the
  essential logic (how) of the capabilities used
  for production
• The means determine the physical implementation
  (with what) of the procedures

5
Implications for Service Design

• The better the needs are understood
• the better the Service definition
• the better the logic of fulfilment can be defined
• Different parties that have need for Services
• Customers
• Business Stakeholders
• IT Operations Stakeholders
• Some need SOA
• Some dont need SOA

6
The vision

• The basic issue to solve is the response to
  market dynamics
• The problem to solve is dynamics of change and
  increasing variability of operations.
• Enterprises translate this in a need for more
  flexibility
• Technology enables (SOA) and complicates (Legacy)

How can the requirements of a flexible Service
based architecture be defined?
7
Research has identified four different domains to
enhance flexibility
Different Perspectives
Management task of Flexibility
Strategic Management
Operational flexibility
Dynamic Contingency
Structural Flexibility
Organizational Learning
Strategic flexibility
Innovation Entrepreneurship
Environmental impact
Design task of flexibility
Non-competitive - rigid
Technology routine / non-routine
Complex/dynamic - planned
Structure mechanic / organic
Hyper competitive - flexible
Culture conservative / innovative
Extremely turbulent - Chaotic
With these aspects flexibility can be visualized!
8
Different perspectives of organizational
flexibility have complementarities . and
Aspect Perspective Flexibility meaning When required Solution to enhance flexibility
Strategic Management Strategic asset If anticipation is impossible Redundancy in org. conditions Broad frame strat. governance
Dynamic Contingency Org. potential to adapt to environm. change Dynamic environment Reactive Proactive
Organizational Learning Reflective capacity Dynamic environment Single loop Double Loop
Innovation Entrepreneurship Organizational ability to innovate New techn and new businesses Routine Proliferation Routine Destruction
. Flexibility is a composite of many aspects
9
8 Different scenarios can be defined

• Organize for a broad range of different
  organizational conditions
• Organize for a broad frame of strategic
  governance
• Organize for pro-activeness
• Organize for re-active adaptability
• Organize for evaluation and improvement
• Organize to re-invent the business
• Organize for routine proliferation
• Organize for routine destruction

What are the implications for Service Orientation?
10
The outcome from the working group may take
different forms

• Increased understanding in the degree of urgency
  of the need for SOA
• Insight in the implication of each scenario for
  SOA thinking
• Insight in the different approaches for SOA
  development
• Insight in the importance of specific standards
  per scenario

11
The Proposed Plan

• Identify the descriptors of flexibility in each
  scenario
• Source The Flexible Enterprise, H.W. Volberda
• Build on the given descriptors in this research
• Analyse each scenario for its implication for SOA
  approach
• Business Architecture
• Information System Architecture
• Technical Infrastructure
• Security
• Governance
• Determine the major distinguishable scenarios
• Communicate the results within The Open Group
  membership