Practical Guide to Federal SOA

1. Practical Guide to Federal SOA Version 1.0 • Introduction & Status Update • Draft Guidance Prepared by Dan Ellis (dellis@everware-cbdi.com)

2. PGFSOA - Purpose of the Endeavor • Many initiatives in Federal agencies to explore & adopt SOA • Inconsistent approaches & implementations • AIC Services & Governance Subcommittees were targeting multiple documents Background The Opportunity • Convergence of approaches & SOA vocabulary • Codify rationale, target, keys to implementation • Help illustrate roadmap alternatives based on current state, and sequential, practical steps that minimize risk and have tangible benefit

3. PGFSOA - Objectives Provide sound, practical guidance in support of agencies’ efforts to adopt SOA into their business, IT, and EA practices. Primary Objective Secondary Objectives • Collaborative effort by knowledgeable individuals within government and industry. • Initial review with a select focus group to refine document. • Broad-based distribution for open review and comment period. • Final release by CIO Council by end of 2007.

4. Executive Steering Committee Editorial Board Content & Revisions Governance Structure Darren Ash Roy Mabry Kshemendra Paul John Sullivan George Thomas AIC Subcommittee Sponsors, IAC Reorganized into four Authoring Teams aligned with document structure Coordination (Execution) Coordinator, Assistant, and Expert Advisors Coordination Authoring Roadmap to SOA (Bob Haycock) Co-Leads Tom Lucas, Raphael Malveaux SOA Target Architecture (George Thomas, Dave Mayo) Co-Leads Gary Berg-Cross, Craig Miller Keys to Implementation (Roy Mabry, Dan Ellis) Lead Chris Gunderson Rationale for SOA (Kshemendra Paul, Bob Haycock) Co-Leads Mel Greer, Ira Sachs Unifying Examples preferably within the US Federal Government

5. Department of Defense* Department of Justice Department of Transportation General Services Administration Internal Revenue Service Library of Congress US Patent and Trademark Office EPA Australian Government Information Management Office NASCIO Global Justice National Center for State Courts * Multiple representatives Argosy Omnimedia ASG BAH CGI Federal Dovèl Technologies EntArch Everware-CBDI Fujitsu Harris HP HPTi IBM Currently Over 50 Volunteers • INNOVIM • Lockheed Martin • MITRE • Mercury • Pearson-Blueprint • PPC • SAIC • SRA International • Thomas & Herbert • Telelogic • TowerStrides • Webmethods 31 team members Authored 1st Drafts

6. Core Ideas • Written for Chief Architects: • To inform conversations with CIOs and Program Execs • To influence architectural and investment planning • Reference established external bodies of knowledge • Focus on what is unique about the (Federal) government • Use Federal and private sector examples to anchor

7. PGFSOA High Level Outline • Exec Summary and Introduction • Articulate the rationale • Put forward a concrete target / vision • Service Oriented Infrastructure • Service Oriented Architecture • Service Oriented Enterprise • Keys for Implementation – limiting factors to be addressed • Provide a roadmap with concrete actions across SOI, SOA, and SOE

8. Definition of SOA "Let's start at the beginning. This is a football. These are the yard markers. I'm the coach. You are the players." • Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. • -- OASIS SOA Reference Model version 1.0 • A Service-oriented architecture is a software architecture that uses loosely coupledsoftware services to support the requirements of business processes and software users. Resources on a network in an SOA environment are made available as independent services that can be accessed without knowledge of their underlying platform implementation. • -- Wikipedia, Feb 28, 2007

9. PGFSOA Rationale Why SOA?

10. Rationale for SOA • This section discusses why the federal government should adopt SOA at all levels. • Sets the stage for all subsequent sections. Theme: SOA enables you to achieve your organizational mission objectives Objectives of the Rationale Section: Note: This section is preceded by an Introduction that introduces SOA.

11. Draft PGFSOA Rationale – FEA Goals • Improve government responsiveness • Simplify delivery of enhanced government services • Contribute to a more efficient government • Contribute to information sharing • Increased security, transparency, and resilience Federal SOA Objectives are extrapolated from FEA Goals

12. PGFSOA Rationale – SOA Objectives • Continuous innovative IT asset re-capitalization • Cross-domain/cross-agency trust, data access, and semantic interoperability • Leverage IT investments across federal agencies and share best practices • Enhance mission effectiveness Proposed Federal Government SOA Objectives are to achieve: Theme: SOA enables you to achieve your organizational mission objectives

13. PGFSOA Target What is the vision for SOA?

14. SO Target Architecture (Vision) • Provide a foundation for SOA terminology and its use within the Federal Government. • Present a vision for a federal SOA that can be applied at all levels of the Federal Government. • Demystify SOA. Theme: A service oriented framework for agility Objectives of the SO Target Architecture Section:

15. Vision: Federal Agencies Become More Agile • IT provides timely and effective support to the operational businesscase through services architected to interact in flexible ways to achieve strategic and tactical objectives and to respond to an ever changing set of requirements. • Agencies routinely organize into ad hoc partnerships that pool resources to develop and deploy the secure, inter-operable, services necessary to enable the operational requirements. • Both the above activities weave together into interdependent lines of business that have external customer facing and also support internal service centers. “…the vision is that Federal agencies become more agile from a management, operational and acquisition perspective, and with respect to both internal and external support requirements …

