SOA is dood.Leve SOA!

Marc GoversSogeti Nederland B.V.

Marc.govers@sogeti.nl

16 december 2010

Agenda

• Wat is het?• Wanneer wel/niet?• Wie doet het?• Hoe aan te vliegen?• Welke succesfactoren?

Agenda

• Wat is het?• Wanneer wel/niet?• Wie doet het?• Hoe aan te vliegen?• Welke succesfactoren?

SOA zorgt voor veel ophef….

Integration

Services

e*GateTM

Web App WCC / WPCLegacy

Core Bank

Risk & Financials

3rd Party

Web Adapter

WCCAdapter

LegacyAdapter

Adapter Comm.Adapter

Web Adapter

WCCAdapter

WCCAdapter

AdapterAdapterLegacyAdapter

WCCAdapter

LegacyAdapter

WCCAdapter

AdapterAdapter Comm.AdapterComm.Adapter

AdapterAdapter

Retrieve Customer

Detail Review Rating

Prepare Customer

Offer

Enterprise Service Bus

Business Process Management

Business Processes

IT Domain

Het lijkt zo simpel….

Bron: IBM

….maar een lawine aan consequenties

Service Oriented Architectuur

+ Andere manier van ‘business’ doen

Grenzen vervagen, herbezinning op kern, …

+ processen er omheen

Architectuurproces, governance, innovatie, …

+ Relatie Business-IT

BPEL, BPM, Business-services, architectuur, …

+ Infrastructuur

ESB, On demand, virtualisatie,….

SOA = Systeeminrichting

Services

+ Impact op: testen, security, beheer, project-aanpak, …

Eigenaar Gebruiker

Levert service

Betaalt service

Ontwikkelaar

Specificatiesservice

Gebouwdeservice

Governance

Spelregels voor ontwikkelenen afrekenen van services

Informatie over services(ontwikkeling, gebruik etc.)

Belangrijke rollen in SOA context

Ontwikkelaar

Specificatiessamengestelde

applicatie

GebouwdeapplicatieBusiness

IT

SOA gedefinieerd

•Service Oriented Architectuur is een architectuurstijl waarmee de enterprise wendbaarheid verbeterd kan worden door het gebruik van business services

Agenda

• Wat is het?• Wanneer wel/niet?• Wie doet het?• Hoe aan te vliegen?• Welke succesfactoren?

Wanneer services?

Wijzigingen in:• Producten en diensten• Regelgeving• Kanalen• Acquisities• Hosting• Business to business• Combinaties hiervan

Wanneer geen services?

• Statische producten en diensten• Statische regelgeving• Geen plannen voor acquisities• Geen sprake van hosting• Geen sprake van kanalen die komen en

gaan• Geen sprake van wisselende partners

waarmee informatie wordt uitgewisseld• Oplossen fragmentatie-, legacy- of

siloproblemen

Wanneer SOA?

WEL

• Veel veranderingen• Heterogene IT• Verschillende

distributiekanalen of bedieningsconcepten

• Afgedwongen door ketenpartners

• Integratieproblemen• Best-of-breed beleid

NIET

• Weinig veranderingen

• Homogene IT• Wanneer real-time

performance van cruciaal belang is

• Best-of-suite beleid

Agenda

• Wat is het?• Wanneer wel/niet?• Wie doet het?• Hoe aan te vliegen?• Welke succesfactoren?

ING

Gebruikers SOA

• Verzekeraars kanalen en labels• Air France KLM kanalen• IND wet- en regelgeving• CFI wet- en regelgeving

Over het algemeen valt het tegen:•Ambities stroken niet met de benodigde capabilities•Implementatie wordt zwaar onderschat•Verwachtingen zijn te hoog (complexiteit stijgt!!!!)

Agenda

• Wat is het?• Wanneer wel/niet?• Wie doet het?• Hoe aan te vliegen?• Welke succesfactoren?

Wat is SOA?

die je implementeert door: • Services te identificeren,

ontwerpen, bouwen, testen, beheren en (uiteindelijk) weer uit te faseren

