<Insert Picture Here>

Governing Transformation to SOA

Duško Vukmanović
PrincipalSales Consultant
SOA Roadmap
Providing Guidance and Coordination

• Allow multiple projects to

progress in parallel and
remain coordinated
• Generally, time horizon is
2-3 years
• Depends on enterprise
planning cycles
• Greater detail in near-term
phase • SOA Roadmap consists of 3
• Regularly reviewed and fundamental parts
updated • Program-level efforts
• Incremental improvement • Portfolio of projects that build
• Course correction specific business solutions
• Portfolio of shared services
SOA Roadmap
Three Fundamental Parts
 Building an SOA Roadmap

All roadmap building follows the same four steps:

•Where are we now?
•Where do we want to be?
•What is the gap between the two?
•What is the path to get to where we want to be?

These steps require a consistent measurement to

assess current state and progress toward the goal.

SOA Maturity Model

Oracle’s SOA Maturity Model
Key Concepts
• Oracle’s SOA Maturity Model
includes the following key
concepts:
• Capabilities
• Domains
• Maturity
• Adoption
• SOA Maturity Model remains
technology, standards and
product agnostic.
• SOA Maturity Model includes
over 90+ capabilities.
• Capabilities capture best
practices that Oracle has
collected over many years
working with a wide variety of
companies
• Additional capabilities are
added as more best practices
emerge
• 8 Domains classify & organize
related capabilities
• Capabilities include a
description for each level of
maturity and each level of
adoption
 SOA Capability Maturity Levels
Higher the Level – Higher the Capabilities
Strategic Goals Tactical Plans
Able to support business initiatives Refine and improve standards and
in a timely and cost-effective manner. processes
OPTIMIZED Exploit new business opportunities

Processes and procedures

- 5 - enabled by SOA
Establish key performance indicators
quantitatively managed to drive and manage to those metrics
business value. MANAGED Leverage BAM to improve business

- 4 -
processes.

SOA concepts consistently applied Standardize approach and products

facilitating sharing and reuse Drive widespread adoption
SYSTEMATIC Establish governance

Focused on simple quick win

- 3 - Apply SOA to simple integrations
projects to demonstrate value Select business-driven projects
OPPORTUNISTIC amenable to SOA (e.g. simple portals)

- 2 -
Build confidence with business owners

Experimenting with and learning Get experience building, deploying,

SOA concepts and consuming services
AD HOC
SOA not being pursued
- 1 - Investigate applicability of SOA
NO SOA
- 0 -
 Capabilities that provide the
SOA Capability Domains high-level constructs that
allow SOA initiative to
Capabilities concerned with proceed, i.e. Business
the definitions of the overall motivation, guiding
Capabilitiesand
architecture concerning
guidelines principles, expected costs,
information
for aspects of to
various practitioners funding model, etc..
SOA, e.g. Information
ensure adherence to the as a
Service. This includes
architecture Capabilities concerning the
Business &
shared data models, Architecture development of corporate
Strategy
message formats, competency around SOA
schemas, MDM, content including the organizational
management, etc. structure and skills
Organization
development
Information

Infrastructure Governance
Capabilities concerning the
governance structures and
Capabilities concerning the
Operations, Projects, processes that support and
service infrastructure and
Administration Portfolios & guide the SOA efforts.
tools that provide the
technical foundation for the & Services
SOA initiative. Management

Capabilities concerning Capabilities concerning the

post deployment aspects of planning and building of
solutions based on SOA. services and the service
usage guidelines of service
consumers
 SOA Maturity Model
Measures Maturity and Adoption
Either individual
Optimized
Capabilities or • Measure how
Defines the widely
path an
Domains SOA is beingusually
organization accepted,
embraced,
takes movingand applied
toward
Managed
Exploiting withinmaturity.
SOA the enterprise
• In
SOAlarge enterprises, it is
requires
SOA Maturity Level

Systematic common to have multiple

coordination,
divisions at different
cooperation, and a
Expanding levels of adoption.
common vision to be
Opportunistic
successful.
• For smaller enterprises,
it may be desirable
• Necessary to definetothe
Target Range
Ad-Hoc
Exploring ignore the
strategy adoption
before it is
dimension
possible to and simply
be truly
No SOA
As-Is Phase-1 Phase-2 measure maturity
successful at repeating it
None Project Program Division Cross Enterprise
Level Level Wide Divisional Wide

SOA Adoption Level

 Graphing SOA Assessment Results
