Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Came Presentation


Published on

  • Be the first to comment

  • Be the first to like this

Came Presentation

  1. 1. SOA: An Approach to Information Sharing BJA Regional Information Sharing Conference Minneapolis, Minnesota March 28, 2007 Scott Came Director of Systems and Technology SEARCH
  2. 2. Agenda <ul><li>By the end, you should know: </li></ul><ul><ul><li>What is SOA? </li></ul></ul><ul><ul><li>What is a reference architecture, and how does it help with SOA adoption? </li></ul></ul><ul><ul><li>What value does SOA bring to information sharing? </li></ul></ul><ul><ul><li>What resources are available to help you consider or adopt SOA? </li></ul></ul><ul><ul><li>What are some SOA success stories? </li></ul></ul>
  3. 3. What is SOA?
  4. 4. Lets start with “architecture”
  5. 5. Architectural Style <ul><li>An architectural style is a set of characteristics that distinguish an architecture </li></ul><ul><li>The characteristics are intended to produce certain effects in things designed according to the style </li></ul>
  6. 6. Architectural Styles: Integration Shared User Interface Shared Database File Transfer SOA
  7. 7. SOA is an architectural style <ul><li>SOA is an architectural style, not for houses, but for sharing information and functionality between systems </li></ul><ul><li>Like any architectural style, SOA has a set of distinguishing characteristics </li></ul><ul><li>There are many ways to build a functional house…the right one depends on what you find important </li></ul>
  8. 8. Distinguishing Characteristics <ul><li>Interactions between consumers and providers (of functionality, data) take place across a minimalist interface </li></ul><ul><li>Interface based on open (versus proprietary) standards </li></ul><ul><li>Interface defined in business event terms, not system or technology terms </li></ul><ul><li>Consumer can discover interface dynamically </li></ul>
  9. 9. What is SOA…really? <ul><li>A set of policies, standards, and guidelines that constitute the architectural style </li></ul><ul><li>A reference architecture can provide a starting point for these by standardizing terminology and then standardizing how concepts are implemented </li></ul>
  10. 10. The Global JRA <ul><li>The Global Infrastructure/Standards Working Group is defining a Justice Reference Architecture </li></ul><ul><li>The JRA: </li></ul><ul><ul><li>Establishes common terminology for discussing SOA </li></ul></ul><ul><ul><li>Evolves SOA concepts into reference standards/guidelines that you can use in establishing a specific SOA in your environment (rather than starting from scratch) </li></ul></ul>
  11. 11. Key JRA Deliverables <ul><li>The JRA itself (common terminology) </li></ul><ul><li>Service Interaction Profiles: Think “messaging standards” </li></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><li>Others </li></ul></ul><ul><li>Service Modeling Guidelines </li></ul><ul><li>Service Design Principles </li></ul><ul><li>Methodology for identifying services </li></ul><ul><li>Guidance on necessary investments to support services and interactions </li></ul><ul><li>Management/Policy guidelines </li></ul>
  12. 12. What SOA is Not <ul><li>The same as web services </li></ul><ul><li>Service buses and message brokers </li></ul><ul><li>An infrastructure investment strategy </li></ul><ul><li>The brainchild of any particular vendor </li></ul><ul><li>Radically new </li></ul>
  13. 13. Why SOA? <ul><li>What is the value? </li></ul><ul><li>How do I sell it? </li></ul><ul><li>Why is an architecture with these qualities a good thing? </li></ul><ul><li>What value will I get by adopting SOA as my integration / information sharing approach? </li></ul>
  14. 14. Agility <ul><li>Accessing capabilities through services, if done with care, should result in more agile integrated systems </li></ul><ul><li>Agility: the ability to adapt to changing business requirements and environmental context </li></ul>
  15. 15. Agility Makes a Difference <ul><li>Agility is the hallmark of successful modern enterprises </li></ul><ul><li>Citizens expect rapid response to changing requirements </li></ul><ul><li>In the public safety arena: </li></ul><ul><ul><li>Clever opponents </li></ul></ul><ul><ul><li>New partners and requirements </li></ul></ul><ul><ul><li>Policy initiatives </li></ul></ul>
  16. 16. How is SOA agile? <ul><li>Minimizing dependencies: loose coupling </li></ul><ul><li>Interoperability </li></ul><ul><li>When context changes, there is minimal impact on existing systems </li></ul><ul><li>What kinds of context changes can happen? </li></ul>
  17. 17. Summary <ul><li>SOA is a style of designing integration solutions to achieve technical and policy agility </li></ul><ul><li>SOA is not technology that you buy…it’s a way of thinking about positioning your technology capabilities for agile sharing </li></ul>
  18. 18. BJA/Partner Resources <ul><li>Global JRA: </li></ul><ul><li>Training: </li></ul><ul><ul><li>IJIS/SEARCH SOA Seminar available through GTTAC </li></ul></ul><ul><li>Technical Assistance available through BJA partners </li></ul>
  19. 19. Success Stories <ul><li>Wisconsin </li></ul><ul><li>Washington State </li></ul><ul><li>District of Columbia </li></ul><ul><li>New York City—Corrections and Probation </li></ul><ul><li>Los Angeles County </li></ul>
  20. 20. Thank You! <ul><li>Scott Came </li></ul><ul><li>Director, Systems and Technology </li></ul><ul><li>SEARCH </li></ul><ul><li>[email_address] </li></ul><ul><li>916-212-5978 </li></ul>