New Soa Maturity Model

8/8/2019 New Soa Maturity Model

1/27

.ogss.com

w h i t e p a p e r

a New SerViCe-aNew SerViCe-Ori-

eNteD arChiteC-tUre (SOa) MatU-

>

Progress Sonic

SaaS ar-

ChiteCtUre

>a New SerViCe-OrieNteDarChiteCtUre (SOa)MatUritY MODeL

>


2/27

.ogss.com

tabLe Of CONteNtS

fod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.0 inoducon nd Movon . . . . . . . . . . . . . . . . . . . . . . 1

2.0 w s SOa (Svc-Ond accu)? . . . . . . . . . . . 4

3.0 t SOa Muy Modl . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 SOA Maturity Level 1 Initial Services . . . . . . . . . . . . . . . . .11

3.2 SOA Maturity Level 2 Architectural Services . . . . . . . . . . . . .13

3.3 SOA Maturity Level 3 Business and Colaborative Services . . . . . .15

3.4 SOA Maturity Level 4 Measured Business Services . . . . . . . . .19

3.5 SOA Maturity Level 5 Optimized Business Services. . . . . . . . . .21

4.0 Concluson . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

andx: Ky Conuos. . . . . . . . . . . . . . . . . . . . . . . . .24

To encourage the widespread adoption o the New SOA Maturity Model, you are authorized to copy,

distribute and use (including make derivative works based upon) the SOA Materials or the benet o

you or your company subject to the restrictions set orth herein.

SOA Material(s) means all images, icons, templates, white papers and other materials urnished in

connection with the New SOA Maturity Model, including related text and captions.

You will not remove any copyright or other proprietary rights notices contained in the SOA Materials or

in any related materials provided to you.


3/27

.ogss.com

1

fOrewarD

This whitepaper and the model it presents were created to better

enable organizations in their quest or business agility through service-

oriented architecture (SOA). The SOA Maturity Model outlined in this paperwas specically developed to oer guidance to managers who may be

struggling to communicate the business value o their SOA vision and to be

able to benchmark SOA adoption within their organization.

We look orward to receiving eedback and commentary on

this model, as we will continue to expand its content and share SOA

successes. Enjoy!

1.0 iNtrODUCtiON aND MOtiVatiON

In an environment where the strategic value o IT is questioned1, and

the pressure is on or every IT and sotware development organization to cut

costs, even the discussion o the strategic business value o technology can

get lost. Much attention has been devoted to methods o reducing costs such

as outsourcing and oshoring, but less attention has been ocused on the

business enablement value o new technology.

The goal o this paper is to show how a new approach to designingand deploying inormation technology, specically service-oriented

architecture (SOA), can orm the basis or the technology and business

organizations to work in concert or the improvement o business

perormance along several dimensions including cost reduction and

streamlining the implementation o new business models. More specically,

this paper provides:

A ramework or discussion that enables an organization to>

understand what the path toward adopting a SOA should be

An explanation o the business benets o successul migration>

towards SOA, divided into multiple levels o maturity o SOA

implementation

1Carr, Nicholas G., Does IT Matter?, Harvard Business School Press, 2004.


4/27

.ogss.com

2

A meaningul vocabulary and context around which an organization>

may seek alignment between IT and the business

The basis upon which an organization may build a roadmap towards>

true business agility through successul adoption o SOA

SOA is an approach to designing, implementing, and deploying

inormation systems such that the system is created rom components

implementing discrete business unctions. These components, called

services, can be distributed across geography, across enterprises, and

can be recongured into new business processes as needed.

All claims or new technology are subject to skepticism, so what

makes SOA dierent rom other approaches o the past? The key actors are:

SOA is built on the standards o the World Wide Web, leading to>

cost-eective implementations on a global basis with broad support

by vendors.

Services are loosely coupled, allowing or much more fexibility>

than older technologies with respect to re-using and re-combining

the services to create new business unctions both within and

across enterprises.

SOA best practices create designs that embody business processes>and enhance the ability to outsource and extend processes to

business partners.

SOA encompasses legacy (i.e., existing) systems and processes so>

that the useulness o existing investments can be preserved and

even increased.

This combination o actors makes SOA an approach that provides

a winning strategy or all stakeholders as:

The nance organization sees cost-eectiveness.>

The business organization sees enhanced and expanding business>

models (as shown later in examples).


5/27

.ogss.com

3

The IT organization sees success in supporting its customers, meeting>

service goals, and having the fexibility to respond to uture demands

through increased agility.

Corporate governance sees improved alignment o IT and business.>

