SOA Symposium

October 22, 2009Tony Shan

tonycshan@gmail.com

Enterprise Architect/Adjunct Professor

Keane Inc

USA

Agenda Speaker’s Background

SOA Proliferation

Reality Check

Architecture Challenges and Barriers

Pragmatic Framework

Framework Components Inner Ring

Middle Ring

Outer Ring

Summary

Final Thoughts

Q&A2

SOA ecosystem

The Open Group

• Service-Oriented Architecture (SOA) is an architectural stylethat supports service orientation, which is a way of thinking in terms of services and service-based development and the outcomes of services.

OASIS

• SOA is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.

3

Reality Check

56% of executives at companies deploying

SOA admit that at least half of the code or artifacts developed

under their roofs are not reviewed for compliance

before moving into production. (SOA Forum

2007)

32% of those using SOA said those projects fell short of expectations (2007 InformationWeeksurvey of 278 IT pros)

• 58% said their SOA projects introduced more complexity into their IT environments.

• 30% said they cost more than expected.

Only 37% of 106 organizations surveyed actually were realizing

ROI from their investments in SOA

technology and programming. (Nucleus Research 2007 Report)

4

5

Real-world Architecture Complexity

Page 1 of 2

Barriers to Successful SOAInitiatives solely led

and driven by techies

Insufficient semantics in service composition

Disconnection between traditional education and real-

world SOA implementation needs

Absence of holistic roadmaps with

specificity

Lack of well-defined service models (business and

technical)

Gap between logical architecture and

infrastructure

Ad-hoc governance (dictatorship or

anarchy)

Home-grown reference models

Product lock-in with no or limited

interoperability

Inability to quantify ROI/TCO and

improper-sizing

Project-centric execution without

reuse/sharing disciplines

Immature specifications and

standardization

6

7

In Search for a Methodical Approach

Tomorrow’s computing

systems cannot be built using

methods of today. [Computing

Research Association (CRA)

report]

We can't solve problems by

using the same kind of

thinking we used when we

created them. [Albert Einstein]

Conquering Complexity – one of five

“deliberately monumental" research

challenges, each requiring "at

least a decade of concentrated

research in order to make

substantive progress”. [“Grand IT

Research Challenges” report supported

by NSF]

Pragmatic Framework

8

Inner Ring: key principles and tenets

Middle Ring: core methods and models

Outer Ring: best practices and disciplines

Reusable Enterprise System Platform

& Extensible Component Technology

Stack of Standards

New

an

d E

merg

ing

Tech

no

log

ies

Serv

ice-O

rien

ted

Desig

n A

ccele

rato

r

Hybrid Enablement,

Aggregation, Realization, &

Transformation

Serv

ices E

ng

ineeri

ng

& A

rch

itecti

ng

Meth

od

Service Identification,

Discovery, and Ensemble

Por

tfolio

Eng

inee

ring

Servic

e & In

dustry P

attern

s

X-application

Framew

ork

En

terp

rise A

rch

itectu

re

Realig

nm

en

t

Pro

cess

Sta

ndar

ds

Architecture

Abstraction

SOAR Framework

Principles and Tenets

Process standard: enforceable governance process to measure and

monitor the IT development efforts, to assure the

compliance of policies, standards and regulations.

Cross-application framework: common

foundation for sustainable application development

practices and runtime environment infrastructure, to

expedite the delivery and improve the quality of

services.

Portfolio engineering: software/service engineering discipline to generalize and

optimize the technical architecture and

methodology, to better equip IT assets with flexibility and agility in alignment with the

business domain models.

Architecture abstraction: effective model-driven

mechanism to simplify the architecture complexity, to

reduce the total cost of ownership (TCO) of IT

solutions.

9

Inner Ring

Middle Ring

Hybrid Methodology

• A combination of the top-down and bottom-up designs not only provides the forward-thinking direction, but also leverages the existing IT investments to the maximum extent.

Enterprise Architecture Realignment

• A multi-level architecture model effectively copes with the architecture complexity in diverse IT solutions across the lines of business in a large organization.

