10 measures for successful soa implementation

©2008 Symphony Service, Corp. All Rights Reserved. Symphony Services is a registered trademark of Symphony Service Corp. All other trademarks and service marks used herein are the property of Symphony Service Corp. or their respective owners and may not be used without written permission.

High Impact Global Product Engineering SolutionsHigh Impact Global Product Engineering Solutions

www.symphonysv.com

®

10 Measures forSuccessful SOA Implementation

Dr. Jerry A. Smith

©2008 Symphony Services Corp. All Rights Reserved . Proprietary and Confidential www.symphonysv.com

Why We’re Here

Talk a bit about Service-Orientation

Look into why things fail in order to understand how to succeed

Walk through 10 key measures that can lead to successful SOA operations

Some Added Value

Assessing SOA Readiness from a quantitative approach

Leave you with a brief review of the SOA Maturity Model and it’s key benefits

22


What is Service-Oriented Architecture (SOA)?

What is an Architecture?– IEEE 1471-2000: Software architecture is the fundamental organization of a

system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution

What is a Software Architecture?– Architecture is communicated from multiple viewpoints (e.g., topology,

operations, disaster recovery, etc.)

– Collection of the decisions about a software designed to meet the project’s quality attributes

– These attributes include their main components, their main attributes, and their collaboration - often represented abstractly

What is a Service?– Depends upon your point of view

– Work performed by one that helps, serves, or is used by another

– Process of creating benefit through the exchange of tangible assets

33

Put it all together and you get...


SOA Defined

SOA is an architectural style where systems consist of service users and service providers

SOA is a way of thinking in terms of services and service-based development and the outcomes that services bring

A Service– is self contained

– is highly modular and independently deployed

– is a distributed component

– has a published interface

– stresses interoperability– is discoverable, often through directory services– is dynamically bound (implementation does not have to be available at runtime)

44

SOA Turns This... ... Into This


Business Value of SOA

Revenue/Margin

Respond to business changes

Address new needs with existing applications

Unlock existing application investments

Support new channels & complex interactions

Support organic business

Better reuse

Build new client functionality on top of existing business services

Well defined interfaces

Make changes without affecting clients

Easier to maintain

Changes/Versions are not all-or-nothing

Better flexibility

On and on and on…

55

There are a lot of reasons why SOA is of Value


Why Good Things Fail So Bad

It is important to understand why things fail in general– Things fail because of the inherent uncertainties involved in any complex

system ---- Hugh implication to RELIABILITY/AVAILABILITY

– Despite our best intentions, outcomes often do not match desired effects (Errors, Faults, and Failures)

– It is impossible to get around this simple fact, and no amount of intelligent analysis will change the situation

Ways to looks at success and failure– Necessary Conditions

Those characteristics that if not present result in failure E.g., Air is a necessary condition of life

– Sufficient Conditions Those characteristics that if present guarantee success E.g., No one knows all the elements needed to guarantee life

The question becomes...What are the necessary and sufficient characteristics of SOA?

66


Necessary and Sufficient SOA Characteristics

No data exists to indicate there is a sufficient set of conditions for successful SOA implementation (searching for the White Whale syndrome)

SOA implementations fail if it does not take into account a sense of what the current state is (seems to be a necessary condition)

SOA implementations fail if it does not have an understanding of what the future state should look like (seems to be a necessary condition)

SOA implementations fail at an organizational level if it does not mature in a systematic and sustainable manner (seems to be a necessary condition)

SOA implementations fail if it can not govern the overall solution characteristics through which they generate value – This is where measures and metrics fall!

77


10 Key Measures

Corporate– Revenue per service (currency/service)

– Service vitality index (amount of revenue from new services over the last 12 months compared to all service revenue) (%)

Management– Number of new services generated and used as a percentage of total services (%)

– Mean time to Service Development (MTTSD) (time)– Mean time to Service Change (MTTSC) (time)– Service Availability (%)

Project– Service reuse (%)

– Cost of not using or stopping a service (currency, time)

Service– Service complexity, as measured through cyclomatic complexity (unit-less)

– Service quality assurance confidence, derived through service code coverage (%)


SOA Modernization Program - A Systematic Approach

Analyze heritage/legacy capabilities

Gathers wide range of information about existing systems

Consists of 5 major activities– Establish Stakeholder Context

– Describe Existing Capabilities/Assumptions

– Describe Targeted SOA State

– Analyze Ecosystem Gap– Develop SOA Migration Strategy

Key deliverables– SOA Assessment

– SOA Maturity Model

– SOA Reference Architecture

– Modernization Reference Architecture

9


Key Work Products

SOA Assessment– Provides a scoring instrument that will help assess several organizational and technology

aspects that are essential to both mitigate risks and maximize opportunities for business benefits

SOA Reference Architecture– Created during “Describe Targeted SOA State” and updated during subsequent stages as

necessary, but is the basis of the future state Everest Technical/Technology architecture– Defines the idea technological, technical, and organizational state of the system and is designed

to cover all areas of functionality required to support a successful SOA implementation, and it is the result of a logical set of deductions based on the nature and objectives of SOA best-practiced based experience in the real-world issues of deploying SOA-based production solutions.

Modernization Reference Architecture– Created during “Develop Migration Strategy” and updated during subsequent stages as

necessary, but is the basis of the future state Everest Technical/Technology architecture– Defines the mechanisms used transform applications that align with business with reduced total

cost of ownership (TCO) and increased application agility in reacting to business change, while retaining the legacy quality of service that organizations

Modernization Development Product Plan– Created during “Develop Migration Strategy” and updated during subsequent stages as