As companies look to the challenge o guring out how to obtain the

benets o SOA, how to justiy the required investments, where to begin,

and what vision to aim or, guidance is required. The solution presented in

this paper is the introduction o a SOA Maturity Model (SOA MM) to show

the increasingly positive impact that SOA adoption can have rom a business

perspective. The SOA MM derives rom three key inspirations:

The successes o the Capability Maturity Model>

(CMM) and newer

CMM Integration (CMMISM)2 rom the Sotware Engineering Institute

(SEI) in providing a common ramework or dening and assessing

process improvement in sotware and other engineering endeavors

Papers such as those by Randy Hener o Forrester Research>3

,

showing the various successul paths taken by companies

introducing SOA.

The success o our customers in the deployment o SOA projects.>

By putting SOA into a ramework similar to the Capability Maturity

Model

, we can show the goals, characteristics, and prerequisites to SOAs

business impact progressing through levels as ollows:

NewFunctionality

Cost ReductionBusiness

ResponsivenessBusiness

TransormationBusiness

Optimization

The SOA MM includes goals, characterization o the scope and

business benets o each level, the important industry standards, key

practices, and critical success actors, both technological and organizational.The SOA MM thus provides guidance to set SOA vision and a benchmark to

measure progress.

2Sotware Engineering Institute, Capability Maturity Model Integration, http://www.sei.cmu.edu/cmmi.

3Hener, Randy, Your Paths to Service-Oriented Architecture, Forrester Research, Dec. 2004.


6/27

.ogss.com

4

Forrester Research has ound that companies approach SOA through

dierent paths, each with dierent business benets, skills, and technology

inrastructure requirements. For some companies a ocus on internal

integration and workfow is most important, while or others a ocus on

partner integration is most important. As companies pursue the specic pathsappropriate to their needs, they can correlate their paths with the maturity

model to see the organizational needs, technology needs, and goals as they

move up the levels o SOA maturity.

2.0 what iS SOa (SerViCe-OrieNteD

arChiteCtUre)?

SOA is an evolution o distributed computing designed to allow the

interaction o sotware components, called service, across a network.

Applications are created rom a composition o these servicesand

importantly, the services can be shared among multiple applications.

For example, a Human Resources management application could be

created rom the ollowing services:

An Employee Administration Service to manage hiring, changes in>

status, and termination

A Salary and Review Administration Service to manage salaries and>

employee perormance reviews according to corporate standards

A Benets Administration Service to initiate and terminate benets,>

and to process the annual enrollments

An IT Security and Provisioning Service to manage the addition and>

removal o access rights or employees according to their role and

employee status

A Payroll Service provided securely over the Internet by an>outside provider


7/27

.ogss.com

5

An HR Department Portal Service providing a Web browser-based>

user interace or members o the HR department presenting the

unctions o the above services

A Business Process Management Service to manage the approval>

and notication processes

With SOA, organizations can achieve greater reuse o existing assets

and can respond aster to change requests. These benets are attributed to

several critical elements o SOA:

The seres reet logal bsness attes.> Each service

typically perorms multiple operations or a specic business

unction such as a Payroll Service providing operations including

issue checks, issue W2s, and provide payroll period report.

Importantly, these services, oten reerred to as course-grained,

refect business process concepts, not the capabilities or ne-

grained APIs dened by traditional packaged sotware applications.

Ne seres an be added or reated b omposng>

exstng seres thot mpatng the exstng sere

mplementatons4

. So, in the example above, an Employee Sel-

Service component could be added making use o the existing

services, ltering data and operations to those appropriate or the

sel-service users. This allows or an incremental deployment

approach in implementing services.

The seres an be on heterogeneos sstems aross>

netorks and geograph, prodng platorm ndependene

and loaton transparen. There is no need or each service to

be implemented using the same sotware or hardware technology

nor to be on the same network or in the same location. The Salary

and Review Administration Service could be implemented in a

COBOL environment on a Linux/mainrame server in one locale

while the IT Security and Provisioning Service could be implemented

in a Microsot .NET environment on a Windows server in a

dierent locale.

4Care must be taken with respect to security and service-level agreements (SLA) when adding new consumers to existing services


8/27

.ogss.com

6

The seres ommnate b standard protools prodng>

broad nteroperablt. Most commonly, especially or connecting

heterogeneous systems, these are protocols based on World Wide

Web standards. Web services are the implementations o services

using these standards. Amazon and eBay are high-prole examples ocorporations that have made their core applications accessible over

the Internet as Web services.

Lega applaton sstems an be ntegrated as a sere>