Service and Industry Patterns

• Systems/applications are categorized into specific groups for efficient portfolio management and cross-application reusability.

Service Identification, Discovery, Ensemble

• The logical service model is built across the lines of business and channels based on the service patterns identified, following the Hybrid Methodology defined.

Services Engineering & Architecting Method

• Service identification, analysis, design, development, composition, operations, rationalization, management and sunset

10

Middle Ring

Core Methodsand Models

Hybrid Methodology

11

Middle Ring

Business Process Model

Service

Process

Choreography

Platform-independent

Technical Model

Platform-specific

Technical Model

ServiceServiceService

Wrapper

Top-down

Decomposed

Consolidated

Bottom-up

Service Composit

ion

& Coordinatio

n Layer

Service

Existing

App

Existing

App

Existing

App

Existing

App

New

Service

Mediator

Existing

App

Collaborative

Computing

Service

Aggregation

Service

Orchestration

Interaction

Portal &

Mashup

Business Operations Model

Screen

Scraping

Service

Existing

App

Enterprise Architecture Realignment Model

12

Enterprise Business & Technical

Architecture

Cross Channel/LOB Architecture

Reusable Enterprise System Platform &

Extensible Component Technology

(RESPECT)

Push Profile

Auto

Enroll/

ICCA

ODPSOnline

Billpay

Online

Banking/

ICID

Kana/

ECCS

PFM/

OFX

- High-level enterprise-wide

business and technical model

- Operation policy and Governance

- Corporate standards & Strategy

- Network, data center, IT security,

infrastructure assets, inventory

- Implementation: service patterns

- Channel-independent functionality

- LOB-neutral business services

- Technical capabilities

- Current and target state

- Roadmap

- Implementation: enterprise service

model

- Domain-specific architecture

- Common foundation

- Address >80% system concerns

- Quality of services

- Best practices

- Implementation: domain-specific

model

- Application-specific architecture

- Business functionality

- Business logic realization

- Implementation: systems/

application architecture

Middle Ring

1

4

3

2

Service & Industry Patterns

13

Pattern Description Characteristics Exemplary Solution Implementation Commonality

P2B Self-

Service

enable users to use the business functionalities via the graphical user interfaces of a thin client (web browsers), thick client (typically Windows GUI applications), and rich client (rich Internet applications) as well as other pervasive platforms like personal digital assistants (PDA) and mobile devices such as cell phones

- Onboarding

- Enrollment process

- E-sign

- E-disclosure

- Profile management

- Customer management

- Alerts via email, pager, & cell

phone

- External services

- Subscription/Shopping cart

- Billing

- Auto Enrollment

- Online Deposit Products Services

- Yodlee service registration

- Alerts subscription

- MyProfile

- Online Banking and Billpay

- Internet Check Card Activation

- Prepaid Debit Card

- Personal Financial Manager

(PFM): Money & Quicken

- Self-service

- User interface

- Predominantly web-based

- Rich Internet Application (Ajax-

driven)

- Web app frameworks

- Transactions

- Statefulness

- Volume

- Real-time response

- Device profiles

P2P

Collaboration

enable users to communicate with other people in an online community or customer services representatives electronically

- Email collaboration

- Secure message box

- Online chat, conferencing

- Agent assistance

- Kana

- Secure

- Alerts

- ServiceProfile

- User-centric

- Social computing

- Web 2.0, e.g. Wiki

P2D Data

Aggregation

enable users to access product information, service details, directory, contents of interest, and data summary

- View e-statements

- Aggregation for service

agents

- Centralized reporting services

- Internet Check Image Delivery

- ServiceProfile

- Reporting

- Data-centric

- Largely read-only access

- Analytics and info aggregation

B2B

Enterprise

enable business partners to collaboratively provide services with seamless navigations between sites

- B2B single sign-on solution

- Supply chain integration for

product/service orders

- B2B partnership

- Yodlee seamless router

- Check Reorder (Harland)

- Onestop shopping