necessary– Defines the activities, duration, resources, effort, and dependencies needed to systematically

modernize application

10


SOA Assessment

SOA Governance

Methodology

SDLC

Modeling

Tools

Architecture

Security

Quality of Service

Infrastructure11

Portfolio

Skills

Data Model

Organizational Alignment

Metrics

Costing

Strategy

Awareness

Identify area of potential improvement and focus future effort

Quantitative in nature

Assist in determining future effort

Coverage


Targeted SOA Ecosystem

Goal– Gather evidence about potential services that can be

created from heritage/legacy components

– Develop necessary and sufficient characteristics of SOA reference architecture

– Demonstrate how future SOA ecosystem will interact with new and old components

SOA Reference Architecture– Standards, Best Practices, and Guidance– Employed Technology– Deployment Requirements

– Data and State Handling Requirements

– Support Characteristics– Operational Characteristics– Continuity of Operations Characteristics

Service Table - identification of potential services from existing components as well as services that might exist

12126


SOA Reference Architecture

SOA Reference Architecture is an idea target state architecture for an enterprise or line of business.

Often referred to as a Future Vision of the enterprise

Objective is to provide a roadmap to start the journey from the current state to the target state

Three fundamental foundations– Business Architecture

– Infrastructure Architecture

– Information and Data Architecture

1313


SOA Maturity Model

Communication tool that will help coordinate a consistent set of changes across all the functional dimensions of an enterprise

Based on similar principles found in SEI CMMI

5 Level (Ad hoc to Optimized)

Key Benefits: Quantifies the changes that need to

happen based on a systemic perspective Manages expectations of the benefits,

throughout the company Assists in the implementing SOA as a

function of readiness Saves money in that it minimizes the

chances pursuing a single change driver while the rest of the system resist the change

Maximizes the chances that the SOA implementation will be sustainable over the long term

1414


Ecosystem Gap Analysis

Goal– Identify the gap between the existing state and the future ecosystem

– Determine the level of effort/cost associated with legacy/heritage migration

Migration Alternatives Table– Selecting specific components to migration

– Component interdependencies

Key activities– Creation of Component Service Option tables: maps between

existing components and service options– Identify addition data and meta data needs: there are often additional

capabilities added to migration effort and/or concerns over the quality/fidelity of current data sources

– Prototyping and Proof of Concepts: Key assumptions are resolved, high consequence issues are addressed

– Difficulty and risk are identified

15157


Proof of Concept Lab

Lab– Purpose

Reduce project risk through experimental evaluation of technical and technology-based issues of program significance

– Location/Management Distributed Global Agile

– Composition Servers, Networking Developmental software SOA/Application development environment (e.g., Oracle

STS) Everest development environment

Collaboration– Wiki

– SharePoint– Desktop Conferences

161612

CoE (Center of Excellence)–Purpose Technology Leadership

Creation of Product/Process IP

Creation of reusable codes/tools

Competency development and management of best-practices

–Principle Focus SOA, Web Services, Grid, J2EE/Java, Security,

Global Agile


SOA Governance

Lack of reuse

Inconsistent and incompatible services

Increase in sustenance costs

Upgrade challenges and limitations

Lack of regulatory (as in Industry) compliance

Breaches in security, leading to exposure of company proprietary data

1717

SOA governance is about getting people to realize the right services at the right time in the right way

Ung

over

ned

SO

A Im

plem

enta

tion

coul

d le

ad to


Governance Best Practices

There are five critical aspects to governance:– Establish and communicate the enterprise SOA policies (e.g., security,

versioning, publishing, etc.)

– Deploy tools needed to monitor and audit policy compliance

– Review and enforce policies

– Provide visibility into the levels of compliance in the organization

– Improve governance through organizational change

Common Best Practices– Create a board of review

– Develop an interoperability framework first

– Don’t get too granular

– Communicate early and often

– Establish COEs (centers of excellence)

– Create policies with teeth

1818


Summary

SOA is less about the technology and more about organization, architecture, and services

Things fail and they fail for reasons

There are no guarantees in SOA (e.g., sufficient), so stop looking for them

If you don’t know what causes failure in SOA (necessary conditions), then you are doomed to fail

10 key measures should span from top to bottom (corporate to services)

Develop a SOA Roadmap– Assess your current SOA capabilities

– Define your future ideal SOA state

– Understand the difference between where you are and where you need to go– Govern your organizational SOA approach or it will govern you

1919


Comprehensive Product Engineering Services

2020

Commercial-Grade Software

Complete short- and long-term Product

Development Lifecycle capabilities

Strategic Consulting

Experts providing clients with strategic,

operational, and technical guidance

Embedded Systems and Software

Complete short- and long-term Product

Development Lifecycle capabilities


Symphony Services – Credentials

Exceptional Delivery Record

Commercial Software Engineering DNA & Focus

More than 100 clients

More than 300 products under management

Delivered more than 1,000 product releases in 2007

21

Top-notch Staff and Quality Standards World-class talent with more than 3,500 employees

Process maturity rated at CMMI Level 4

6 Sigma process proficiency

Strong IP Protection: ISO 27001 certified

Certified Agile Development personnel

Approximately 600,000 sq ft across 6 delivery centers

Unparalleled Productivity Comparable to “most effective center”

90-200%

Majority of clients 1:1 or better in 6-9 months

Process, focus, technology and monitoring


Questions

2222

Dr. Jerry A. SmithCTO

Phone: 781.547.3667Fax: 781.890.1793

Mobile: 484.467.4959E-mail: [email protected]

1100 Winter Street, Suite 2300Waltham, MA 02451