• De daarvoor benodigde infrastructuur te selecteren en implementeren

• Werkwijzes aan te passen en mensen op te leiden

SOA is een architectuurstijl …

Business projecten

Readiness projecten

Generieke IT/SOA

Business Project

Business Project

Business ProjectBusiness Project

SOARoadmap

SOA Implementatie Tijdlijn

Business doelen,Knelpunten,

Kansen,Entry Points

Strategie Scan Plan Introductie Expansie Operatie

Processen

Mensen

SOAMaturity

SOABusinessVisie

TechnologieWaa

r sta

at u

nu?

Wat

wilt

u b

erei

ken?

Wel

ke s

tapp

en m

oet u

nem

en e

n w

anne

er?

Business Project

Business Project

Readiness Project

Readiness Project

Readiness Project

Readiness Project

EntryPoint

Project

Business strategie,

Lange termijn doelen

Huidigesituatie

SOA Implementatie Aanpak

Typische toepassingen voor SOA• Klantinformatie• Basisregisters• Berichtenverkeer met

ketenpartners• Veel voorkomende checks

Voorbeelden van readiness projecten

• Beschrijven rollen en verantwoordelijkheden

• Inrichten portfoliomanagement• Opstellen standaarden en richtlijnen• Selecteren en implementeren van

een serviceregister• Aanpassen van de projectmethode• Opleiden van businessanalisten

Voorbeelden business projecten• Verbeteren van management

informatie• Productiviteit

call center-medewerkers verhogen• Doorlooptijd orderverwerking

verkorten

Agenda

• Wat is het?• Wie doet het?• Wanneer wel/niet?• Hoe aan te vliegen?• Welke succesfactoren?

Succesfactoren SOA

• Start vanuit organisatiedoelen• Houd rekening met toename complexiteit• Richt het werken onder architectuur en

governance in• Financier infrastructuur niet vanuit

businessprojecten• Denk vroegtijdig na over de consequenties

voor beheer• Houd rekening met culturele en

veranderkundige aspecten• Ben in staat om de waarde aan te tonen

Ergo..

Het implementeren van SOA is een kwestie van:

• Kiezen van de juiste business projecten én readiness projecten

• Stellen van prioriteiten• Managen van verwachtingen• Geloof, geduld en discipline

10 Great things to say to get fired

1. Let’s not tell the business2. Trust me: SOA is small, SOA is easy 3. We don’t need process orientation4. We will build a tower of Babel5. Let’s ask our junior Enterprise Architect6. Let’s change the standards7. With SOA we will start aiming at a moving

target8. SOA? Just let a thousand flowers bloom9. Let’s do SO without the A10.We’ll migrate everything to SOA

Wil je meer weten?

PDF Boek aanvragen:WWW.DYA.INFO

…..en hoge verwachtingen

0 1 2 3 4 5 6 7 8 9 10

Creëren van flexibiliteit

Herbruikbaarheid

Reduceren van complexiteit

Kostenreductie

Integratie

Vervangen van oude systemen

Efficiency

Verbeteren afstemming business en IT

Nieuwe technologie

Operational excellence

Meer gebruik maken van IT

Nastreven industriestandaarden

Wegkomen uit monolieten (point-to-point)

Bijdrage aan winstontwikkeling

Bron: Onderzoek UvA en Sogeti

Voorbeeld

Orderintake

Order

CheckKrediet-waard.

CheckVoor-raad

BepaalVerkoop-voorw.

MaakOrder-

bevest. Klant Order-

bevestiging

Verkoopproces

Klantbeheer

UitvoerenKrediet-

waardigheids-toets

Voorraadbeheer

UitvoerenVoorraad-

toets

Info of klant

kredietw. is

Info of artikel in

voorraad is

Traditioneel

Orderintake

Order

CheckKrediet-waard.

CheckVoor-raad

BepaalVerkoop-voorw.

MaakOrder-

bevest. Klant Order-

bevestiging

Verkoopproces

Klantbeheerapplicatie

Voorraadbeheerapplicatie

Gebruikklantbeheer-

applicatie omkredietwaardigheid