- Credit card (MBNA)

- Partnering

- Federated auth and auz mgmt

- Seamless integration

- rebranding

Front-end

Access

Integration

enable the integration of front ends of servicing applications, typically at the web server tier

- Homepage for online services

- Single sign-on

- Portal for customization and

personalization

- Mashups

- Online Services Homepage

- SSO

- Service representatives portals

(ServiceProfile)

- PFM

- Portal and content aggregation

- Customization and personalization

- Business process automation

- One-time login

Back-end

Application

Integration

enable inter-system integrations and synchronizations

- Synchronous HTTP

- Asynchronous message

queues

- Mainframe access

- Multi-channel adapter design

- Web Services

- MyProfile Web

- Protocol Translation Server

- Push Messaging & message queue

- Kana

- DocCentral

- Cimphony/Tibo/Integration Hub

- Service-oriented

- Scalability and availability

- Interoperability

- Legacy system modernization

- Integration

- Packaged suites

Service Identification, Discovery, & Ensemble

Service mining and repository

•Classification

•Taxonomy

•Reuse rate

•Dependency chain

•Naming convention

•Versioning

•Granularity

•Registry

•Publishing

Enterprise Service Assets

•Core business services

•Specialized business services

•Common business services

Channel Services

•Cross-channel core services

•Cross-channel common services

•Channel-specific services

Technical Services

•Basic technical services

•Advanced technical services

Infrastructure Services

•Operations

•Security

•Management

•Quality

Domain-specific Services

•Shared services

•Atomic services

•Composite services

•Service orchestration

•Service access

14

Middle Ring

Financial Service Model

15

Channel-specific Services

Internet

Channel

ATM

Processing

VRU

Call Center

Branch

Platform

Agent

Access

Lines of Business

Retail Wealth InvestmentSecuritiesCommercial

Basic Technical

Services

Authentication

Authorization

Logging

Component

monitoring

Metrics gathering

Service

management

Application

management

ID management

QoS

Persistence

Advanced Technical

Services

Workflow

Process

orchestration

Grid computing

Caching

Virtualization

Integration

Secure

communication

Self-hearing

Performance

optimization

Session

management

Duplicate requests

Fraud detection

Service Infrastructure

Availability

Throttling

Load balancing

Failover

Content-based

routing

Contextual routing

Service stabilization

Closed loop control

Operations

Auditing

Monitoring

Alerting

Provisioning

Metering

Reporting

Root cause

analysis

Security

Attack prevention

Denial of service

mitigation

Content inspection

Policy management

Privacy protection

Tamper proofing

Nonrepudiation

Access Points

Core Business Services

Banking

Payment processing

Card processing

Customer Relationship Services

Customer management

Contact management

Campaign management

Common Business Services

Rationalized products parity

ATM locator

Funds transfer

Institutional business rules

Advanced Business Services

Transactional services

Account opening

Account transactions

Versioning

Capacity planning

Impact analysis

Tailoring

Cross Channel Common Services

Customer Profile

Check image

eStatements

Check Reorder

Ledger inquiry

Credential recovery/reset

Bill payment

Brokerage

Cross Channel Core Services

Basic access services

Composite access services

Service aggregator

Service transformation

Partner

Access

Internet

Browser/PFM

Email/Pager/

Wireless

phone/Voice

VRU

Telephony

Intranet

Browser/

Rich Client

Blackberry/

Ubiquitous

Devices/PDA

ATM

Kiosk

Branch

Platform

Teller

Middle Ring

Domain-Specific Model

16

Account

Opening

(ODPS)

Non-authenticated Space

Designed by Tony Shan

Service-Oriented Architecture for Internet Channel

ServiceProfile

Customer

/Prospective Customer

/User

Authenticated Space

Online Service

Homepage

(OSH)

Unified

Enrollment

Center

Unified

Message

Center

Unified Internet

Banking

Service Center

Universal

Subscription

Management

Center

Online

Services Enroll

(Auto Enroll)

Alerts

(Push

Messaging)

Electronic