leeragng exstng nestments. SOA technology provides

mechanisms to ront-end (or wrap) existing systems behind a

services interace with no changes to the existing system. In addition

traditional ERP vendors are quickly exposing their applications

unctionality as Web services.

Seres hae an nterae and are message-orented.> The

unctionality provided by services is dened by metadata describing

the interace to the service and its operations. Inormation is

transmitted to and rom services as messages. The ocus in the

denition o the interace and messages is in what a service does

rather than how. The how is internal to the implementation o the

service. SOA applications are usually designed to be event-driven,

responding to the messages as they arrive.

An implementation o SOA relies on skills, methods, and a SOA

inrastructure to support the SOA application in a reliable, scalable, and

secure manner. Some o the basic elements o this new approach include:

Analss, desgn, and mplementaton methodologes> to guide

project managers, developers, and IT operations personnel in the

rapid design, assembly, and reuse o SOA components

Modelng, onfgraton, testng and deploment> tools to

speciy and create the services and then dene business processes

which orchestrate those lower level services into coarse grained

business services

5Chappell, David, Enterprise Service Bus, OReilly, 2004


9/27

.ogss.com

7

Enterprse sere bs> (ESB)5

to provide reliable, scalable,

distributed communications and data transormations between

services as well as providing adapters to legacy technology and

various vendor implementations

Seres and pol regstr and repostor> to provide a common

place to organize, understand, and manage SOA inormation including

a catalog o available services, their interace denitions, and policies

governing the use o services

Prosonng and nrastrtre management> Tools to provide

Business Process Visibility (BPV) across a widely distributed

SOA inrastructure

Rntme goernane> to dene and control security and business

policies and enorce regulatory compliance across tiers o sotware

in a way which refects the underlying business processes

3.0 the SOa MatUritY MODeL

The introduction o SOA can provide a ocus or the technology and

business organization in a company to meet common goals o the enterprise.

A SOA Maturity Model can provide goals and guidance on how SOA can have

an increasingly positive impact on the enterprise.

Figure 1 shows the ve levels o SOA Maturity along with the key

business impact progressing rom least to most mature as ollows: Initial

Services, Architected Services, Business Services and Collaborative

Services (two dierent ocuses at level 3), Measured Business Services,

and Optimized Business Services. Also shown or reerence are the

corresponding CMMISM

levels6

.

6In very short summary: CMMISM Perormed means that needed unctions are perormed, CMMISM Defned means that standard

processes are defned, CMMISM Managed means that the standard processes are implemented and managed, CMMISM

Quantitatively Managed means that the results o the processes are measured against goals, CMMISM Optimizing means that

there is a continuous improvement process implemented based on the measurements.


10/27

.ogss.com

8

5

43 a b2

OptimizedBusinessServices

CMMISM

OptimizingOptimization

Transformation

Responsiveness

Cost Effectiveness

Functionality

CMMISM

Quantitatively

Managed

CMMISM

Defined

CMMISM

Managed

Measured BusinessServices

Architected Services

Initial Services

BusinessServices

CollaborativeServices

1CMMISMPerformed

Table 1 shows the key attributes o each maturity level including

business impact, scope, critical success actors, and relevant standards.

Consistent with the approach taken by the SEI or the Capability Maturity

Model

, Key Goals and Practices or each SOA maturity level are specied

in Table 2. Attainment o these goals and the implementation o these

practices are the measures as to whether a maturity level has been attained.

Each maturity level has as a prerequisite the goals and practices o the

lower levels.

It will oten be the case that particular goals will be achieved,practices implemented, and technologies used at levels lower than those

shown in Tables 1 and 2. This is to be expected and encouraged according

to the priorities o the enterprise.

Subsequent sections will examine each o the SOA maturity levels.

Figure 1

Service-Oriented Architecture

Maturity Model Levels with

Key Business Impact


11/27

.ogss.com

9

tabLe 1: SOa MatUrit Y MODeL

Maturity Level Prime BusinessBenefts

Scope Critical TechnologySuccess Factors

Critical People& OrganizationalSuccess Factors

SelectedRelevantStandards

1. Initial Services New unctionality R&D experimentation,Pilot projects, Website, Portal, Customintegrations, Smallnumber o services

Standards, LegacyIntegration

Developers learnservice developmentskills

Developer ManagerSponsorship

XML, XSLT,WSDL, SOAP,J2EE, .NET

2. ArchitectedServices

IT cost reductionand control

Multiple integratedapplications

Support or heterogeneityand distributed systems,Reliable Messaging,Mediation, Ease odeployment, Databaseintegration, Versioning,Internal Security,

