www.cbdiforum.com
Roadmap to Strategic SOA
David Sprott
Independent Guidance for
Service Architecture and Engineering
Agenda





Everware-CBDI?
Baseline SOA Adoption
Assessment Exercise
Applying structure to the change management task
Strategies, Techniques, Framework
A working session, guiding participants through elements of an SOA
adoption planning process to illustrate a framework for managing
the transition to SOA. The session will commence with an
assessment exercise – to help participants understand their current
SOA maturity level, and then introduce by example the techniques
involved in SOA capability planning
2
© 2007 Everware-CBDI Inc
A Newly Merged Company

Specialist firm providing actionable guidance and support to the most
profound transformation in the history of business and IT
- Enabling structured, enterprise level SOA
- Facilitating SOA standards
- Research based best practices
Trusted, Independent SOA Advisors
3
© 2007 Everware-CBDI Inc
The Challenge


Complex change management problem
Introducing architecture driven approach to largely unstructured
environment
PRE-SOA








Project driven
Variable approaches and
processes
Point to point integration
Low levels of reuse at any level
Loose coupled technology
Tight coupled applications
Low level of business alignment
...
SOA








4
Business/IT convergence
Contract based services
High levels of reuse of coarser
grained functionality
Manufacturing and assembly
environment
Architecture and policy driven
Repeatable processes
Strong governance to maintain
architectural integrity
...
© 2007 Everware-CBDI Inc
Current State?

Tactical SOA
 Project and or infrastructure driven
 Delivering and using services with little or no structure
 Little or no consensus or consistency across the organization
 No explicit policies and repeatable processes that permit governance
 Recipe for Service Anarchy and limited ROI
Early Learning
5
Integration
Most enterprises
are “doing” SOA
today in some fashion
© 2007 Everware-CBDI Inc
Future State


Tactical SOA
 Project and or infrastructure driven
 Delivering and using services with little or no structure
 Little or no consensus or consistency across the organization
 No explicit policies and repeatable processes that permit governance
 Recipe for Service Anarchy and limited ROI
Strategic SOA
 Analogous to a manufacturing and assembly environment
 Classes of service have appropriate, repeatable processes
 Mature architecture and engineering processes and practices
 Formality over policy implementation to ensure implementation of both
business requirements and architectural policies
 Manage outcomes that are fit for purpose, deliver future flexibility, utility and