address,

newsletter

(MyProfile)

Web-based

InBox (Secure

Message

Center)

PFM

Internet Check

Image Delivery

(ICID)

Online BillPay

Online

Banking/

eStatement

Profile Data

Services

(eProfile)

Message

Delivery Service

(Push Alert Svc)

PSR

Customer

Service Portal

WDA Message

Archive

Reporting

Center

Client Banking

Service Center

Money

Movement

eDisclosure

Center

SSO

(Log-in App via

PAPI)

Retail Wholesale

Pervasive

Interaction

Service

Online Service

Directory

Universal

Authorization

Service

WDA Message

Service

(Kana)

Service

Communication

(event, queuing,

distributed log)

Service-oriented

Management

(orchestration,

metering/acct)

Service-oriented

Integration

Server

POP3/IMAP

Servers

EmailVoice

Gateway

Media

Gateway

Convergence

Fax

Gateway

WAP

Gateway

Internet Check

Card Activation

(ICCA)

Enterprise

Reporting

Service

Middle Ring

Services Engineering and Architecting Method

17

Acti

vit

ies

Art

ifacts

Inp

uts

Portfolio Assessment

• Business vision and goals

• Existing application portfolio inventory

• Business strategy/architecture

• Technical issues

• User experience requirements

• Nonfunctional requirements

• Stakeholders’ preferences

• Constraints and assumptions

• Business assessment

• Business process modeling

• Technical assessment

• Application asset mining

• Applications portfolio evaluation

• Process-to-capability mapping

• Capability-to-application mapping

• Gap analysis

• Recommendations formulation

• Solution blueprinting

• Current business architecture

• Business issues and NFRs

• Current technical architecture

• Application portfolio metadata

• Root cause of technical pain points

• Process-to-capability mapping matrix

• Capability-to-application mapping matrix

• Target business architecture

• Business and technology implications

Service Analysis

• Business use cases

• Applications suitable for service mining

• Business trust requirement

• Business rules

• Business policies

• Enterprise taxonomy

• Business patterns

• Service meta-model

• Domain decomposition

• Business services identification

• Map application capabilities to services

• Impedance rationalization/consolidation

• Define service granularity

• Classify services

• Service matching

• Rationalize services

• Consolidate services

• Business services

• Application services

• Choreography/Orchestration

• Composition

• Atomic services

• Shared services

• Domain services

• Portfolio/Channel services

• Infrastructure services

• Utility services

Service Modeling

• Enterprise common information model

• Industry vertical services, process, information model (e.g. IFW, IFX, ACORD, ebXML, OAGIS, NGOSS, SCOR)

• Composite patterns

• Service patterns

• Service reference model

• Service encapsulation

• Service contract

• Service data model

• Service usage interface

• Service usage policy

• Service composition

• Service input/output/pre-conditions/Effects (IOPE)

• Service attributes

• Service metadata

• Service-to-component mapping

• Service specification

• Service NFRs

• Service descriptions

• Service flow specification

• Service registration

• WSDL

• Service semantics

• Component specification

• Message and event specification

Service Realization

• Technology and products decision framework

• Service realization decision framework

• Services’ level of reuse

• WS-*

• Application patterns

• Industry model (SCA, SDO)

• Tools

• Wrap existing functionality

• Legacy reengineering

• Build new services

• Componentization

• Identify/select architectural patterns

• Select technology

• Choose products

• Perform proof-of-technology

• Define service deployment model

• Service transaction

• Service reliability

• Service realization rationale

• Service realization decisions

• Service hosting

• Service location

• Service security

• Service quality

• Service publication

Service Assembly

• Enterprise integration strategy

• Integration patterns

• Industry model (OGSA)

• Messaging methods

• Middleware strategy

• Data source

• Enterprise resources

• Security policies

• Integration testing standards

• Service agreement

• Interaction integration

• Portal integration

• Process integration

• Data integration

• Information integration

• Foundation services

• Service mediation

• Service chaining

• Service choreography

• Service orchestration

• Service composition

