1. The Government And Service Oriented Architecture Presented by: Dan Pelman

2. What is a Service Oriented Architecture? Who should be concerned and is it valuable? Where to start and how do I get there? Are there any government success stories? How should SOA be used to leverage value into the future? A Short Review

3. What SOA is and is not  SOA is:  An approach or framework  A viable approach to reducing cost SOA is not: A technology A panacea Distributed Computing or Modular Programming SOA should be: A Journey not a Jump Flexible, Scalable and Accessible

4. Who in the Government should be interested in SOA?  Those that have to meet expanded business demands with lower budgets  Those that want to be prepared to leverage future technologies  Core Business Executives and Managers  Chief Information Officers and Chief Architects

5. When..Where..and How.. to Start  When?  Once Your Enterprise Architecture includes it as a mandate… why?  Where?  Data Web Services Note: this is a technology implementation and having or using web services does not mean you have a SOA  How?  Think Big, Start Small (Oliver Rist, InfoWorld, Nov 2007)  Consider provisioning using existing infrastructure.

6. A Case Study in Data Web Services NAS change at any layer affects higher layers

7. XML (GML) Data Web Service Used for Computer Aided Design 2D

8. Same Data Web Service used in Instrument Approach Procedure App

10. Data Web Service in CAD 3D

11. More Data Web Services in Use Today

12. How should working from a SOA now.. benefit us in the Future?

14. Questions?