Perormance management

Architecture groupprovides leadership,SOA CompentencyCenter

CIO Sponsorship

UDDI, WS-ReliableMessaging,WS-Policy,WS-Addressing,XQuery, Security,SAML

3.a. BusinessServices

Businessresponsivenesschange businessprocesses quicklyand eectively

Business processesacross business unit orenterprise

Reuse, Ease o modication,Availability, Businessprocess rules, Event-drivenprocesses, Compositeapplications

IT Partnershipwith BusinessPartnership acrossOrganizations,SOA Lie-cycleGovernance,Executivecommitment, Event-driven design skills

Business UnitManagerSponsorship

WS-BPEL

3.b. CollaborativeServices

Businessresponsivenesscollaboration withbusiness andtrading partners

Services availableto external partners,Cross-enterprise

External services enablement,Cross-enterprise, Translationo cross-enterprise protocols,Long-running transactions

RosettaNet,ebXML, WS-Trust

4. MeasuredBusinessServices

Businesstransormationrom reactiveto real-time,Meet businessperormancemetrics

Business unit orenterprise, Cross-enterprise

Business ActivityMonitoring, Event StreamProcessing, Complex EventProcessing, Event-drivendashboards and alerts

On-going businessprocess evaluationand response

CFO sponsorship

5. OptimizedBusinessServices

Businessoptimizationreactand respondautomatically

Business unit orenterprise, Cross-enterprise

Event-driven automation oroptimization

Continuousimprovement culture

CEO sponsorship


12/27

.ogss.com

10

tabLe 2: SOa MatUritY MODeL GOaLS aND KeY

praCtiCeS

Maturity Level Key Goals Key Practices

1. Initial Services 1. Learn SOA technology in R&D and pilot projects.

2. Apply SOA technology to immediateorganizational needs.

3. Dene initial ROI measurements or SOA projectsand apply to initial projects.

1. Create services denitions.

2. Integrate SOA into project development methodology.

3. Quantiy costs, time, and business benets o pilotprojects.

2. ArchitectedServices

1. Institutionalize use o SOA.

2. Put in place architecture leadership or SOA.

3. Prove returns rom use o standards technology.

4. Anticipate use o SOA inormation or businessoptimization.

1. Speciy technology standards or SOA.

2. Integrate SOA into organization-wide developmentprocess.

3. Provide organization-wide SOA training and competencycenter.

4. Use incremental integration.3.a. Business

Services1. Create ongoing partnership between business

and technology organizations or SOAgovernance.

2. Support ull business processes via SOA.

3. Prove returns rom reuse o services andresponsiveness to change.

1. Speciy policies or use o SOA in creation or modicationo business processes.

2. Take advantage o event-oriented and mediationunctionality o SOA technologies, especially with regardsto enhancing/extending business processes.

3.b. CollaborativeServices

1. Create ongoing partnership between businessand technology organizations or SOAgovernance.

2. Extend SOA business processes to external

organizations.3. Prove returns rom use o services or

collaboration.

1. Speciy policies or use o SOA in collaboration withbusiness and trading partners.

2. Implement cross-enterprise security.

4. MeasuredBusiness Services

1. Institute transormation rom reactive to real-timebusiness processes.

2. Dene and meet business-oriented perormancemetrics.

1. Collect and analyze business process-oriented real-timeperormance metrics.

2. Implement ongoing business process evaluation andre-engineering.

5. OptimizedBusiness Services

1. Provide enterprise-wide leadership or businessand SOA governance.

2. Prove returns rom SOA-supported continuousimprovement.

1. Implement sel-correcting business processes.


13/27

.ogss.com

11

3.1 SOA MATuRiTy LEvEL 1iNiTiAL SERvicES

SOA Maturity Level 1 is Initial Services (see Table 1 and Table 2).

Initial Services represent the initial learning and initial project phase o SOA

adoption. Projects here are typically done to simultaneously meet a specic

need to implement unctionality while trying out specic technologies and

an approach to SOA. This maturity level also includes initial R&D activities

testing the SOA technologies in a laboratory environment. Usually, the initial

introduction o SOA is driven by the application development organization

oten as part o an application integration project. New development skills are

learned and initial attempts at quantication o ROI are created.

This is the level at which the most basic o SOA standards rom W3C7

are introduced, such as XML or denition o message ormats, WSDL orservice interace denition and SOAP or invocation o services.

NewCRM

Application

SalesForecasting

and TrackingService

ServicesInterface

ServicesInterface

ServicesInterface

INTRANET

