An Enterprise Architecture and Model-Driven approach to ...archive.opengroup.org/events/q208a/presentations/Jonathan Chard.pdf · Increase Business Agility – Respond to customer

An Enterprise Architecture and

Model-Driven approach to Service

Application Creation

Jon C

hard

Princip

al C

onsultant

a2

©Telelogic AB

Session 1 –

SOA overview

a3

©Telelogic AB

What is ‘Service Oriented Architecture’?

•A

rchitectu

re b

uilt

fro

m m

any indiv

idual serv

ices

•E

volu

tion o

f past arc

hitectu

res

•T

he o

pposite o

f a m

onolit

hic

applic

ation

•C

om

mon c

om

munic

ation p

latform

Th

ink a

bo

ut

a c

ity w

ith

man

y

inte

rwo

rkin

g p

ieces

…

a4

©Telelogic AB

SOA –

Market Trends

“The march of SOA into companies is unavoidable at this point. Adoption is

accelerating, and SOA is being baked into virtually every commercially available

enterprise application. However, SOA adoption is uneven, with some industries

and geographies leading and others clearly lagging.”

Sourc

e : Ian F

inle

y,

AM

R R

esearc

h 2

007

a5

©Telelogic AB

What is a Service?

•S

upplie

s a

busin

ess n

eed

•lo

osely

-couple

d to o

ther

serv

ices

•W

ell

defined s

erv

ice

contr

act

•A

uto

nom

ous

•A

bstr

act

•R

eusable

•S

elf-d

escribed a

nd

dis

covera

ble

con

tra

ct

Legacy

Asset

ad

ap

ter

(Greenfield)

Service

con

tra

ct

Legacy a

ssets

may b

e ‘S

OA

-enable

d’

with a

SO

A c

om

plia

nt w

rapper

a6

©Telelogic AB

Service Interactions

contractLegacy

Assetadapter

(Greenfield)

Servicecontract

Service Registry

con

tra

ct

Consumer contract

Ente

rprise S

erv

ice B

us

WSDL

WSDL

WSDL

UDDI

lookup

registration

registration

XML stream (SOAP)

a7

©Telelogic AB

What makes up the Architecture?

•T

he c

om

ple

te s

et of serv

ices a

nd their inte

rconnections

–(W

ith a

ll th

e s

upport

ing info

rmation)

•S

om

e c

om

mon issues

–W

hat

are

the in

terc

onnections (

depe

nde

ncie

s)?

–W

hat

will

the A

rchitectu

re lo

ok lik

e in t

he f

utu

re?

–H

ow

will

you c

ontr

ol cha

nges t

o it?

–H

ow

will

you f

ind a

part

icu

lar

serv

ice?

–H

ow

do p

eop

le g

et

to u

nders

tand t

he A

rchite

ctu

re?

⇒T

he A

rchitectu

re h

as to b

e m

ain

tain

ed a

t an a

bstr

act le

vel

–S

imply

havin

g a

bunch o

f W

eb S

erv

ices w

hic

h c

all

each o

ther

isn’t

an A

rchitectu

re

a8

©Telelogic AB

Why SOA?

•In

cre

ase B

usin

ess A

gili

ty

–R

espo

nd t

o c

usto

mer

needs

–M

ore

fle

xib

le I

T (

plu

g a

nd p

lay)

–B

ring p

roducts

/serv

ices t

o m

ark

et

quic

ker

–Flexibility + Efficiency = Innovation

•R

educe C

osts

–M

anag

e o

ut

overlap

pin

g o

r re

dund

ant

syste

ms

–E

asily

scale

ea

ch a

pplic

atio

n f

or

max e

ffic

ien

cy

•R

educe R

isk

–B

ett

er

Unders

tand I

T C

apabili

ty

–A

ssess im

pact

on t

he b

usin

ess

–D

eliv

er

requ

ire

d c

apab

ility

•It’s

a BIG

com

petitive a

dvanta

ge

–Y

our

users

an

d c

usto

mers

can

bett

er

meet

their

requir

em

ents

and d

ea

dlin

es

a9

©Telelogic AB

Some Common Pitfalls

•B

uild

ing S

OA

lik

e a

tra

ditio

nal dis

trib

ute

d a

pplic

ation

•In

abili

ty to c

om

munic

ate

betw

een team

s

•N

ot cre

ating a

tra

nsitio

n p

lan

•N

ot sta

ndard

isin

g a

cro

ss y

our

pro

jects

•N

ot definin

g the c

ontr

acts

first

•P

oor

analy

sis

and d

esig

n

a10