cost.
Service Architecture & Engineering:
A comprehensive, defined approach for service architecture together with repeatable
service engineering processes that guide the delivery of the agile enterprise.
6
© 2007 Everware-CBDI Inc
Service Architecture & Engineering Reference Framework
CBDI-SAETM SOA Reference Framework
Process
Model
SOA Principles
Glossary
Manage
SOA Meta Model
Service Life Cycle
Consume
Provide
Architecture
SOA Views
Enable
SOA Best Practice
Business
Standards
Patterns
7
Organization
Techniques
Technology
Models
Deployment
Policy
Implementation
Deliverables
Specification
Roles & Structure
Project Profiles
Funding Models
© 2007 Everware-CBDI Inc
A Clutch of SOA Maturity Models
Service Maturity Model from AmberPoint,
Bearing Point, Sonic Software and Systinet
SEI CMMI
BEA Systems
IBM - Service Integration Maturity Model
1.
2.
3.
4.
5.
6.
7.
8
Silo (data integration)
Integrated (application integration)
Componentized (functional integration)
Simple services (process integration)
Composite services (supply-chain integration)
Virtualized services ( virtual infrastructure)
Dynamically reconfigurable services (eco-system
integration)
© 2007 Everware-CBDI Inc
SOA Capability/Maturity Model
Management
Architecture
Operational Infrastructure
Delivery Infrastructure
Organization
Process
Projects
CAPABILITY
WORK
PACKAGE
MATURITY
LEVEL
OUTCOME
STRATEGY
Narrow path
Tactical. . .
Domain
...
9
Early Learning
Applied
Integrated
Enterprise
Ecosystem
© 2007 Everware-CBDI Inc
SOA Capability Maturity Model
Ecosystem
Enterprise
Applied
Project based
SOA activity
Early
Service
Learning
architecture
enables
Initial SOA
business
activity
adaptability
Experimental for limited
scope
10
Enterprise level
shared services
Integrated
create enterprise
adaptability and
Shared services
consistency
integrate silos,
SOA enables
rationalize EAI
enterprise wide
contracts
consistency of
Integrated
approach reduces business information
and processes
complexity, cost
and increases
adaptability
Common ecosystem
services eliminate
organizational
boundaries and
enable broader
economic activity
Service concepts
standardized across
industry sectors and
or LOBs
© 2007 Everware-CBDI Inc
SOA Roadmap Streams
SOA
Management
Management tools including vision, strategy, funding, charging, measurement and monitoring
Service
Architecture
Operational
Infrastructure
Creation and ongoing management of the service architecture and portfolio
Single logical operational infrastructure with common policy implementation and management tools
LifeCycle
Infrastructure
Consistent reference architecture for tools and platforms to deliver and manage
the requirements to retirement life cycle
Framework
and Process
The architectural framework and repeatable processes enabling consistency,
trust and governance in federated activity.
Organization
Roles and responsibilities to execute on federated, specialized, utility based solutions environment.
Projects &
Programs
Project strategy and planning to enable very high levels of reusable services
in a manufacturing and assembly environment
Early
Learning
11
Applied
Integrated
Enterprise
Ecosystem
Maturity Level
© 2007 Everware-CBDI Inc
Outline SOA Maturity Level Assessment
Maturity Level
Stream
Early
Learning
Applied
Integrated
Enterprise
Ecosystem
Funding for
pilot/PoC
projects
Services are
managed as an IT
architecture concept
Funding systems facilitate
provisioning of shared services
Services are managed as
business assets.
Services facilitate inter
business collaborations
Architecture
is
fragmentary
&
experimental
Project architectures
are service oriented
There is a standard for rich
service specification
The Enterprise has a Service
Portfolio Plan
There are agreed business
process and data
architectures for business
collaborations
Operational
Infrastructure
ESB pilot or
PoC
Project ESB
Common ESB framework
Common framework for
enterprise service management
and security
Services are managed as
federated resources
Life Cycle
Infrastructure
Services are
not managed
assets
Services are project
level deliverables
Enterprise level registry and
repository provides consistent life
cycle governance of the run time
service asset
Enterprise registry and repository
provides design AND runtime
service asset life cycle
governance and asset
dependency horizon analysis
Ecosystem registries
provide governance over
collaborative business
processes
Framework and
Process
Frameworks
and practices
extended in
ad hoc
manner
Project specific
architecture
frameworks
Common SOA reference
architecture and process (defined
concepts, principles, policies and
patterns)
Convergence of business and IT
practices around service concept
Collaboration reference
architecture (defined points
of collaboration)
Organization
IT architects
sponsor SOA
SOA is a project
level responsibility
There is single point of
accountability for integration
Services are owned by the
business
Services defined and
managed on inter business
collaborative basis (vertical,
supply chain etc)
Projects & Programs
Pilot and PoC
projects
Service delivery and
usage integrated into
LoB projects
Specialization of Service
provisioning, implementation and
assembly projects
Service product management
Collaborating parties act as
provider and consumer
SOA Management
Service Architecture
12
© 2007 Everware-CBDI Inc
SOA Maturity Assessment
Current, 1 year and Target State Views
The graph below indicates the initial maturity assessment of the SOA with respect to:
•
Current state assessment
•
Situation after in-flight initiatives have run (a 1 year time horizon)
•
A target state proposed for the enterprise (a 3-5 year time horizon)
SOA Understanding
4
3
Projects
Management Tools
2
Current State
1 year view
Target state
1
0
Organisation
Architecture
Process
Maturity Levels
0: Zero base
1: Early learning
2: Integration
3: Reengineering
4: Cultural Integration
Infrastructure
Sample
13
© 2007 Everware-CBDI Inc
Current State Assessment: Architecture
0: Zero
base
1: Early
Learning
2: Integration
Current
initiatives
NOW
3: Reengineering
4: Cultural
Integration
Gap
1 year
outlook
Current State
No consistent enterprise wide reference
architecture for re-use exists although
different elements are being developed in
different parts
Evidence for Maturity
• Some definition of terms locally
• Recognition that architecture is more than just IT
• Reference architecture defined in parts
• Canonical data models exist
• Have some automatic enforcement of architectural
rules
• Some policy definitions written
• Recognition of need for service contracts
Target
state
1 year outlook
Work is planned on taxonomy over
the next year
Target State (3-5 yrs)
See next slide
Evidence for Immaturity
• Lack of awareness of a reference architecture and doubts about its
usability expressed
• Confusion about terminology e.g. no unified definition of a service
• Architectures weren’t consistent across SOA domains
• No single semantic model in place
• Service contract definitions not written or implemented
• Policy definitions not written at business governance level or
consistently enforced
• Low visibility of links between business drivers and architectural
plans
Interview Quote: “Have 5 different capability managers who are doing their interfaces in 5 different ways!”
1
CBDI Comment: Architectural maturity is key in order to lead the overall direction.
Sample
14
© 2007 Everware-CBDI Inc
Target State: Architecture
0: Zero
base
1: Early
Learning
2: Integration
3: Reengineering
Target
state
Target State Characteristics
15
4: Cultural
Integration
Target State Justification
A defined and stable state for the
architecture is considered be
optimal. The more mature state –
mandated – may be inflexible
given the enterprise’s disparate
businesses
Outcomes
Reference Architecture: consistent, layered architectures
across SOA domains enforced in a consistent manner and
widely adopted
Consistent approach enables reuse and drives
productivity through standard approach to solving
complex problems. Layered architecture reduces
dependency and increases adaptability
Taxonomy/Canonical Data Models: consistent use of
service-based terminology across areas. Architectural
classifications and Functional classifications in place. A single
semantic model, against which all services are mapped
Allows management of complexity; easier and
faster to construct compatible end-to-end
solutions
Service Contracts: Rich service specifications and contracts
implemented including SLAs. Procurement agreements
include architectural constraints and obligations
Reduced testing costs. Consumers have
guaranteed service levels.
Greater agility due to ability to modify, extend
and improve services independently if contracts
are unaffected
Modularity: Well-defined boundaries between products and
capabilities. Legacy applications reengineered and
componentised
Sample
Increased speed of change (due to reduced
horizon of change), easier to manage complexity
and better accountability
© 2007 Everware-CBDI Inc
SOA Capability
Maturity Levels
EARLY ADOPTION
CAPABILITY
APPLIED
STREAM
CAPABILITY
CAPABILITY
AREA
INTEGRATED
CAPABILITY
ENTERPRISE
CAPABILITY
ECOSYSTEM
CAPABILITY
16
© 2007 Everware-CBDI Inc
Scenario Example
Scoped Manifest
Business Type Model
Architectural
Framework
Detail Manifest
Architecture
Key:
Long term
Scenario
Map Manifest BTM to LDM
(Transformation Architecture)
Candidate Reference
Architecture
Service
Portfolio
Planning
High Level Manifest
Service Model
Programs
& Projects
Manifesting Project
Manifest Rich Service
Specification
Delivery
Process and
Infrastructure
Rich Service Specification
Standards
Service Acquisition
Contract Modifications
Runtime
Infrastructure
Roles and
Responsibilities
Management of the
Adoption Process
17
Service Acquisition
Governance Process
Service Registry
Define Test Bed
Processes for Services
Consumer Support
Process
Change Management
and Communication
Policies
Common Service Security
Architecture for Manifest
(Limited)
Common Policies for
Service Runtime
Operation
Effective Service
Infrastructure
Assign Manifesting
Service Portfolio Manager
Establish Manifesting
Service Community of
Interest
Differentiated Security
with Message Level
Profiles
Common Service Security
Architecture for Manifest
(Potential)
Definition of Scope and
Business Case for
Manifesting
© 2007 Everware-CBDI Inc
Capability Dependency Diagram – Example
Basic Level
of Governance
Reference
Implementation
Delivery
Team Charter
Service
Asset Automation
Formal
Specification
Standard
Basic
SOA Policy
SOA
Reference
Architecture
18
Skills
Development
SOA
Reference
Process
© 2007 Everware-CBDI Inc
Capability Plan – Example Fragment
Capability
Recommendations
Maturity Level
Outcome
Central or federated
coordination of
integration activity.
Integration activities are consolidated
and centrally co-ordinated and
managed to reduce proliferation of
point-to-point communications, and
proliferation of products and disparate
technologies.
Integrated
Architecturally-driven
acquisition
Procurement should exert greater
architectural control and obligation
over 3rd parties.
Integrated/Enterprise The outsourcing contract
needs to specify the
requirements for flexibility.
Architecturally driven
SOA policies and
standards
The architecture organization
establishes policies and standards for
enterprise wide adoption of SOA
Early learning
Enterprise level standards
and policy development
Balancing short-term
and longer-term
requirements
Business analyst/architect function
have responsibility for short and long
term demand for business process
change
Integrated
Requirements for shared
services are established on
the basis of forecast
business needs.
Architectural
governance
Establish architectural community of
interest.
Enterprise
Collaboration and learning
between architecture
groups.
19
Rationalization of existing
EAI contracts; governance
over integration activity,
transformation to services
© 2007 Everware-CBDI Inc
Levels
Streams
Early Learning
Integration
Enterprise
Reuse metrics
R&D Funding
Management
Architectural
Recovery &
Reconstruction
Service
Architecture
Architectural
fragments used in
attempt to stabilize
and future proof early
services
Project ESB
Many common
infrastructure
services
Exploratory Life
Cycle Reference
Architecture
Simple
DIY
Service
Catalogue
SOA Knowledge
management
Process
Change Management for
main classes of service –
focus on stability
Cross organization
architecture board
CBDI SOA
CAPABILITY
ROADMAP
20
Copyright Everware-CBDI Inc.
2006
Completed Service
Portfolio Plan =
ongoing management
mechanism
Reference
Architecture and
policies for all classes
of services defined,
mandated, stable –
enable standard
approaches to
complex problems
Canonical model
is integrated with
business strategy
supporting many
TO BE scenarios
Federated ESB
Federated Service
management
Virtualization of
resources
Cross organization
mechanisms
Assembly environment
Asset
Management
Rich Service Contracts
Reference
Implementation
Proof of Concept
Initial exploratory SOA activity
Service Based
Procurement Agreement
and SOA obligations on
3rd parties
Defined, common life
cycle process
Centralized
Integration
Separation of core
business & utility
service provisioning
Process oriented
services pattern
Dynamic Business
Activity
Management
Registry with automated
Lifecycle governance
Supporting runtime as well
as design time discovery
Enterprise
Registry
Reference and
Implementation
Life Cycle
Architecture
completed
Key governance
requirements
defined
Projects
Componentization of
core applications
Planned time and cost of
business change based
on service product
architecture
Service management
Business Activity
Monitoring
Organization
Reference
Architecture and
policies for all
classes of services
Many mandatory
policies
patterns
Enterprise ESB
Business IT
convergence
Flexibility metrics
Defined
Reference
taxonomy &
Architecture and
classification
policies for Domain
systems
& Utility Services –
Mostly advisory
Core Service Adaptability
policies
Portfolio Plan policy &
Operational
Infrastructure
Life Cycle
Infrastructure
Product and
Process
contribution
Product and
Process
contribution
Central investment in
core business and
utility services
Project ROI
Ecosystem
Façades;
single
component
services;
multichannel
patterns
Repeatable processes deployed to
create basic shared services
capabilities
Federated Service
provisioning
replaced
centralized
integration
Collaborative
process
patterns;
Joined up
business
processes;
metadata
driven
assembly
Policy
Management
Service supply/demand
system in place
Certification for defined
classes of service
Federated Service
Ownership
Resources are utility
Change planned
using automated
simulation and
forecasting systems
linked to process
management
Change Management
policy integrated across
business and IT planning
Institutionalized
knowledge
management
Business signoff on
adaptability
requirements
Service Product
Management
Modified
reward/recognitio
n systems
Real time
mediation;
differentiated
service;
commodity
service patterns
Shared service platform allows wider
collaboration and reengineering of IT
and business
Industry standard
services
Service concept embedded in mature
enterprise practices
© 2007 Everware-CBDI Inc
SOA Excellence Process
SOA Readiness Assessment
= SOA Roadmap Preparation
SOA Adoption Planning

Initial Capability Assessment

Status Assessment

Adoption Strategy

Gap Analysis

Scenario Planning

Capability Planning

Role/Organization Planning

Resourcing & Action Planning
SOA Maturity Assessment
= SOA Roadmap Review
21
SOA Adoption Management
= SOA Management

Ongoing Capability Assessment

Leadership & Governance

Status Assessment

Architecture

Gap Analysis

Process

Infrastructure

Organization

Projects & Programs
© 2007 Everware-CBDI Inc
Summary



22
SOA adoption is a complex change management problem
 Introducing broadly based change
 Into loosely coupled organizations
 That may not immediately recognize the value of the change
Formal approach required
 Maturity Model
 Streams
 Capabilities
 Performance Measurement
 Governance
High correlation with quality initiatives
© 2007 Everware-CBDI Inc
www.cbdiforum.com
Independent Guidance for Service Architecture and Engineering
www.everware-cbdi.com
23
© 2007 Everware-CBDI Inc