PORTAL USER

MAINFRAME

HOSTED

BUSINESS-ORIENT

WEB SERVICES

REQUEST

SalesManagement

PortalServer

INTERNET

REPLY

PORTAL USER

7World Wide Web Consortium, Web Services Activity, http://www.w3.org/2002/ws/.

Figure 2

Example Application or Maturity

Level 1: Initial


14/27

.ogss.com

12

A typical example o an initial services project as shown in Figure 2

is to link a corporate sales orce Web portal directly to both a legacy sales

orecasting system running on the mainrame and a new CRM application

exposed as a Web service.

In this example the ollowing SOA inrastructure component could

be used:

A Manrame integraton Sere> such as the Progress

DataDirect

Shadow RTE providing bidirectional standards-based

Web service access to a legacy sales orecasting system hosted

within CICS on an IBM mainrame running z/OS

A Hghl Prodte Deelopment Platorm> optimized or the

creation o service-oriented business applications such as Progress

OpenEdge

to develop and host new CRM application logic that is

accessible as Web services

The key benets o this initial project are to provide the business

unctionality required while also learning how to develop and deploy a basic

SOA application. Such an implementation would use the SOAP protocol

between the portal server and the supporting services, as well as or the

Sales Forecasting and Tracking Service to obtain inormation rom the

CRM Application.

However, even a basic initial application could benet rom using

some o the key additional SOA inrastructure components. Beyond the

learning gained rom using the technologies early, the most important reason

or the introduction o these advanced technologies on initial projects is to

put in place scalable technology so that as SOA encompasses more business

unctions, the right oundations are in place. For example, Figure 3 shows this

same example with the addition o:

A Rntme Goernane Sere> such that o Progress

Actional

which provides the monitoring and control mechanism to apply

service and security policies to all steps within a business process

across heterogeneous SOA inrastructure elements.


15/27

.ogss.com

13

An Enterprse Sere Bs> (ESB) such as the Progress

Sonic

ESB,

which provides a standard interaction model or SOA components

including Web services and relational databases as a scalable, easy-

to-deploy distributed inrastructure. The ESB provides a large number

o adapters to allow services implemented in disparate technologiesto interchange messages allowing, or example, a .NET application to

communicate with a J2EE application at a services level.

A Seres Regstr> supporting the UDDI standard. This provides

a central store o service denitions across initial projects and

provides a single point o reerence or service developers to

obtain services denitions.

INTRANET

Enterprise Service Bus

SalesForecasting

and Tracking

Service

NewCRM

Application

RuntimeGovernance

Service

ServicesInterface

ServicesInterface

Sales

ManagementPortalServer

ServicesInterface

Services

Registry

ServicesInterface

ServicesInterface

INTERNET

PORTAL USER

PORTAL USER

ADMINISTRATOR

3.2 SOA MATuRiTy LEvEL 2ARcHiTEcTED SERvicES

SOA Maturity Level 2 is Architected Services (see Table 1 and Table

2). It is at this level that standards are set as to the technical governanceo SOA implementation, typically under leadership o the architecture

organization. The key business benet o this level is development and

deployment cost reductions through the use o SOA standard inrastructure

and components as compared to using older technologies or costs

Figure 3

Enhanced SOA Inrastructure or SOA

Maturity Level 1: Initial


16/27

.ogss.com

14

accumulated through multiple unique one-time projects. These benets are

greater in the heterogeneous environments typical o most enterprises.

Based on the learning and eedback rom the initial services at

Maturity Level 1, architectural standards and standard implementation

technologies are dened. For example, standards are set or:

Enterprise SOA protocols to be used chosen rom industry standards,>

particularly those o W3C, OASIS8

and WS-I9

Implementation platorms to be used>

Policies including reuse, runtime governance, compliance and>

security policies

Technical review process or denition o new services and reuse o>

existing services

Figure 4 shows an example o an SOA deployment at Maturity Level

2 or a nancial trading example. Maturity Level 2 includes the use o key

components shown previously in Figure 3 including the runtime governance

service and the enterprise service bus as well as the additional key aspects o

this example:

A> Repostor, which extends the Services Registry to provide

storage or SOA artiacts and policies inormation. Liecycle support

such as access controls, versioning, and deployment tools are also

important characteristics to consider here. Usage o such a repository

with both development and runtime support is part o Maturity

Level 2Architected Services.

A modied> Rntme Goernane Sere, which identies services

and dependencies providing the proper oundation to detect, diagnose

and automatically remedy both system and application-level errors.

A> Message Transormaton Serewhich allows the integrationo services with dierences in expected message contents or