©Telelogic AB

Avoiding the pitfalls of SOA –

a lifecycle

approach

•E

ffective S

OA

is n

ot ju

st about gettin

g the

arc

hitectu

re r

ight

•E

ffective S

OA

is n

ot ju

st about a c

orr

ect te

chnic

al

imple

menta

tion

•E

ffective S

OA

requires a

n inte

gra

ted, yet flexib

le

appro

ach, in

clu

din

g:

–A

ccom

modatin

g n

ew

an

d e

volv

ing b

usin

ess n

eeds

–S

upport

ing e

ffic

iency t

hro

ugh e

ffective r

euse a

nd

optim

isation

–S

upport

ing

an

d e

nab

ling e

ffective t

echnolo

gy

str

ate

gie

s

a11

©Telelogic AB

A Layered Enterprise SOA Approach

Busin

ess M

otivation

Busin

ess P

rocess L

ayer

Serv

ices L

aye

r

Applic

ation L

ayer

Technolo

gy L

ayerBusiness goals

Business processes

BPMN

Tau

Java

C#

Services

UMLBusiness requirements

Technology platform

sCode

Operating systems

Application platform

s

Applications

Service buses

Service repositories

Legacy systems

WSDL

Schemas

Service registries

Databases

IT

.NET

J2EE

Process execution

Storyboarding

Service adapters

UML

Orchestration

Choreography

Governance

Business roadmap

Service roadmap

Application roadmap

Technology roadmap

BPEL

Business organization

User requirements

a12

©Telelogic AB

Enterprise Architecture and M

odel-Driven

SOA

Motivation

Busin

ess

Serv

ice

Applic

ation

Technolo

gy

Java

C#

.NET

J2EE

a13

©Telelogic AB

Benefits of Enterprise Architecture-Driven

SOA

•A

sin

gle

repository

of busin

ess S

OA

info

rmation

–C

aptu

re b

usin

ess s

trate

gy,

pro

cesses a

nd in

form

ation

–M

odel th

e s

yste

ms a

nd a

pplic

ations t

he

y h

ave t

o s

upport

the

busin

ess n

ee

ds

–C

aptu

re t

he r

ela

tionsh

ips b

etw

een a

rchitectu

ral ele

ments

•A

basis

for

com

munic

ation a

naly

sis

and u

nders

tandin

g

–M

easure

and c

om

pare

the v

alu

e o

f diffe

rent

initia

tives

–R

eport

on t

he s

erv

ice la

ndscape,

revea

ling g

aps a

nd o

verl

aps

–T

ime-b

ased r

eport

ing f

or

‘wh

at-

if?’and ‘w

he

n?’an

aly

sis

–E

valu

ate

the a

lignm

ent

of

serv

ices b

efo

re a

nd a

fter

deplo

ym

ent.

a14

©Telelogic AB

Benefits of Model-Driven SOA

•S

atisfy

busin

ess r

equirem

ents

–D

esig

n a

pp

lica

tions t

hat

directly t

ie t

o t

he b

usin

ess p

lan

•T

am

e c

om

ple

xity

–V

isually

ana

lyse,

desig

n a

nd a

ssem

ble

serv

ice a

rchitectu

res

–P

rovid

e a

sin

gle

SO

A t

echnic

al serv

ice r

epo

sitory

•C

olla

bora

tion a

nd u

nders

tandin

g

–V

isualiz

e,

impo

rt a

nd g

enera

te W

SD

L a

nd X

SD

•A

dapt le

gacy s

erv

ices

–A

pply

rou

nd-t

rip e

ngin

eeri

ng

•E

nsure

corr

ectn

ess

–S

imula

te a

nd t

est

your

logic

before

an

y c

od

e is w

ritt

en

!!

•E

nable

reuse

–K

eep d

esig

ns a

bstr

act

to e

xte

nd t

heir life

a15

©Telelogic AB

Enterprise W

orkflow

Develop

enterprise

architecture

Analyze &

optimize business

strategies

Deploy & m

aintain

Design services &

applications

Business

requirements

User

requirements

System

requirements

Trace and analyze relationships

Middleware

JC1

Slide 15

JC1

Add the m

iddleware stuff to this diagram

Jon Chard, 23/04/2008

a16

©Telelogic AB

Implementation Considerations -1

Imple

menting a

SO

A w

ork

flow

and tools

et is

a s

trate

gic

undert

akin

g w

hic

h w

ill u

nderp

in the b

usin

ess o

ver

multip

le

pro

jects

and tim

e fra

mes

•B

oth

busin

ess a

rchitectu

re a