Many Different Views Possible

• Spider Graph

• Scatter Plot

• Domain Detail

• Heat Maps

• Etc…

Select the graphics that

convey the information that is
most relevant to the audience
Roadmap Creation Process
Overview

SOA Maturity SOA Goals &

Model Expected Benefits Projects
Complexity vs Effort vs Benefit Analisys

Business & Complexity

Architecture
Strategy
10 9 8 7 6 5 4 3 2 1 0
0.0
7.5 1.0

Information Organization 2.0

4.9 Process 1
3.0
Process 2
1.5 4.0

Effort
Process 3
5.0
Infrastructure Governance Process 4
4.7 6.0
Process 5
7.7 7.0
Process 6
Operations, Projects, 8.0
Administration Portfolios & 9.0
& Services 3.5 10.0
Management

Current Gap Activity

Future
State Analysis Selection &
Vision
Scheduling

SOA Assessment SOA Inhibitors SOA Roadmap

Results & Remedies
Current State
Assessment
SOA Maturity
Model
Business &
Architecture
Strategy

Information Organization

Infrastructure Governance

Operations, Projects,
Administration Portfolios &
& Services
Management

Gather &
Identify Determine Review Assign
Define Interview Perform
Interview Relevant capability
Scope participants Interviews
Schedule Documents Scores

5
Business & Strategy
4 Business
Architecture& Strategy
5
Infrastructure
3 Information

Maturity
4 Portfolios & Services
Projects,
Architecture
2 OA&M
3
Organization
1 Governance
2

0 1
Organization 0 Infrastructure
-1
-1 0 1 2 3 4 5 6
Adoption

OA&M Information

Projects, Portfolios &

Interview
Services
Current Maturity Current Adoption

Schedule
SOA Maturity
Model Scoring
Understanding of the Current State
• Define the scope of the
assessment Business & Strategy
5

• Ultimately the scope of the 4

Architecture
roadmap as well 3
2
• Participants are chosen to ensure 1

that all capabilities within the Organization 0 Infrastructure

SOA Maturity Model can be

accurately scored
OA&M Information
• Existing IT and SOA documents
are reviewed Projects, Portfolios &
Services

• Ask more intelligent questions Current Maturity Current Adoption

during interviews
• Resolve inconsistencies via
interviews • Scores are analysed in the gap
analysis phase
• Score each capability in the SOA
Maturity Model for maturity and
adoption
Future Vision
SOA Vision Definition
• The SOA vision definition
phase focuses solely on the
high level goals and principles
that will be used to guide and
entire SOA initiative
• Detailed future vision is not
something that must be
created prior to creating an
SOA Roadmap
• Initial phases of the SOA
Roadmap can create detailed
vision
• What is goal of the SOA
initiative?
• What is the organizational
scope of the SOA initiative?
• What are the benefits that
SOA is expected to deliver
to the organization?
• What are the guiding
principles for the SOA
initiative?
Future Vision
SOA Goal
SOA Goal Statement
Improve business/IT alignment and drive
business value by measuring and
managing to key performance indicators

Prioritized SOA Benefits SOA Principles

! Rapid Deployment of Applications
! Transition to a Responsive, Flexible & Extensible
Infrastructure
! Ability to support cross functional and cross divisional
processes
! Single Implementation & Enterprise-View of Business
Services
! Service Granularity Recognized by a Business User
! Standardize Process & Technologies
! Compliance to Standards (Enterprise & Industry)
! Data is owned by the Enterprise
! Support cross-functional processes
! Dynamic, Discoverable, Metadata-driven Processes &
Services
! Utilize Standards-based Service Infrastructure Layer
! Access Disparate Data via a Single Consistent Access
Point
! Separation of Business Logic from the Underlying
Technology

Realized Enforced
by across

the
Enterprise-wide SOA Initiative
Gap Analysis
Analyze Gap and Determine Remediation

Domain Spider Capability Scatter Capability Heat

Graph Plot Maps

Identify Identify Identify Determine

Problem Outlier Lagging Remediation
Domains Capabilities Capabilities Activities

Remediation
Activities
 Problem Domains and Outlier Capabilities

• Identify the domains that • Outlier capabilities are capabilities

exhibit the largest gap where the maturity and the adoption are
between current maturity significantly out of sync
and the maturity needed to • Usually indicates a capability that
achieve the SOA goal should receive attention early in the
roadmap
Lagging Capabilities and Remediation