ormats. This is oten done by the invocation o XLST transorms

applied to an XML messagein this example as a mediation

unction under the control o the ESB.

8OASIS, OASIS Committees by Category: Web Services and SOA, http://www.oasis-open.org/committees/tc_cat.php?cat=ws.

9WS-I, Web Se rvices Interoperability Organization, http://ws-i.org


17/27

.ogss.com

15

A> Sngle Sgn-On Seresupporting user authentication and

authorization across the organization. Such a service, typically

supplied by a vendor, could be based on the OASIS SAML standard

or the exchange o authentication and authorization inormation.

RepositoryUser

Directory

Single Sign On

Trading System

OrderManagement

Service

FundsTransferService

RuntimeGovernance

Service

Agent

StockExchange

ECN

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterfaceServicesInterface

Enterprise Service Bus XML

INTRANET

ServicesInterface

ADMINISTRATOR

3.3 SOA MATuRiTy LEvEL 3

Business Services and Collaborative Services

The ocus o SOA Maturity Level 3 is on the partnership between

technology and business organizations in order to assure that the use o

SOA provides clear business responsiveness. Core to the value o SOA is

the linkage between business processes and digital processes as shown in

Figure 5.

Figure 4

Example Application or SOA

Maturity Level 2: Architected Services


18/27

.ogss.com

16

Service Delivery Network

SampleProcess

DigitalServices

DIGITALWORLD

ServicesCorrelate to

Process Steps

Services CallInitiates

Digital Processes

PHYSICALWORLD

DigitalProcesses

CreateCustomerOrder

ReserveInventory

ScheduleProduction

CreateShippingOrder

ScheduleShipment

CreateSupplierOrder

CreateSupplierOrder

ScheduleProduction

CreateShippingOrder

CreateCustomerOrder

ScheduleShipment

ReserveInventory

SOA Maturity Level 3 is dened with two complementary paths to attaining

these goalstwo, Business Services, ocused on the improvement o

internal business processes, and one, Collaborative Services, ocused on the

improvement o collaborative processes with external partners. (See Table 1

and Table 2.) Certainly both can be done to get the greatest advantage rom

SOA, but Maturity Level 3 can be attained through either path; both provide

improved business responsiveness.

Figure 6 shows an example o an SOA deployment at Maturity Level 3or nancial trading. Key to this Business Services implementation is:

Bsness Proess Management> (BPM)the management o

long-running processes involving sequential messages between

services. This could be done or example by the Progress

Sonic

Orchestration Server, which can manage the state o each process

along with intermediate results.

10The Big Strategic Impact O Organic Business And Service-Oriented Architecture, Forrester Research, Inc., June 2004.

Figure 5

SOAs Source o Power: It Models

Business Processes (adapted rom

Forrester Research10

)


19/27

.ogss.com

17

RepositoryUser

Directory

Single Sign On

Trading System

CallCenter

Service

OrderManagement

Service

FundsTransfer

Service

OrchestrationService

RuntimeGovernance

Service


ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

1 2

43

StockExchange

ECN

XML

Agent

ServicesInterface

Figure 7 continues the evolution o Business Services with the addition o:

Straghtorard enhanement o bsness proesses.> A

principal advantage o SOA is its enablement o business process

modication through the reconguration o services. In this example,

a new Compliance Service required or regulatory compliance is

inserted in the message fow between the Order Management

Service and the Trading Service without any changes to theimplementations o the existing services.

Rese o seres.> In this example, reuse is shown as through a

multi-channel application (e.g., provide access to the same application

through dierent customer communication methods) in which the

Order Management Service is shared by both the Call Center Service

and the Online Service.

Figure 6


Maturity Level 3: Business Services


20/27

.ogss.com

18

RuntimeGovernanceService

ServicesInterface

OrderManagement

Service

ServicesInterface


ServicesInterface

INTERNET

CUSTOMER

Agent

StockExchange

ECN

ServicesInterface

CallCenter

Service

ServicesInterface

OnlineService

Repository

ServicesInterface

XML

ServicesInterface

UserDirectory

Single Sign On

ServicesInterface


ServicesInterface

ComplianceService

ServicesInterface

TradingSystem

1

2

3 45


CUSTOMER CUSTOMER

The alternative ocus at Maturity Level 3 is Collaborative Services with a

ocus on linking with external partners. Figure 8 shows an example in which

the trading company expanded into a new business o oreign exchange

transactions oered over the Internet.

Key eatures in this implementation o Collaboration Services include:

Use o standard> SOA protools spportng spef bsness-to-

