service oriented architecture search membership group meeting cleveland, ohio july 24, 2008 scott...

14
Service Oriented Architecture SEARCH Membership Group Meeting Cleveland, Ohio July 24, 2008 Scott Came Director of Systems and Technology SEARCH

Upload: theodore-farmer

Post on 18-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Service Oriented ArchitectureSEARCH Membership Group MeetingCleveland, OhioJuly 24, 2008

Scott CameDirector of Systems and Technology

SEARCH

Welcome

IntroductionsObjectivesBrief motivation for SOAOpen discussion: what does this mean for

SEARCH members?

What is Architecture?

An architecture is a framework that guides

the significant decisions involved in creating or enhancing something

that matters.

Information Sharing Decisions

Architecture should tell us:How do we describe/define exchanges

(requirements)?How do we format the information?How is information transported (securely,

reliably)? How do systems connect?What infrastructure do we share? What

does it do? What technologies?How do we find exchanges?Who does/owns/funds what?

< JIEM

< NIEM

Why SOA?

The short answer:

Business agility

Single, standards-based way of handling cross-exchange requirements

A scenario

Law Enforcement sends demographics/charge information to Prosecutor…and the repository…and the jailProsecutor makes bail recommendation to courtProsecutor files charges with courtAnd pretty soon…

Flavors of Agility

AdaptabilityRespond to business opportunities

ReusabilityEliminate large-scale “rip and replace”

AutonomyBalance agency and enterprise needs

InteroperabilityChange technologies, vendors

TransparencyModels drive integration logic; orchestration

rather than coding

Is Agility Important?

How much change do you expect?OpportunitiesNew PartnersLegislative MandatesFederal MandatesExecutivesManagersStaffVendorsTechnology changes

How much will it cost?

Cross-Exchange Requirements

Some classes of requirements will be common across exchangesSeek economies of scaleStandards, thenShared infrastructure

Requirements:

Transport

Authorization

Authentication

Non-repudiation

Integrity

Supportability

Notification

Reliability

Routing

Transformation

A scenario

Law Enforcement reports booking eventPlatform transforms information and routes to Prosecutor and jailProsecutor makes bail recommendationPlatform routes to CourtProsecutor files chargesPlatform routes to Court

A few pointers

SOA is something you do, not something you buyRequirements and business need first,

software acquisition secondArchitecture first, ESB/hub/broker second

SOA implementation is a continuumXML/NIEMWeb ServicesProper servicesBusiness Processes

Incremental Adoption of SOA

AgilityXML

Indu

stry S

tand

ards

Contro

lled

voca

b

Stand

ard

mes

sage

s

(IEPDs)

SOAP

WS-*

Loca

tion

Inde

pend

ence

(regis

try)

Repos

itorie

s

Separ

ation

of

Busine

ss lo

gic

(inte

rmed

iaries

)

Provis

ioning

Mod

els

(sha

red

serv

ices)

Event

-driv

en

arch

itectu

reShare

d

Mes

sage

Trans

port

Discussion

How is SOA relevant to you?Handouts…

Thank you

Scott CameDirector, Systems and Technology

[email protected]

916-212-5978