16. SO Target Architecture – Top Level View Agile Enterprise • Service Oriented Enterprise • Agreed behaviors and clear incentives for collaboration • Mutually leveraged investments • Enhanced mission outcomes • Service Oriented Architecture • Interoperability at build time based on open standards and composable adapters • Agile recapitalization • Centrally-managed registries and repositories • Service Oriented Infrastructure • Secure, scalable infrastructure as a service • Interoperability at run time • Service enabled network

17. PGFSOA Keys to Implementation Where should we focus?

18. SOA Keys to Implementation • Help federal Chief Architects understand where to focus their resources. • Present best practices. • Elaborate on SOA challenges unique to the federal government. Theme: These are the critical things to focus on. Objectives of the SOA Keys to Implementation Section:

19. Keys to Implementing the SOE • Treat SOA adoption as an organizational change initiative • Obtain Executive Support • Establish program plan for SOA and measure results • Establish SOA center of excellence to oversee adoption • Appropriately Fund the Change Initiative • Build community processes and collaborative platforms • Establish Federated Governance • Establish communities of interest with budget authority • Create services development, test, and evaluation (DT&E) laboratories

20. Keys to Implementing the SOE • Establish service funding and charging mechanisms • Service based SDLC with incremental development • Service based procurement • Advance institutional knowledge and capture best practices

21. Keys to Implementing the SOA • Use EA to align with business objectives • Introduce Services as a First-Order Concept in your EA • Establish a Service Based Target Architecture • Adopt model based architecture and pattern based design • Enable automatic compliance and alignment • Leverage legacy assets to enable evolutionary progress

22. Keys to Implementing the SOI • Enterprise security, scalability, and interoperability • Establish discovery and trust mechanisms • Repositories/Registries • Adaptive and collaborative testing and certification

23. PGFSOA Roadmap How does all this fit together? How do I get there?

24. SOA Roadmap • Provide a framework for assessing an organizations SOA capability maturity. • Present a roadmap for maturing an organizations SOA capability. Definition: “A SOA Roadmap is a structured plan for implementing SOA capabilities that addresses the critical factors for successful SOA adoption.” Objectives of the SOA Roadmap: Theme: …“managed” adoption of a new approach achieves the objectives of the organization more quickly and at a higher level of maturity.

25. Optimization Adoption Managed Plan Value / Maturity Value Differential Application Ad-hoc assimilation Early Learning Time SOA Roadmap Theme: …“managed” adoption of a new approach achieves the objectives of the organization more quickly and at a higher level of maturity.

26. Independent Insight for Service Oriented Practice Roadmap Required Consolidation & Reuse Business Agility Information Sharing No Reuse Zone Cultural Roadblock Cultural Roadblock Service Portfolio Plan Compliance Deadlock Roadmap Effective Governance SOA Landscape Analysis Paralysis No Reuse Zone Service Anarchy

27. SOA Roadmap – Six Dimensions of SOA Maturity • Service Oriented Architecture – • Services Architectural process and alignment – Creation and on-going management of the Service Architecture and Service Portfolio; Architecture framework and repeatable processes that enable trust, interoperability, and governance in a federated environment • Services Life-Cycle Management – Consistent reference architecture with tools and platforms to manage the service lifecycle • Service Oriented Infrastructure – • Services Infrastructure – Integrated runtime environment with a common policy implementation and effective management and monitoring tools • Service Oriented Enterprise – • Initiative Management – Management policies and processes and including vision, funding strategy, charging approach, and performance measurement and monitoring tools • Organization – Defined organizational responsibilities to execute federated solutions • Collaboration – Strategy, planning and execution to enable mutual development and reuse of services

28. SOA Roadmap Focus Areas (1) • Identification and Description of Common Services: • Activities to increase maturity of service identification, definition, development, implementation, and operation, e.g., Business Process Management, and Business Activity Monitoring. • Activities to develop and manage the organizations services portfolio • Coordination of service identification and management activities and responsibilities among COIs • Activities that support the services lifecycle

29. SOA Roadmap Focus Areas (2) • Fiscally enable Community Of Interest (COI) governance bodies to: • Manage and monitor the development, integration, testing, deployment and retirement of services • Harvest EA Best practices, use cases, architectural patterns and principles, and extensions or modifications to existing life-cycle and support processes • Establish and enable key services management roles and responsibilities • Develop and implement communication and training plans • Review and extend existing project support processes for cross-organization, cross-agency services development and operation

30. SOA Roadmap Focus Areas (3) • Services Infrastructure, Integration Platform and Tooling: • Establish and sustain SOA development, test, integration and runtime environments • Identify and implement tools to monitor and enforce governance policies and service level agreements • Establish and grow a services oriented infrastructure environment • Establish repositories/registries that will capture system artifacts – including policies – to help enforce governance and manage assets throughout the lifecycle • Identify and implement key SOA management components that integrate with the infrastructure environment

31. Roadmap Sample

32. PGFSOA Overview Complete Questions?