1. Real Examples SOA Governance in Use Today 2nd SOA for E-Government Conference Presenter: Chris Brown E-Mail: chbrown@mercury.comchbrown@mercury.com Date: October 31, 2006

2. 2 Some Systinet Customers

3. 3 What is SOA Governance About? VisibilityTrustControl Trigger Your organization begins its SOA Teams begin sharing services Teams depend on others’ services Challenge Make SOA part of your culture Make SOA predictable Make SOA adoption easy and safe Capabilities Understanding, Oversight Governance, Policy and Standards Compliance Rich lifecycle management, Impact Analysis, Change Management

4. 4 How are Customers Defining the Service Lifecycle?  Federal Government FDCE – Development, Development Piloting, Operational Piloting, Operations NCES – In Development, Release Candidate, Operational, Deprecated, Obsolete  Commercial Customers Development, Testing, QA, Production, Deprecated, Retired

5. 5 What are the Roles and Responsibilities in SOA Governance?  Developer/Material Provider Responsible for the development and integration of services available on the network  Testers Test services for functionality, but test the service against the SOA Policies and load testing to ensure the service can meet the proposed SLA  Architects Responsible for the overall architecture of the SOA by defining the SOA policies and services needed within the SOA  End Users/Warfighter End-Users engaged early in the development of services to provide feedback back to the developers prior to the service going into production

6. 6 What Policies are Being Enforced?  Technical Policies WS-Interoperability Basic Profile Namespace Rules Organization Best Practices such as all WSDLs must implement a getVersion operation  Metadata Policies Has the service been tagged with the proper DoD Security Classification Has an architecture guide been associated to the service  Business Polices Does the service have proper sign-off to be deployed in production Does the service conform to DoD IA Standards

7. 7 How does all this fit into a process? Provide metadata and relationships to service Self-check service against policies Allow end-users to utilize and publish feedback Request Promotion to next lifecycle stage Policies are validated Service promoted to next lifecycle stage

8. 8 Governance while in Operation  Managing the relationships between service consumers and providers Who are my consumers? What is my SLA to those consumers? Who do I affect if I change my service? Am I using a deprecated Service?

9. Q & A