nd technic

al serv

ice in

form

ation

must be a

vaila

ble

acro

ss p

roje

cts

and a

cro

ss the b

usin

ess

⇒Im

ple

menta

tio

n a

ppro

ach s

hould

pro

vid

e r

epositori

es f

or

(1)

ente

rprise a

rch

itectu

re a

nd (

2)

technic

al serv

ices

•N

ota

tions w

illvary

acro

ss the S

OA

lifecycle

:

–B

usin

ess:

BP

MN

, ID

EF

, B

PE

L,

etc

.

–T

echnic

al: U

ML,

WS

DL,

Code,

etc

.

⇒T

ool support

for

require

d n

ota

tions a

nd d

efin

able

map

pin

gs

betw

ee

n t

he la

yers

is e

ssential

a17

©Telelogic AB

Different Approaches

Model-centric

Code-centric

Business Processes

Requirements

Architecture/Service Model (Platform

Independent)

Application M

odel (Platform

Specific)

Application Code

Runtime

development

integration & reuse

a18

©Telelogic AB

Implementation Considerations -2

•D

iffe

rent w

ork

flow

appro

aches r

equire b

i-directiona

l m

odelin

g

inte

rfaces

•T

wo info

rmation flo

ws thro

ugh the lifecycle

:

–M

odel e

lem

ents

–T

raceabili

ty –

end t

o e

nd lin

ka

ge o

f m

odels

and r

equ

irem

ents

•T

echnolo

gy independence o

f solu

tions:

–S

OA

is s

trate

gic

–te

chnolo

gie

s c

hange

–T

echnolo

gy in

depen

dence is v

ital fo

r eff

ective r

euse

–M

iddle

ware

is t

he inte

rface

a19

©Telelogic AB

Interim Conclusions

•S

OA

has the p

ote

ntial to

deliv

er

busin

ess a

gili

ty w

ith r

educed

costs

and r

isk

–If

SO

A p

roje

cts

are

hand

led c

orr

ectly

•E

ffective S

OA

pro

jects

must addre

ss the w

hole

landscape fro

m

busin

ess m

otivation to technic

al deliv

ery

–E

nte

rprise A

rchitectu

re c

an d

eliv

er

benefits

in p

lan

nin

g a

nd

alig

nin

g S

OA

activitie

s t

o t

he b

usin

ess

–M

odel D

riven D

evelo

pm

ent

can d

eliv

er

be

nefits

in c

olla

bora

tion,

corr

ectn

ess,

co

nsis

tency a

nd r

euse in t

he t

echnic

al

imple

menta

tio

n p

hase

•C

om

bin

ing E

nte

rprise A

rchitectu

re a

nd M

odel D

riven

Develo

pm

ent w

ith fle

xib

le w

ork

flow

support

is the k

ey to

deliv

ering e

ffective S

OA

Thank Y

ou!

Questio

ns?

An Enterprise Architecture and

Model-Driven approach to Service

Application Creation

Jon C

hard

Princip

al C

onsultant

a22

©Telelogic AB

Session 2

A practical Enterprise Architecture and Model-

Driven SOA W

orkflow

a23

©Telelogic AB

Enterprise W

orkflow

Develop

enterprise

architecture

Analyze &

optimize business

strategies

Deploy & m

aintain

Design services &

applications

Business

requirements

User

requirements

System

requirements

Trace and analyze relationships

Middleware

JC4

Slide 23

JC4

Add the m

iddleware stuff to this diagram

Jon Chard, 23/04/2008

a24

©Telelogic AB

Example tool support

Develop enterprise

architecture

Analyze & optimize

business strategies

Deploy & m

aintain

Design services &

applications

Business

requirements

User

requirements

System

requirements

Trace and analyze relationships

System

Architect

Tau

DOORS

Common Repository

a25

©Telelogic AB

Netw

ork

Concept D

iagra

m

Applic

ation A

rchitectu

re

•M

odel th

e k

ey d

om

ain

s a

nd their r

ela

tionship

s:

–B

usin

ess,

Str

ate

gy,

Ap

plic

atio

ns,

Infr

astr

uctu

re,

Data

•R

ela

te to the o

vera

ll serv

ice infr

astr

uctu

re a

nd its

ele

ments

Busin

ess P

rocess D

iagra

m

Ente

rprise D

irection D

iagra

m

Serv

ice C

olla

bora

tion D

iagra

m

Modeling the Enterprise Architecture

en

terp

rise b

luep

rin

t…g

ain

un

ders

tan

din

g

a26

©Telelogic AB

An example EA for SOA workflow

