Your SlideShare is downloading. ×
0
Service Oriented Architecture SEARCH Membership Group Meeting Cleveland, Ohio July 24, 2008 Scott Came Director of Systems...
Welcome <ul><li>Introductions </li></ul><ul><li>Objectives </li></ul><ul><ul><li>Brief motivation for SOA </li></ul></ul><...
What is Architecture? An architecture is a framework that guides the significant decisions involved in creating or enhanci...
Information Sharing Decisions <ul><li>Architecture should tell us: </li></ul><ul><ul><li>How do we describe/define exchang...
Why SOA? <ul><li>The short answer: </li></ul><ul><ul><li>Business agility </li></ul></ul><ul><ul><li>Single, standards-bas...
A scenario <ul><li>Law Enforcement sends demographics/charge information to Prosecutor </li></ul><ul><li>…and the reposito...
Flavors of Agility <ul><li>Adaptability </li></ul><ul><ul><li>Respond to business opportunities </li></ul></ul><ul><li>Reu...
Is Agility Important? <ul><li>How much change do you expect? </li></ul><ul><ul><li>Opportunities </li></ul></ul><ul><ul><l...
Cross-Exchange Requirements <ul><li>Some classes of requirements will be common across exchanges </li></ul><ul><li>Seek ec...
A scenario <ul><li>Law Enforcement reports booking event </li></ul><ul><li>Platform transforms information and routes to P...
A few pointers <ul><li>SOA is something you do, not something you buy </li></ul><ul><ul><li>Requirements and business need...
Incremental Adoption of SOA Agility XML Industry Standards Controlled vocab Standard messages (IEPDs) SOAP WS-* Location I...
Discussion <ul><li>How is SOA relevant to you? </li></ul><ul><li>Handouts… </li></ul>
Thank you <ul><li>Scott Came </li></ul><ul><li>Director, Systems and Technology </li></ul><ul><li>SEARCH </li></ul><ul><li...
Upcoming SlideShare
Loading in...5
×

Service Oriented Architecture Briefing

181

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
181
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Write this down: An architecture is a framework that guides the significant decisions involved in creating or enhancing something that matters. Matters = important enough that you want to be thoughtful and controlled in your decision-making. Means that success or fulfillment depends on how it turns out. Generally, but not always, that means something that is (a) complex, (b) expensive and (c) hard to undo.
  • Substantial discussion at the end of this slide…what can cause the criss-crossing lines? Direct network connections Integration logic embedded in the sender or receiver Vendor dependencies (shared database, shared “broker” from the system vendor) Proprietary data formats Coupling to particular business processes in the sender Unique (exchange-specific) implementation of non-functionals And: what is the business cost of the hairball? Paralysis! You can never change anything without enormous expense. Which means you get stuck.
  • Substantial discussion at the end of this slide…what can cause the criss-crossing lines? Direct network connections Integration logic embedded in the sender or receiver Vendor dependencies (shared database, shared “broker” from the system vendor) Proprietary data formats Coupling to particular business processes in the sender Unique (exchange-specific) implementation of non-functionals And: what is the business cost of the hairball? Paralysis! You can never change anything without enormous expense. Which means you get stuck.
  • Transcript of "Service Oriented Architecture Briefing"

    1. 1. Service Oriented Architecture SEARCH Membership Group Meeting Cleveland, Ohio July 24, 2008 Scott Came Director of Systems and Technology SEARCH
    2. 2. Welcome <ul><li>Introductions </li></ul><ul><li>Objectives </li></ul><ul><ul><li>Brief motivation for SOA </li></ul></ul><ul><ul><li>Open discussion: what does this mean for SEARCH members? </li></ul></ul>
    3. 3. What is Architecture? An architecture is a framework that guides the significant decisions involved in creating or enhancing something that matters.
    4. 4. Information Sharing Decisions <ul><li>Architecture should tell us: </li></ul><ul><ul><li>How do we describe/define exchanges (requirements)? </li></ul></ul><ul><ul><li>How do we format the information? </li></ul></ul><ul><ul><li>How is information transported (securely, reliably)? How do systems connect? </li></ul></ul><ul><ul><li>What infrastructure do we share? What does it do? What technologies? </li></ul></ul><ul><ul><li>How do we find exchanges? </li></ul></ul><ul><ul><li>Who does/owns/funds what? </li></ul></ul>< JIEM < NIEM
    5. 5. Why SOA? <ul><li>The short answer: </li></ul><ul><ul><li>Business agility </li></ul></ul><ul><ul><li>Single, standards-based way of handling cross-exchange requirements </li></ul></ul>
    6. 6. A scenario <ul><li>Law Enforcement sends demographics/charge information to Prosecutor </li></ul><ul><li>…and the repository </li></ul><ul><li>…and the jail </li></ul><ul><li>Prosecutor makes bail recommendation to court </li></ul><ul><li>Prosecutor files charges with court </li></ul><ul><li>And pretty soon… </li></ul>
    7. 7. Flavors of Agility <ul><li>Adaptability </li></ul><ul><ul><li>Respond to business opportunities </li></ul></ul><ul><li>Reusability </li></ul><ul><ul><li>Eliminate large-scale “rip and replace” </li></ul></ul><ul><li>Autonomy </li></ul><ul><ul><li>Balance agency and enterprise needs </li></ul></ul><ul><li>Interoperability </li></ul><ul><ul><li>Change technologies, vendors </li></ul></ul><ul><li>Transparency </li></ul><ul><ul><li>Models drive integration logic; orchestration rather than coding </li></ul></ul>
    8. 8. Is Agility Important? <ul><li>How much change do you expect? </li></ul><ul><ul><li>Opportunities </li></ul></ul><ul><ul><li>New Partners </li></ul></ul><ul><ul><li>Legislative Mandates </li></ul></ul><ul><ul><li>Federal Mandates </li></ul></ul><ul><ul><li>Executives </li></ul></ul><ul><ul><li>Managers </li></ul></ul><ul><ul><li>Staff </li></ul></ul><ul><ul><li>Vendors </li></ul></ul><ul><ul><li>Technology changes </li></ul></ul><ul><li>How much will it cost? </li></ul>
    9. 9. Cross-Exchange Requirements <ul><li>Some classes of requirements will be common across exchanges </li></ul><ul><li>Seek economies of scale </li></ul><ul><ul><li>Standards, then </li></ul></ul><ul><ul><li>Shared infrastructure </li></ul></ul><ul><li>Requirements: </li></ul><ul><ul><ul><ul><li>Transport </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Authorization </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Authentication </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Non-repudiation </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Integrity </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Supportability </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Notification </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reliability </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Routing </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Transformation </li></ul></ul></ul></ul>
    10. 10. A scenario <ul><li>Law Enforcement reports booking event </li></ul><ul><li>Platform transforms information and routes to Prosecutor and jail </li></ul><ul><li>Prosecutor makes bail recommendation </li></ul><ul><li>Platform routes to Court </li></ul><ul><li>Prosecutor files charges </li></ul><ul><li>Platform routes to Court </li></ul>
    11. 11. A few pointers <ul><li>SOA is something you do, not something you buy </li></ul><ul><ul><li>Requirements and business need first, software acquisition second </li></ul></ul><ul><ul><li>Architecture first, ESB/hub/broker second </li></ul></ul><ul><li>SOA implementation is a continuum </li></ul><ul><ul><li>XML/NIEM </li></ul></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><li>Proper services </li></ul></ul><ul><ul><li>Business Processes </li></ul></ul>
    12. 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. 13. Discussion <ul><li>How is SOA relevant to you? </li></ul><ul><li>Handouts… </li></ul>
    14. 14. 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>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×