te checken

Gebruikvoorraadbeheer-

applicatie om beschikbaarheid

voorraad te checken

Service georienteerd

Orderintake

Order

CheckKrediet-waard.

CheckVoor-raad

BepaalVerkoop-voorw.

MaakOrder-

bevest. Klant Order-

bevestiging

Verkoopproces

Klantbeheerapplicatie

Voorraadbeheerapplicatie

Info of klant

kredietw. is

Geef krediet-waardigheid klant

Info of artikel in

voorraad is

Geef vooraad artikel

Service georienteerd

Orderintake

Order

CheckKrediet-waard.

CheckVoor-raad

BepaalVerkoop-voorw.

MaakOrder-

bevest. Klant Order-

bevestiging

Verkoopproces

Info of klant

kredietw. is

Geef krediet-waardigheid klant

Info of artikel in

voorraad is

Geef vooraad artikel

Applicatiecomponent

Applicatiecomponent

SamengesteldeApplicatie

Wat is een goede service?

Een component die relatief stabiel blijft ondanks veranderingen in de organisatie of technologie

services

Veranderendetechnologie

Veranderendebusiness

processen

SOA Maturity Building Blocks

Process

Technology People

SOA

Hoe werkt het SOA Maturity Model?

• 20 key areas (aspecten)• Drie of vier niveaus van

volwassenheid per key area• Plotten van volwassenheid• Gebruiken om vervolgstappen te

bepalen

∆ Warning: full Powerpoint slides ahead

SOA Maturity Key AreasBuilding Block Nr Key AreaProcess 1 Commitment and motivation

2 Relationships with projects3 Roles and responsibility4 Development of architecture5 Use of architecture6 Architectural tools (methodology and software)7 Quality Management8 Service portfolio management9 Vision of architecture10 Alignment with business11 Budgeting and planning

Technology 12 Technology and standards13 Componentization and Reuse14 Business processes implementation in the Information system15 Information system (infrastructure and applications) flexibility 16 Information Security

People 17 SOA skills in IT18 SOA skills in Business19 SOA mindset & knowledge among IT People20 SOA mindset & knowledge among Business People

SOA Maturity Levels (1)Nr Key area Level A Level B Level C Level D1 Commitment

and motivationBudget and time available for SOA initiatives

SOA approach is sponsored by the management of the organization

SOA approach is integrated in the organization processes

 

2 Relationships with projects

Architecture to project communication

Architectural process takes projects feedback into account

Architects, business and IT jointly build the project architecture

Continuous dialog between architects, business & IT

3 Roles and responsibility

IT department in charge of architecture and process

IT and business collaborate in architectural process

Responsibility of process ownership is transversal

 

4 Development of architecture

Architecture undertaken in projects

Architecture as a transversal process

Architecture as a facilitation process

 

5 Use of architecture

Architecture used informatively

Architecture used to steer content

Architecture integrated into the organization

 

6 Architectural tools (methodology and software)

Non-coordinated initiatives

Tooling streamlining and integration policy; global architecture process defined

Tooling is comprehensive and integrated, global architecture process is formalized

 

SOA Maturity Levels (2)Nr Key area Level A Level B Level C Level D7 Quality

ManagementAfterwards non-formal validation

A retroactive assessment is done on the basis of standardized indicators

The IS architecture quality process is defined. Continuous quality management

The IS architecture quality process is integrated in the organization quality process

8 Service portfolio management

Life cycles of services follow those of applications delivering them

Service Level Agreements

Planned life cycle (including decommissioning)

Service usage funding (service market place)

9 Vision of architecture

Vision of “as is” architecture

Vision of short-term evolutions

Vision of long-term architecture

Continuous alignment of vision with business goals, short and long- term

10 Alignment Information Systems with business

Applications and services are designed to meet business goals (business driven)

Applications and services are tested for compatability with business goals

Architectural process supports the business

Architectural process facilitates business transformations

11 Budgeting and planning

Need to formally justify a direct ROI for each impacted SOA business project

SOA project specific Organization generic

Continuous optimization of the budgeting and planning process