• Service interoperability

• Service infrastructure

• Integration bus

• Data grid

• Data fabric

• EII solution

• SOA fabric

• SaaS

Service Management

• Service categorization scheme

• Service governance model

• Service addition policies

• Service change policies

• Service maintenance process

• Auditing procedures

• Event management

• SDLC

• Asset inventory

• CMDB

• Project management

• Risk assessment

• Risk mitigation

• Service ownership

• Service versioning

• Service rollout

• Impact analysis

• Service agreement (conversation, financial terms, performance, delivery, exception management)

• Capacity

• Service virtualization

• Service continuity plan

• Application retirement plan

• Service dependency matrix

• Service monitoring

• Service provisioning

• Service metering

• Service configuration

• Resource requirements and availability estimates

• Standards

• Best practice guidelines

Middle Ring

Best Practices & DisciplinesService-Oriented Design Accelerator

• A set of step-by-step recipes, in the form of templates, checklists, cheat sheets, and reference cards, for expedited development of SOA solutions in a cookbook style.

Stack of Standards

• SOA Standards Stack to logically categorize relevant specifications

• Model-driven Architecting Practices

New and Emerging Technologies

• Web X.0

• Cloud Computing

Reusable Enterprise System Platform & Extensible Component Technology (RESPECT)

• Reference implementation model addressing the common design considerations and concerns

18

Outer Ring

Service-Oriented Design Accelerator

19

Outer Ring

Access & Interaction Layer

Integration/Communications Layer

Services & Components Layer

Composite Services Layer

Business Process Layer

Enterprise Resources Layer

Reference Model of Solutions Architecture for N-Tier ApplicationsDesigned by Tony Shan

Jets

peed

Life

ray

JOSSO

Yale

CAS

Acegi

Mo

de

lin

g &

De

ve

lop

me

nt

To

ols

Eclip

se,

Ne

tbe

an

sA

nt, M

ave

nC

VS

, S

ub

ve

rsio

n,

Bu

gzill

a, F

xC

op

JU

nit,

NU

nit,

Cru

ise

Co

ntr

ol

Arg

oU

ML

, S

tarU

ML

Cro

ss

cu

ttin

g A

sp

ec

ts &

Pa

tte

rns

Mic

roso

ft E

nte

rprise

Lib

rary

Mic

roso

ft

Ap

plic

atio

n B

locks

Go

F d

esig

n p

atte

rns

Ja

va

EE

pa

tte

rns

Asp

ectJ

, S

prin

g,

JB

oss A

OP

Ap

plic

ati

on

& S

erv

ice

Fra

me

wo

rks

JS

F,

Ta

pe

str

y,

Wic

ke

tR

IFE

, S

ea

mK

ee

l S

prin

gD

WR

, E

ch

o2

,

JS

ON

-RP

C,

Do

jo

We

bW

ork

, S

tru

ts,

Be

eh

ive

Ho

sti

ng

En

vir

on

me

nt

JB

oss A

pp

Se

rve

rT

om

ca

tX

en

Grid

En

gin

e,

Glo

bu

sL

AM

P

Se

cu

rity

Op

en

SS

HJa

cksu

mO

pe

nS

AM

LE

nh

yd

ra O

yste

rO

pe

nS

SL

Op

era

tio

na

l M

an

ag

em

en

t

Na

gio

sX

MO

JO

DM

TF

CIM

JM

X/S

NM

PW

EB

M S

erv

ice

s

ActiveB

PEL

jBPM

Ope

n-Xch

ange

Shark

JaW

E

WS-B

PEL

jUDDI

ebXM

L Reg

istry

SCA

SDO

Axis

REST, A

jax

Dro

ols

Swee

tRul

es

NxB

RE

Service

Mix

Mul

e

ActiveM

Q

Ope

nJM

S

Ope

n ESB

Der

by

Ope

nCM

S

Sugra

CRM

Mon

dria

n

Wek

a

20

Application Framework Reference Card

Stack of Standards

21

Foundation

Presentation

Management

