DC Case Study in Service Oriented Architecture

Kevin Bell and Brady Birdsong

Index of Slides : Text Only Version

  1. District of Columbia Case Study in Service-Oriented Architecture
  2. Agenda
  3. No Title
  4. Definition of SOA Theory
  5. Definition of SOA Theory (cont.)
  6. Potential for SOA in Human Services Less Theory, More Practice
  7. Potential for SOA in Human Services Intake Using SOA in an Urban County
  8. Potential for SOA in Human Services Intake Using SOA in a Rural Setting
  9. Potential for SOA in Human Services Placement Using SOA in a Suburban County
  10. Experience in the District of Columbia Services Implemented So Far
  11. No Title
  12. Magic Quadrant: Selecting Functionality to Implement as a Service
  13. No Title
  14. Case Study: FACES.NET
  15. Case Study: Address Validation
  16. No Title
  17. Case Study: Address Validation (cont.)
  18. Case Study: Address Validation (cont.)
  19. Case Study: Address Validation (cont.)
  20. Case Study: Address Validation (cont.)
  21. Case Study: Case Planning
  22. No Title
  23. Third-Party Tools: Global Person Search
  24. Third-Party Tools: Workflow
  25. Third-Party Tools: Spell-Checking
  26. No Title
  27. Selecting SOA Implementation From a Project Management Perspective
  28. Project Management Perspective
  29. Selecting SOA Implementation From a Technical Perspective
  30. Technical Perspective
  31. Selecting SOA Implementation From a Functional Perspective
  32. Functional Perspective
  33. No Title
  34. SOA Balance Sheet
  35. No Title
  36. Advice to Other States: What to Tackle First
  37. Fitting SOA Into the Bigger IT Picture
  38. Questions and Contact Information

Return to Format List