SOA Maturity Levels (3)Nr Key area Level A Level B Level C Level D12 Technology and

standardsAd hoc technology chosen when needed

IT base referential defined and proven

Motivated strategy Anticipation of technological changes and new standards adoption

13 Componentization and Reuse

Non-coordinated reuse

Reuse is coordinated within IT (technical services)

Reuse is coordinated on the business level (business services)

Business and IT are componentized and reuse is a common practice

14 Business processes implementation in the Information System

Existing business services within silos

Transversal processes

Business Activity Monitoring (BAM)

Business & IT collaborates to build and deploy business processes

15 Information system (infrastructure and applications) flexibility

Silos based information systems containing service-based application and hardware running them

Some applications and infrastructure are shared among (hazy) silos due to rationalization

Urbanized, reconfigurable & process-oriented information system

Decoupled business – information systems virtualization

16 Information Security

Reactive Individual Collective Proactive

SOA Maturity Levels (4)Nr Key area Level A Level B Level C Level D17 SOA skills in IT Basic Moderate Experienced  18 SOA skills in

BusinessBasic Moderate Experienced

19 SOA mindset & knowledge among IT People

Sparse awareness

Organization level awareness

Common SOA mindset

 

20 SOA mindset & knowledge among Business People

Sparse awareness

Organization level awareness

Common SOA mindset

SOA Maturity MatrixBB Nr Key area 0 1 2 3 4 5 6 7 8 9 10 11 12 13Pro-cess

1 Commitment and motivation A B C2 Relationships with projects A B C D3 Roles and responsibility A B C4 Development of architecture A B C5 Use of architecture A B C6 Architectural tools (methodology and software) A B C

7 Quality Management A B C D8 Service portfolio management A B C D9 Vision of architecture A B C D10 Alignment with business A B C D11 Budgeting and planning A B C D

Tech-nology

12 Technology and standards A B C D13 Componentization and Reuse A B C D14 Business processes implementation in the

Information SystemA B C D

15 Information System (infrastructure and applications) flexibility

A B C D

16 Information Security A B C DPeople 17 SOA skills in IT A B C

18 SOA skills in Business A B C19 SOA mindset & knowledge among IT People A B C20 SOA mindset & knowledge among Bus. People A B C

SOA Maturity Matrix exampleBB Nr Key area 0 1 2 3 4 5 6 7 8 9 10 11 12 13Pro-cess

1 Commitment and motivation A B C2 Relationships with projects A B C D3 Roles and responsibility A B C4 Development of architecture A B C5 Use of architecture A B C6 Architectural tools (methodology and software) A B C

7 Quality Management A B C D8 Service portfolio management A B C D9 Vision of architecture A B C D10 Alignment with business A B C D11 Budgeting and planning A B C D

Tech-nology

12 Technology and standards A B C D13 Componentization and Reuse A B C D14 Business processes implementation in the

Information SystemA B C D

15 Information System (infrastructure and applications) flexibility

A B C D

16 Information Security A B C DPeople 17 SOA skills in IT A B C

18 SOA skills in Business A B C19 SOA mindset & knowledge among IT People A B C20 SOA mindset & knowledge among Bus. People A B C

Stages of SOA readinessStage SOA readiness Characteristics0 To execute a SOA pilot

projectNo awareness, no skills, no commitment, no standards, no guidelines, no best practices

3 To execute SOA-related projects within isolated parts of the enterprise

The basics are in place, however a lot need to be learned and can be improved. It is important to have a process in which learning experiences can be incorporated and in which standards, guidelines and best practices will be developed and improved.

6 To execute SOA-related projects enterprise-wide

The number of standards, guidelines and best practices is growing. Experience is built up and reused in the enterprise.

9 To execute all SOA-related projects enterprise-wide as well as a SOA-related business transformation project

There is quite a lot of experience in deploying SOA. Standards, guidelines and best practices are broadly available and deployed enterprise-wide.

13 For a continuous business transformation

Deploying SOA is completely embedded in the processes of the enterprise. Products and processes are continously optimized, triggered by internal and external drivers.