SOA: An Approach to Information Sharing

BJA Regional Information Sharing ConferenceJacksonville, FloridaJune 5, 2007

Scott CameDirector of Systems and Technology

SEARCH

Agenda

By the end, you should know:What is SOA?What is a reference architecture, and how

does it help with SOA adoption?What value does SOA bring to information

sharing?What resources are available to help you

consider or adopt SOA?What are some SOA success stories?

What is SOA?

Lets start with “architecture”

Architectural Style

An architectural style is a set of characteristics that distinguish an architectureThe characteristics are intended to produce certain effects in things designed according to the style

Architectural Styles: Integration

Partner A Partner BPartner A Partner B

Partner A Partner BPartner A Partner B

Shared UserInterface

SharedDatabase

FileTransfer

SOA

SOA is an architectural style

SOA is an architectural style, not for houses, but for sharing information and functionality between systemsLike any architectural style, SOA has a set of distinguishing characteristicsThere are many ways to build a functional house…the right one depends on what you find important

Distinguishing Characteristics

Interactions between consumers and providers (of functionality, data) take place across a minimalist interfaceInterface based on open (versus proprietary) standardsInterface defined in business event terms, not system or technology termsConsumer can discover interface dynamically

What is SOA…really?

A set of policies, standards, and guidelines that constitute the architectural styleA reference architecture can provide a starting point for these by standardizing terminology and then standardizing how concepts are implemented

The Global JRA

The Global Infrastructure/Standards Working Group is defining a Justice Reference ArchitectureThe JRA:Establishes common terminology for

discussing SOAEvolves SOA concepts into reference

standards/guidelines that you can use in establishing a specific SOA in your environment (rather than starting from scratch)

Key JRA Deliverables

The JRA itself (common terminology)Service Interaction Profiles: Think “messaging standards”Web ServicesOthers

Service Modeling GuidelinesService Design PrinciplesMethodology for identifying servicesGuidance on necessary investments to support services and interactionsManagement/Policy guidelines

What SOA is Not

The same as web servicesService buses and message brokersAn infrastructure investment strategyThe brainchild of any particular vendorRadically new

Why SOA?

What is the value?How do I sell it?Why is an architecture with these qualities a good thing?What value will I get by adopting SOA as my integration / information sharing approach?

Agility

Accessing capabilities through services, if done with care, should result in more agile integrated systemsAgility: the ability to adapt to changing business requirements and environmental context

Agility Makes a Difference

Agility is the hallmark of successful modern enterprisesCitizens expect rapid response to changing requirementsIn the public safety arena:Clever opponentsNew partners and requirementsPolicy initiatives

How is SOA agile?

Minimizing dependencies: loose couplingInteroperabilityWhen context changes, there is minimal impact on existing systemsWhat kinds of context changes can happen?

Summary

SOA is a style of designing integration solutions to achieve technical and policy agilitySOA is not technology that you buy…it’s a way of thinking about positioning your technology capabilities for agile sharing

BJA/Partner Resources

Global JRA: http://it.ojp.gov/topic.jsp?topic_id=242Training: IJIS/SEARCH SOA Seminar available

through GTTACTechnical Assistance available through BJA partners

Success Stories

WisconsinWashington StateDistrict of ColumbiaNew York City—Corrections and ProbationLos Angeles CountyMaine

Thank You!

Scott CameDirector, Systems and Technology

SEARCHscott@search.org

916-212-5978