Composition/Orchestration/Construction

Process

Messaging

XML Processing

DOM

SAX

XPath

XSLT

XQuery

.Net XML

Serialization

JAXB

SDO

StAX

Description

XML

XML Schema

WSDL

XML Info Set

XOP/MTOM

SML

DMCBX

RELAX NG

Schematron

Assertion Lang

Communications and Events

Transport: SSL/

TLS

Network: IPSec

BEEP

HTTP/IIOP/MQ

WS-Eventing

WS-Notification

WS-Addressing

Security

WS-Security

WS-

SecureConversation

WS-Federation

SAML

Liberty Alliance IDFF

WS-Trust

XKMS

XACML

XrML

EPAL

Interoperability

WS-I Basic Profile

WS-I Basic Security

Profile

WS-I Reliable Secure

Profile

Governance

Interoperability

Framework (GIF)

Reusable Asset

Specification (RAS)

DMTF CIM

Resources

WSRF

WSRF-

ResourceProperties

WSRF-

ResourceLifetime

WSRF-ServiceGroup

WSRF-BasicFaults

WS-Transfer

RRSHB

WS-Enumeration

Transaction

WS-Coordination

WS-Business Activity

WS-Atomic Transaction

WS-Context

WS-CF

WS-TXM

WS-TX

Semantics

RDF

WSDL-S

SA-WSDL, SA-REST

OWL-S, RDF/S

SWSO, WSMO

SWSL, WSML

SOA-S, FEARMO,

ODM

QoS

WS-

ReliableMessenging

WS-Reliability

WS-RX

Discovery

OWL

WS-Discovery

WS-

MetadataExchange

UDDI

ebXML

SwSA

WS-Policy

WS-PolicyAttachment

WS-SecurityPolicy

WS-Manageability

WS-Management

WSDM

WS-Provisioning

WSDM

WSRP

XUL

XAML

XBL

XForms

MXML

Ajax

WS-Choreography

BPMN

BPDM

BPML/BPQL

XPDL

WSCI

CDL4WS

BMM

UML

OAGIS

BPEL

WS-CAF

WSE

WCF

JAX-WS

SAAJ

SCA

Axis

SOAP

REST

JSON

SwA

WS-I Attachment Profile

XML Security: XML Encryption, XML Signature

Outer Ring

22

Reusable Enterprise System Platform & Extensible Component Technology

System Architecture

Technology Solutions

System Management

& Governance

Development Lifecycle

23

RESPECT – Common SOA Design Intents, Styles and Considerations

System Architecture: the fundamental organization

and formal description of an IT system, components,

environment, interrelationships, decisions

and their associated rationales about the overall

structure.

Technology Solutions: module-level common

techniques and methods to resolve pervasive design

concerns and issues in an IT system.

System Management & Governance: enterprise-wide administration and

management of distributed computer resources, rules

and regulations as well as a mechanism for compliance

enforcement.

Development lifecycle: a systematic approach to

developing an information system, including

requirements, analysis, modeling, design,

implementation, validation, rollout, training, user

experience, system ownership, and maintenance.

Outer Ring

RESPECT: Body of Knowledge

24

Outer Ring

RESPECT Structure

Sy

stem

Arc

hit

ectu

re

Logical View

Web/Portal server

Process Server

App server

Database server

Integration server/

Middleware/ESB

Physical View

Brand and model,

virtual room

CPU, memory, disk

Network interfaces

SAN storage. SaaS

Server farm, Cloud

Topology View

Fail-over &

redundancy

Network bandwidth

Firewall & DMZ

Disaster recovery

Data replication

Conceptual View

Layer/Tier

Architectural styles

MVC model

Service-oriented

Communication

protocols

Tec

hn

olo

gy

So

luti

on

s

Utility Components

JAX-WS, Axis, WSE

Logging

XML parsing

Charting and

reporting

Configuration data

Integration Mechanism

App connectivity

(EAI, WS, ESB,

SCA)

Integration broker

Data access (DAO)

File transfer & batch

Interoperability