Iden

tify

& m

ode

l bu

sin

ess p

roce

sse

s

Bu

ild A

pp

lica

tion

po

rtfo

lio

Bu

ild s

erv

ice

mod

el

Ma

p s

erv

ice

s t

o

BP

MN

pro

ce

sse

sM

ap

se

rvic

es t

o

ap

plic

ation

s

a27

©Telelogic AB

Service collaboration diagram

a28

©Telelogic AB

SOA Deployment Analysis

op

tim

ize im

ple

men

tati

on

en

vir

on

men

t, p

rep

are

fo

r ch

an

ge

•P

rovid

e t

he e

nte

rprise v

iew

of

the

SO

A p

roje

ct

–S

how

ho

w b

usin

ess o

pera

tes t

oda

y

–E

xplo

re h

ow

ne

w s

erv

ices a

re g

oin

g

to fit into

the

org

aniz

ation

–P

erf

orm

im

pact

analy

sis

on r

em

oval

or

change o

f e

xis

ting s

erv

ices

•B

usin

ess a

nd I

T c

an s

ee t

he

serv

ice p

lan f

or

an

y

imple

menta

tio

n

–Id

entify

candid

ate

s for

reuse

–P

erf

orm

analy

sis

to d

ete

rmin

e

chara

cte

ristics o

f desired futu

re

sta

te a

rchitectu

res

a29

©Telelogic AB

SOA Deployment Analysis

vis

uali

ze t

he S

OA

en

vir

on

men

t, m

an

ag

e c

han

ge

•C

aptu

re a

nd v

isualiz

e s

erv

ice

hie

rarc

hie

s

•A

uto

matically

genera

te s

erv

ice

roadm

ap r

eport

s

•M

anag

e d

eliv

ery

•A

ssess t

he im

pact

of

changes

•S

pot

gaps a

nd d

uplic

atio

n in

pla

ns

a30

©Telelogic AB

Business Analysis & Planning

bu

sin

ess a

gilit

y …

red

uce r

isk

•M

ap b

usin

ess o

bje

ctives a

nd g

oals

–esta

blis

h s

cope

•U

nders

tand t

he e

xis

ting b

usin

ess

in t

erm

s o

f:

–people

–pro

cesses

–applic

ations

–in

form

ation

–serv

ices

•P

lan c

ha

nges in lin

e w

ith

obje

ctives a

nd g

oals

–ro

adm

aps

•D

evelo

p a

nd m

ain

tain

busin

ess

serv

ice a

rch

ite

ctu

re

Business Services

Design

services

Implement

services

Deployment Platform

Integrate

services

Test

services

Enterprise Architecture

Scope

business

Analyze

organization

Identify

services

Plan

roadmaps

guidance

accountability

a31

©Telelogic AB

Linking Enterprise Architecture and

Technical Development

Busin

ess P

rocesses

UM

L U

se C

ase A

naly

sis

UM

L technic

al serv

ice

imple

menta

tion

Modelin

gin

form

ation flo

w

Tra

ceabili

ty

a32

©Telelogic AB

EA to UML M

odelingFlow

a33

©Telelogic ABLinking the EA and M

DD environments

EA

repository

UM

L2 e

nvironm

ent

EA

environm

ent

a34

©Telelogic AB

Project Architecture Analysis and Design

imp

rove a

ccu

racy …

incre

as

e q

uality

•S

tart

fro

m the b

usin

ess n

eeds fro

m S

yste

m A

rchitect

–C

aptu

re u

nders

tandin

g o

f th

e o

vera

ll p

urp

ose f

or

develo

pm

ent

•V

isualiz

e the s

ignific

ant part

icip

ants

and w

hat th

ey n

eed

•D

ete

rmin

e w

hat is

involv

ed in m

eeting their n

eeds

•M

ain

tain

full

traceabili

ty

•S

imula

te a

nd test as a

whole

a35

©Telelogic AB

Distributed Application Assembly

imp

rove f

un

cti

on

ality

... q

uality

…re

du

ce c

om

ple

xit

y

•S

plit

the A

rchitectu

re u

p into

manageable

com

ponents

–T

reat

each c

om

pone

nt

as a

sta

ndalo

ne m

odel

•S

imula

te a

nd test as a

set of connecte

d s

erv

ices

•C

heck a

nd T

est th

at each c

om

ponent is

corr

ect

•E

xtr

act docum

ents

and r

eport

s fro

m the m

odel

–C

an b

e u

pdate

d a

uto

matica

lly b

y e

xtr

actin

g t

he info

rmation a

gain

•A

naly