• Capability heat maps can be

used to visually identify low
maturity capabilities
• Not all capabilities are of equal
importance for a particular
organization
• Capabilities may be deemed
unimportant or not applicable

• Remediation activities have been

identified to address the lagging
domains and capabilities
• Remediation activities provide a
primary input into the roadmap
creation process
Activity Selection & Scheduling

Remediation SOA Selection Service Candidate

Activities Project Selection Framework
Framework

Determine Identify Identify

Program Select Service Define
Service
Activities Projects Modifications Schedule
Candidates

Project
Portfolio Service SOA
Portfolio Roadmap
 Roadmap Creation
Determine Program Activities

• Top priority is usually given to No SOA Ad Hoc Opportunistic Systematic Managed Optimized

remediation
Cultural activitiesisthat
resistance often the primary reason for failure in
focus onITthe
enterprise domain with
endeavors. the adoption posture is incremental,
If your
youlowest maturity
will lessen thescore
impact on your organization, customers, and
• Undertake
partners changes
so they in can assimilate change gradually.
series
The Seven oftoiterations/phases
Steps SOA Nirvana, Tom Termini, January 2009

• Duration of each iteration

must
• Be long enough to accomplish
some meaningful progress
• Be short enough to minimize • Iteration must not exceed
risk organization’s ability to absorb
• Maintain a continuous pace of that change
incremental progress
Provide Business Value
Project Selection
• SOA Roadmap must select
projects that:
• Provide measureable business
value
• Are amenable to a service-
oriented approach
• Advance the SOA initiative
• Extend traditional project
portfolio planning with additional
SOA criteria to rank projects
• Consider any new risks
• Select projects considering
costs, complexity, benefits, and
risks
• Benefits in line with the prioritized
SOA benefits
• Adherence to the SOA principles
• Functional needs available from
already existing shared services
• Functional overlap with other
projects
• Data requirements overlap with
other projects
• Ability to leverage existing
service infrastructure
• Infrastructure needs aligned with
the SOA Reference Architecture
Project Selection
SOA Project Selection Framework
• The Oracle SOA Project
Selection Framework
evaluates project
• Effort
• Complexity
• Benefits
• Risks
• Generates a numeric score
used to select projects for the
SOA Roadmap
• The framework is not
intended to replace existing
project portfolio planning
 Identify Service Modifications and Candidates
Service
Modification
• Functionality already
available from existing
services
• Increase the performance
or capacity
• Implement functional
enhancements
• Service modifications need
to be incorporated into the
SOA Roadmap
Service
Candidates
• Projects need to be analyzed
to identify the service
candidates.
• Three primary areas to
analyze:
• Functional overlap between
projects
• Business process tasks that are
common across projects
• Common data requirements
across projects
Service Selection
SOA Service Candidate Selection Framework
• The Oracle Service
Candidate Selection
Framework measures
• Benefits of realization
• Inhibitors to realization
• Generates a numeric score
used to justify Services
Candidates for realization
• Does not determine if the
functionality should be built
• Justifies extra effort to buid a
reusable service
• If not justified, functionality
build by the project
Define Schedule
• The high-level schedule defined • Program-level activities
is the schedule for the entire • Selected projects
SOA initiative that illustrates the • Service modifications
ordering and dependency • Selected service candidates
relationships
1. Determine start date and 3. Determine delivery dates for
duration of the program level service modifications
activities • Generally service modifications
2. Determine start dates for must be available in time for
selected projects project integration testing
• Should not begin in earnest until 4. Determine delivery dates for
program-level activities complete. service candidates
(Some overlap is allowed) • Driven by the needs of the projects
• End date is determined by effort, requiring the new service
complexity, resource availability,
and business needs.
Example SOA Roadmap Phase 1 Schedule
 Example SOA Roadmap Subsequent Phases

Measure progress and communicate results. The successful

implementation of any SOA must be driven from the top down.
This means gaining early wins that engage senior management.
Define three or four metrics and regularly communicate results.
The Seven Steps to SOA Nirvana, Tom Termini, January 2009
 Conclusion

• SOA Roadmap encompasses

• Program level activities
• Project activities

• SOA Roadmap should be based on facts

• Ensures that the roadmap is accomplishing the goal of the
SOA initiative
• Tackle largest inhibitors early
• Focus on early wins to build momentum

• SOA is a journey of discovery and learning

• Iterative approach required
• Evaluate and adjust regularly