Upcoming SlideShare
Loading in...5







Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Presentation Presentation Presentation Transcript

  • Demystifying SOA What’s in it for you Tom Clarke National Center for State Courts [email_address]
  • The Business Context
    • Many independent agencies and funding bodies
    • Many levels and branches of government
    • Widely different scales of operation
    • Wide variety of legacy hardware and software
    • Constantly changing requirements
  • Global Justice Information Sharing Initiative Advisory Committee(Global)
    • 22 of 31 groups state or local.
    • 4 Working Groups
      • Standards
      • Security
      • Privacy
      • Intelligence)
  • The Challenge: Information Sharing Across Agencies and Disciplines
    • The Vision:
    • “ Any member of the Justice Community can access the information they need to do their job, at the time they need it, in a form that is useful, regardless of the location of the data.”
    • A Framework for Justice Information Sharing: Service-Oriented Architecture (SOPA), The Global Infrastructure/Standards Working Group,
    • Dec. 9, 2004
  • Solution: Service Oriented Architecture (SOA)
    • Uses the open standards of the Internet.
    • Builds services one business process at a time.
    • Technology now reflects reality of government information sharing.
    • Dramatic management and policy implications.
  • SOA Attributes:
    • Focus is on linking system to system.
    • Uses STANDARDS for making the links.
    • Exploits Internet- based middleware.
    • Independent of hardware.
    • ( Barry’s Audio System Analogy )
  • Web Services Version of SOA Assumptions
    • Open Internet Protocols
    • Define content (GJXDM)
    • Define services
      • Content
      • Delivery mechanism
      • Business rules (security, privacy, ID’s)
    • Data comes from the Sources
      • Think of Internet searches
  • SOA Development
    • Requirements:
      • Open Standards
        • Content: data (GJXDM)
        • Delivery: messaging profiles
      • Common Business Rules
      • Registries
        • Requirements
        • Standards (official versions)
        • Instances (examples)
  • Meeting the Requirements
    • Standards Setting Bodies
      • Public: GJXDM/Global, NIEM
      • Private: W3C, OASIS, WS-I
    • Modeling and Testing
      • Wisconsin, NLETS, ARGIS, JNET, Colorado, NCSC, CAP, ICE
  • Who’s Doing What?
    • Security WG (security & ID)
    • Privacy WG (privacy, public access)
    • Standards WG (services, registries, business rules, governance)
    • GTTAC (message profiles)
  • Management & Policy Implications
    • Incremental Development
      • System is an accumulation of individual services.
    • Management Involvement
      • Services are developed around business processes.
    • Legacy Systems
      • Legacy systems are leveraged.
  • Management & Policy (Con’t)
    • Investment Strategies
      • On-going investment
      • Fallacy of building analogy
    • Data Ownership
      • Data stays at home
      • Virtual warehouses
    • SOA itself a Work-in-Progress
      • Begin skill development
  • Major Business Implications
    • Reuse of services (messages) and micro-services (data components) to eliminate redundant development
    • Governance of services and data components by multiple groups by appropriateness
  • References
    • Office of Justice Programs
    • Douglas K. Barry
      • Web Services and Services Oriented Architectures: A Savvy Manager’s Guide
    • [email_address]