Security Means

PKI, digital cert

Sensitive data

storage and access

Authentication,

authorization, audit

Federated ID mgmt

WS security

Application Framework

Request-based

Component-based

Hybrid

Meta

RIA-based

Composite

Dev

elo

pm

ent

Lif

ecy

cle

Testing

Component-level

Application-level

System-level

Automated unit

testing

JUnit, HttpUnit,

XUnit, Cactus

Build & Deployment

Compilation build

Archive build

Package build

Automated

deployment

Integrated self-test

Tools

Design/Modeling

Development

Profiling & tuning

Configuration

management

Code quality

analysis

Methodology

Unified process

Agile methodology

Portfolio

management

Asset management

Estimation and

capacity planning

Sy

stem

Ma

na

gem

ent

& G

ov

ern

an

ce

Governance

Guidelines,

references, policies

Repository, artifacts

Decisioning model

Design-time

Run-time

Change-time

Quality of Services

Availability

Scalability

Reliability

Usability

Maintainability

Sustainability

Portability

Patterns

Session

management

ID management

Data caching

Coding style

Aspect-Oriented

Programming (AOP)

System Management

Operation process

Monitoring

Backup

Provisioning

Metering

Defect/Issue

management

New & Emerging Technology

25

Outer RingCloudonomic paradigm

Service Integration & Management Platform and Lifecycle Engineering

Cloud Computing Foundation

Principles Methodology Process Techniques Tools Patterns Policy Standards Practices Maturity

Dev

Support

•Collaborati

on

•Asset

Mgmt

•Build Mgmt

•Test Mgmt

•Release

Mgmt

Biz

Support

•Customer

Mgmt

•Partner

Mgmt

•Revenue

Mgmt

•Billing

Mgmt

Operation

Support

•Incident

Mgmt

•Change

Mgmt

•Config

Mgmt

•SLA Mgmt

Provider

Support

•Product

Mgmt

•Inventory

Mgmt

•Capacity

Mgmt

•Resource

Manager

Interaction

Enablement

Virtual Hosting

Runtime

Cloud Service FactoryPlan Define Model Implement Deploy

Channel Device User exp Participate

Onboard Catalog Provision Reports

UI Process Service Data

Security Repository Metering Monitor

Federated Composite Cloud Fabric

AggregateMashup

Bundle

© Tony Shan

Summary – SOA Wisdom

Principles

MethodsThe hybrid methodology

combines the top-down and bottom-up approaches.

A multi-level enterprise architecture realignment model

copes with the architecture complexity progressively.

Service patterns characterizes various business services.

An enterprise service model should be designed from top down, and domain-specific

models should be defined in a bottom-up approach.

Services Engineering & Architecting Method is an

overarching blueprint for SOA execution.

DisciplinesThe service-oriented

design accelerator facilitates expedited development of SOA

solutions in a cookbook approach.

The stack of standards guides the successful

adoption and implementation of SOA via policies, guidelines

and standards.

RESPECT is a best practices knowledgebase to address common SOA

concerns and considerations.

The new and emerging technologies offer

opportunities to augment the SOA capabilities and converge the techniques

and tooling.

26

EngineeringFrameworkStandardAbstraction

27

Final Thoughts What we discussed is just the

tip of the iceberg –complexity in the hidden 80%. use 80-20 Rule.

SOA is NOT a product, book, consultant, tool, vendor, or technology. SOA is a journeyof transformation. Multi-disciplinary theory basis, body of knowledge and practices of services science, engineering, & art.

No miracle cure. Murphy’s Law still holds true for SOA.

28

Q & A

Contact: Tony Shan

Email: tonycshan@gmail.com

Web: http://tonycshan.spaces.live.com

© Tony Shan. All rights reserved.

Thank You

Merci

Grazie

Gracias

Obrigado

Danke Japanese

French

Russian

GermanItalian

Spanish

Brazilian Portuguese

Arabic

Traditional Chinese

Simplified Chinese

Hindi

Romanian

Thai

KoreanMultumesc