Washington, DC January 26, 2006

1. Delivery Report Services and Components Based Architectures (SCBA) A Strategic Guide for Implementing Distributed and Reusable Services and Components in Government Washington, DC January 26, 2006 This document is confidential and is intended solely for the use and information of the client to whom it is addressed.

2. Version 3.0 of the SCBA is an import update that incorporates current architecture practices and moves beyond technology Background Contributors to the SCBA Development • SCBA is a reuse-focused architecture that incorporates • Service Oriented Architecture (SOA) • The Federal Enterprise Architecture (FEA) • Industry best practices • SCBA vs. SOA – different terms used on purpose • SOA can mean many different things: SCBA provides a non-ambiguous description • SCBA incorporates advice on organizational, governance, process, and culture • SCBA is specifically targeted at government (FEA) • SCBA incorporates both process and IT reuse • First chapter is an overall “executive strategy” • Additional chapters will add focused detail AIC CAF Value Proposition SCBA will greatly enhance agencies’ ability to accomplish their missions by increasing agility through service orientation and reducing costs through reuse. 350 commentsfrom 35 reviewers received and incorporated! Services and Components Based Architectures - Presentation to CAF

3. Agenda Background and Value Proposition Summary of Major Points in Paper Next Steps Appendix

4. This update to SCBA incorporates SOA into the FEA • Incorporate SOA • Bring up-to-date with FEA • Make more practical SCBA 3.0 SCBA 2.0 Challenges: • SCBA 2.0 was focused on component-based development, an update was needed to: • Integrate SOA • Reflect the evolution of the FEA • Evolve guidance based on feedback • SOA is an architecture design that maximizes reuse by focusing on single instances of functionality • Differs from previous approaches by not replicating the “reuse package” in multiple locations • One of the most promising and widely accepted architectural approaches to-date • Is garnering strong industry and vendor support • SOA brings strong potential benefit to government (due to the distribution of functionality across agencies) • SCBA moves from the theory of SOA into practice • Multiple chapter format used to allow greater detail while still remaining targeted at a wide audience Services and Components Based Architectures - Presentation to CAF

5. SCBA is an integrated part of the FEA – tying its layers together; given its scope, it is relevant to a wide audience Relationship between SCBA and the FEA • SCBA ties the FEA layers together • BRM and SRM provide organization • TRM provides technology • DRM provides information • SCBA provides reuse framework • SCBA is targeted at a broad audience • CIOs, CTOs, CFOs, and other Execs. • Functional / Business Line Managers • Capital Planners • Enterprise Architects • System and Solution Architects • System and Process Engineers "The President's Management Agenda and the E-Government Act of 2002 identify the overall goals for implementing E-Government: to better perform government services, and at lower cost. This SCBA paper lays out an approach that can be used to help accomplish both.” – Dick Burke, Dir., Federal Enterprise Architecture Program, OMB (January 2006) Services and Components Based Architectures - Presentation to CAF

6. Service Components are the primary units of reuse in the SCBA Service Component Reuse Component Reuse • SCBA focuses on the reuse of services and components – or “Service Components” • Service Components are assets that perform useful business functions through a well-defined interface • Service Components enable reuse both within and across organizations • Service Components are superior to traditional components: • One copy shared among all consumers, eliminating the need to manage and support multiple versions • Can be used by consumers on any technical platform (through a standard interface) • Improvements can be made without requiring consumers to modify business processes or interfaces • Example: eAuthentication service versus component One central copy reused many times Services and Components Based Architectures - Presentation to CAF

7. Reuse programs are not purely technical programs – they must incorporate changes to all dimensions of the organization Non-Technology Change Areas Non-Technical Dimensions of Reuse • Policies: need to alter policies to support reusing assets from any source, and set specific, measurable goals for levels of reuse • Strategies: needs to move from strategies that are narrowly focused on programs to ones focused on producing and integrating reusable services across the entire government • Processes: need to change software development and capital planning processes to make looking for reuse opportunities a core task • Culture: needs to change through a combination of executive recognition and incentive programs that strongly reward reuse • Governance: need to change to take into account that a service may be used by multiple organizations, and put appropriate service level agreements in place Policies Strategies Culture Services and Components Based Architectures - Presentation to CAF

8. Of course, reuse of software Service Components is also enabled through a combination of technical techniques • Design for Reuse: focus on interfaces, configurability, good documentation, and white-boxing • Tools for Reuse: tools enable publication and discovery of Service Components • Registries (such as Core.gov) provide directories of Service Components • Repositories provide the actual Service Components themselves • Reuse Infrastructure: • Internal systems can reflect available services, their interfaces, and monitor their quality • Modern shared middleware can be used to create an Enterprise Service Bus (ESB) • ESB allows services to discovery each other and communicate • Security: an import aspect of design, tools, and infrastructure – cuts across all aspects Services and Components Based Architectures - Presentation to CAF

9. Several work streams must be considered and kept in balance to make effective progress in implementing SCBAs SCBA Streams and Recommended Steps for Getting Started Services and Components Based Architectures - Presentation to CAF

10. The document produced is the first in a series of chapters that fully describe SCBA. Later chapters will provide focused details Delivered so far Services and Components Based Architectures - Presentation to CAF

11. Agenda Background and Value Proposition Summary of Major Points in Paper Summary and Next Steps Appendix

12. Summary and Q&A Session • Summary • SCBA is a framework that cuts across the FEA layers to encourage reuse • Version 3.0 updates the SCBA to incorporate SOA and reflects the evolution of the FEA • Major focuses are reuse of Service Components and comprehensive reuse programs • SCBA adds value by increasing process agility and reducing costs • Questions? Services and Components Based Architectures - Presentation to CAF

13. Next Steps • Next Steps • Seeking AIC endorsement of Chapter 1 • Discuss strategy for completing Chapters 2 through 9 • Commence work on Chapters 2 through 9 Services and Components Based Architectures - Presentation to CAF

14. Agenda Background Paper Content Next Steps Appendix

15. Paper Contributors (in alphabetical order) • James Benson, AIC Contractor Support • Richard von Bostel, OMB Contractor Support • L. Reynolds Cahoon, National Archives & Records Administration • Nathaniel A.F. Clark, AIC Contractor Support • Josiah Cushing, AIC Contractor Support • Bobby Jones(1), Department of Homeland Security, Federal Emergency Management Agency • Karen Kaye, Nuclear Regulatory Commission • David R. Mayo, Industry Advisory Council / EverWare, Inc. • Marion A. Royal, General Services Administration • Adam Schwartz, Office of Management and Budget • James W. Smith, Office of Management and Budget (1) Services and Components Based Architectures Committee Leader Services and Components Based Architectures - Presentation to CAF

16. Discussion Topics for Breakout Session Note: This session is intended to be highly interactive and the only participation pre-requisite is that you have read SCBA v3.4 • Are there any concepts or information from the SCBA Paper or today’s presentation you would like further explained? • Have you had experience in your Department or Agency in implementing a service component based architecture? • Are you aware of any leading edge implementations of service component based architecture within the federal government or the private sectors? • What key messages or points did you glean from the document? • Is the document too technical, not technical enough or just right? (please keep in mind that this chapter is targeted at the broadest audience of all the chapters) • Are there any future chapters that you would like to see added/removed/combined/modified in the document? • Can you recommend any subject matter experts to contribute to the future chapters? Services and Components Based Architectures - Presentation to CAF