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

2. Welcome Introductions Objectives  Brief motivation for SOA  Open discussion: what does this mean for SEARCH members?

3. What is Architecture? An architecture is a framework that guides the significant decisions involved in creating or enhancing something that matters.

4. 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

5. Why SOA? The short answer:  Business agility  Single, standards-based way of handling cross-exchange requirements

6. A scenario Law Enforcement sends demographics/charge information to Prosecutor …and the repository …and the jail Prosecutor makes bail recommendation to court Prosecutor files charges with court And pretty soon…

7. Flavors of Agility Adaptability  Respond to business opportunities Reusability  Eliminate large-scale “rip and replace” Autonomy  Balance agency and enterprise needs Interoperability  Change technologies, vendors Transparency  Models drive integration logic; orchestration rather than coding

8. Is Agility Important? How much change do you expect?  Opportunities  New Partners  Legislative Mandates  Federal Mandates  Executives  Managers  Staff  Vendors  Technology changes How much will it cost?

9. Cross-Exchange Requirements Some classes of requirements will be common across exchanges Seek economies of scale  Standards, then  Shared infrastructure Requirements: Transport Authorization Authentication Non-repudiation Integrity Supportability Notification Reliability Routing Transformation

10. A scenario Law Enforcement reports booking event Platform transforms information and routes to Prosecutor and jail Prosecutor makes bail recommendation Platform routes to Court Prosecutor files charges Platform routes to Court

11. A few pointers SOA is something you do, not something you buy  Requirements and business need first, software acquisition second  Architecture first, ESB/hub/broker second SOA implementation is a continuum  XML/NIEM  Web Services  Proper services  Business Processes

12. Incremental Adoption of SOA Agility XML Industry Standards Controlled vocab Standard messages (IEPDs) SOAP WS-* Location Independence (registry) Repositories Separation of Business logic (intermediaries) Provisioning Models (shared services) Event-driven architecture Shared Message Transport

13. Discussion How is SOA relevant to you? Handouts…

14. Thank you Scott Came Director, Systems and Technology SEARCH scott@search.org 916-212-5978