bsness (B2B) ntonaltsuch as those dened by RosettaNet11

,

which includes standard XML messaging unctions or such cross-

enterprise operations as obtaining product inormation, obtaining

inventory inormation, and ordering.

A collaboraton Sere> would implement the B2B protocols and

support necessary transormations between the messages used

internal to the enterprise and those needed or external processes.

11 RosettaNet, Standards, http://rosettanet.org/standards

Figure 7

Continued Evolution o Application

or SOA Maturity Level 3:

Business Services


21/27

.ogss.com

19

The Electronic Crossing Network (ECN) connection has> moed rom

a propretar protool to a standard ndstr seres protool

and hence is managed through the Collaboration Service.

ServicesInterface

Repository

ServicesInterface

ServicesInterface

UserDirectory


ServicesInterface

ComplianceService

ServicesInterface

TradingSystem

ForeignExchange

Service CollaborationService

RuntimeGovernanceService

ServicesInterface

ServicesInterface

ServicesInterface

OrderManagement

Service

ServicesInterface


ServicesInterface

INTERNET

INTERNET

Agent

StockExchange

ECN

ForeignExchangePartners

CallCenterService

OnlineService


ServicesInterface

ServicesInterface

ServicesInterface

CUSTOMER CUSTOMER

3.4 MATuRiTy LEvEL 4 MEASuRED BuSiNESS SERvicES

While SOA Maturity Level 3 ocuses on the implementation o

internal and/or external business processes, SOA Maturity Level 4 ocuses

on measuring and presenting these processes at the business level so as to

provide continuous eedback on the perormance and business impact o the

processes implemented at Level 3. (See Table 1 and Table 2.)

Figure 9 shows an example process to congure, order and

manuacture, with services or each key unction distributed across

geographic locations.

Figure 8

SOA Maturity Level 3:

Collaboration Services


22/27

.ogss.com

20

Key eatures in this example are:

Real-tme Eent Stream Proessng,> which in this example

collects all RFID events into an event database and lters out the

business-meaningul events based on rules and orwards them on

or use in other services. As explained in The Power o Events12

and

Event Stream Processing-A New Physics o Sotware,13

event

stream processing and complex event processing allow the

transormatono business processes rom being reactive to being

based on real-time intelligence.

Bsness Proess vsblt> , which empowers you to manage your

SOA rom a business process perspective. Business process visibility

allows business and IT users to gain a comprehensive view o

individual business processes and their supporting business services

and IT inrastructure, while simultaneously enorcing policies at the

business process level.

12Luckham, David, The Power o Events, Add ison-Wesley, 2002.

13Palmer, Mark, Event Stream Processing-A New Physics o Sotware, DM Direct Newsletter, July 29, 2005,

http://www.dmreview.com/editorial/newsletter_archive.cm?nl=dmdirect&issueid=20226.


23/27

.ogss.com

21

INTRANET


ServicesInterface

INTERNET

ServicesInterface

Repository

RuntimeGovernance

Service

BusinessProcessVisibility

(BPV) Service

Configureand Order

Service

All EventsMeaningful Events


Plant RFID

Materials and

In-Process

Tracking

Service

ServicesInterface

Fulfillment

Service

ServicesInterface

RFID EventStream

ProcessingEngine

Event

DB

Rules

ServicesInterface

ServicesInterface

ServicesInterface

CUSTOMER

CUSTOMER

MANAGER

3.5 MATuRiTy LEvEL 5OPTiMizED BuSiNESS SERvicES

SOA Maturity Level 5, Optimized Business Services SOA, adds

automatic response to the measurements and displays o Level 4. In this way,

the SOA inormation system becomes the enterprise nervous system and

takes action according to events occurring at the business level according torules optmngbusiness goals (see Table 1 and Table 2).

Figure 10 shows the congure, order, and manuacture process

enhanced to provide dynamic pricing according to the status o materials

and in-process work in the manuacturing plant. For example, i parts or a

particular version o an item are in short supply, pricing can be created to

encourage purchasers to order an item using alternative parts. This example

is inspired by the success o Dell Corporations use o dynamic pricing in

which a shortage o a particular capacity disk drive, or example, causes the

dynamic creation o a special oer to encourage buyers to congure and

purchase a computer with a larger drive14 15

. Using SOA components allows

such an approach to be more easily implemented and evolved than through

Figure 9


Maturity Level 4: Measured

Business Services


24/27

.ogss.com

22

the construction o proprietary systems. With realization o Level 5 Maturity,

an organization should see true competitive advantage by leveraging in real