ze the m

odel to

dete

rmin

e o

vera

ll im

pact

a36

©Telelogic AB

Technical Service Development

deli

ver

fun

cti

on

ality

•P

erf

orm

gap a

naly

sis

to

dete

rmin

e m

issin

g s

erv

ices

–B

uy o

r m

ake?

•E

xtr

act desig

n d

ata

to d

efine

serv

ice’s

arc

hitectu

re

•A

dd p

latform

deta

ils for

deplo

ym

ent

•R

ound-t

rip e

ngin

eer

deplo

yable

softw

are

–In

Java,

C# o

r C

++

a37

©Telelogic AB

Encouraging Re-use

bu

sin

ess a

gilit

y …

fast

tim

e t

o v

alu

e …

scale

as n

eed

ed

•R

euse b

rings m

ajo

r advanta

ges

–R

educes e

ffort

–R

educes r

isk –

zero

im

pact

on q

ualit

y

–S

peeds d

eliv

ery

•R

e-u

se e

xis

ting info

rmation in the IT

landscape

–Im

port

exis

ting S

erv

ice d

efinitio

ns

–Im

port

oth

er

da

ta (

XM

L/X

MI/

CS

V/J

ava/C

#/C

++

/…)

•R

e-u

se w

ithin

the s

erv

ice A

rchitectu

re

–S

earc

h f

or

exis

ting s

erv

ices (

harv

esting)

–D

esig

n n

ew

se

rvic

es w

ith r

e-u

se in m

ind

a38

©Telelogic AB

Automating Service Reuse

1 -

Locate

Web S

erv

ice

2 –

Import

and v

isualiz

e in U

ML

3 -

Auto

-genera

te A

PI and c

lient

4 –

Auto

-genera

te e

xecuta

ble

and o

rchestr

ate

web-s

erv

ice

a39

©Telelogic AB

Collaboration

man

ag

e d

istr

ibu

ted

team

s…

ou

tso

urc

e c

on

tracto

rs

•D

ivid

e a

nd g

overn

larg

e p

roje

cts

–Logic

ally

se

para

te p

roje

ct

mo

dels

–D

evelo

p a

nd d

eliv

er

sp

ecific

ations o

r in

terf

ace

info

rmatio

n (

WS

DL a

nd/o

r X

SD

)

–P

ow

erf

ul com

pare

/merg

e

•S

peak the s

am

e language

–C

om

mon b

asis

for

specifyin

g a

nd e

nfo

rcin

g c

om

plia

nce

–G

ain

accepta

nce a

t each s

tag

e t

hro

ugh s

hare

d m

ode

ls

•K

eep team

s fully

accounta

ble

–T

raceabili

ty e

nsure

s a

ccura

te r

eport

ing

–P

rove d

esig

ns a

gain

st

the o

rigin

al re

qu

irem

ents

a40

©Telelogic AB

Round Trip Traceability -The Audit Trail

Red

uc

e R

isk …

Imp

rove/A

ch

ieve c

om

plian

ce

bu

sin

ess r

eq

uir

em

en

ts

user

req

uir

em

en

ts

syste

m r

eq

uir

em

en

ts

bu

sin

ess p

rocesses

serv

ice d

esig

n

a41

©Telelogic AB

Summary

•C

orr

ectly im

ple

mente

d, S

OA

pro

vid

es the p

ote

ntial to

im

pro

ve

agili

ty w

hils

t lo

wering r

isk / c

osts

•A

n E

A a

nd M

DD

SO

A a

ppro

ach a

ssure

s that th

e w

hole

lifecycle

is c

overe

d, ensuring that busin

ess r

equirem

ents

are

drivin

g the IT

landscape

•E

nte

rprise a

rchitectu

re b

rings m

any b

enefits

to S

OA

pla

nnin

g:

–A

lignm

ent

of

technic

al deve

lopm

ent

with b

usin

ess n

eeds

–M

anag

em

ent

of

the e

volv

ing landsca

pe

•M

odel D

riven D

evelo

pm

ent brings m

any b

enefits

to the

technic

al im

ple

menta

tion o

f S

OA

:

–P

latf

orm

inde

pende

nce o

f de

sig

n a

ssets

im

pro

ves a

gili

ty

–E

arl

y,

mo

del-

based t

esting r

educes r

isk

–M

odel-

base

d s

erv

ices r

ep

ository

and s

erv

ice

s d

iscovery

im

pro

ves

reuse

Thank Y

ou!

Questio

ns?

Com

e a

nd s

ee t

he d

em

oat

the

Tele

logic

sta

nd!