time the fow o inormation within their enterprise SOA to increase revenues,

reduce costs, and respond to unanticipated events in an automated ashion.

INTRANET

Enterprise Service Bus Enterprise Service Bus

PricingService

FulfillmentService

Plant RFIDMaterials and

In-ProcessTrackingService

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

ServicesInterface

INTERNET

Repository

RuntimeGovernance

Service

BusinessProcessVisibility

(BPV) Service

Configureand Order

Service

All Events

Dynamic Prices

Orders

MeaningfulEvents

RFID EventStream

ProcessingEngine

Event

DB

Rules

ServicesInterface

ServicesInterface

ServicesInterface

CUSTOMER

CUSTOMER

MANAGER

4.0 CONCLUSiON

The SOA Maturity Model provides a ramework supporting both the

vision and the assessment o increasing levels o business benets rom the

adoption o SOA. The levels and key benets are as ollows:

14Friedman, Thomas L., The World is Flat, Farrar, Straus and Giroux, 2005.

15McWilliams, Gary, Lean Machine: How Dell Fine-Tunes Its PC Pricing to Gain Edge in a Slow Market, The Wall Street Journal,

June 8, 2001.

Figure 10


Maturity Level 5: Business

Optimization


25/27

.ogss.com

23

5

43 a b

2

1

OptimizedBusinessServices

Measured BusinessServices

Architected Services

Initial Services

BusinessServices

CollaborativeServices

BENEFITS

Optimization

Transformation

Responsiveness

Cost Effectiveness

Functionality

Key to the success o SOA introduction and subsequent success isan evolving partnership between the technology and business organizations.

This partnership is predicated on the ability or the technology organization

to support the business in both responding to competition and in rapidly

implementing new business models such as new distribution channels, new

inormation services products and new pricing modelsall with continuously

improving metrics such as protability and customer satisaction.

The goal o SOA is to allow this business agility in a way dierent

and better than previous technologiesdierent due to the capitalization

on Web standards, due to the inherent fexibility o SOA design, due to the

inclusion o legacy systems, and due to the availability o o-the-shel SOA

inrastructure and services. Ultimately, a companys success in achieving an

increasing level o maturity will depend on the methodology and rigor that is

either created within the enterprise or ast-tracked by engaging a

systems integrator.


26/27

.ogss.com

24

appeNDiX

REALiziNG SOA MATuRiTy wiTH PROGRESS SOFTwARE

The ollowing chart outlines how the Progress products relate to

each level o the Maturity Model:

Lvl 5: Omzd busnss Svcs &

Lvl 4: Msud busnss SvcsBusiness Optimization/Event Stream Processingthrough Progress ESP Event Manager,Progress

Apama

Algorithmic Trading Platorm,and Progress RFID

Lvl 3: busnss Svc &

Lvl 1: ind Svcs

Business Process Management through Sonic

ESB Processes (Itineraries) and Sonic OrchestrationServer or sophisticated central process statemanagement

Lvl 2: accd Svcs &

Lvl 1: inl Svcs

Foundation SOA unctionality through Progress

SonicMQ

, Sonic ESB, Sonic XML Server, SonicDatabase Service, and Sonic Workbench


27/27

prOGreSS SOftware

Progress Sotware Corporation (NASDAQ: PRGS) is a global sotware company that enables enterprises to be operationally responsive to changing

conditions and customer interactions as they occur. Our goal is to enable our customers to capitalize on new opportunities, drive greater eciencies, and

reduce risk. Progress oers a comprehensive portolio o best-in-class inrastructure sotware spanning event-driven visibility and real-time response,

open integration, data access and integration, and application development and managementall supporting on-premises and SaaS/cloud deployments.

Progress maximizes the benets o operational responsiveness while minimizing IT complexity and total cost o ownership.

wOrLDwiDe heaDqUarterS

Progress Sotware Corporation, 14 Oak Park, Bedord, MA 01730 USA

Tel: +1 781 280-4000 Fax: +1 781 280-4095 On the Web at: .ogss.com

For regional international oce locations and contact inormation, please reer to the Web page: .ogss.com/oldd

Progress and Business Making Progress are trademarks or registered t rademarks o Progress Sot ware Corporation or one o its aliates or subsidiaries in the U.S. and other countries. Any

other trademarks contained herein are the property o their respective owners. Specications subject to change without notice.

2007, 2009 Progress So tware Corporation and/or its subsidiaries or aliates. All rights reserved.

Rev. 11/09 | 6525-128897

New Soa Maturity Model

Documents

Transcript of New Soa Maturity Model