1. 1 SOA Essentials: What Department Heads Need to Know Featuring expert panel discussion and collaboration demonstration. Dr. Brand Niemann, US EPA Senior Enterprise Architect and Federal SOA CoP, Co-Chair Grand Hyatt (Constitution D/E Room), Washington, DC February 13, 2007 Google: SOACoPDemo3 Practical Guide to SOA Implementation SOA for E-Government 2007

2. 2 Key Questions Why are government agencies rushing to support a Service Oriented Architecture (SOA)? The deployment of SOA is expected to help transform the way government services are delivered, breaking down silos and lowering costs. (see slide 3) How do you define SOA? (see slide 4) Do you know how SOA will impact your agency and its constituents? (see slide 5) Are you having trouble getting started? (see slides 5-7) See http://colab.cim3.net/cgi-bin/wiki.pl?SOAforEGovernment_2006_10_3031

3. 3 The Business Value of Enterprise Architecture and SOA The Value Proposition of a SOA: –We implement SOA for two major reasons. First is the ability to save development dollars through reuse of services. Second is the ability to change the IT infrastructure faster to adapt to changing needs of the business, or agility. Value = (NSR*DR) * C, where the Number of Services available for Reuse (NSR), the Degree of Reuse (DR) from system to system, as well as the Complexity (C) of each service: –For example, if you have 100 services available for reuse (NSR=100), and the degree of reuse is at 50 percent (DR=.50), and complexity of each service is, on average, at 300 function points, the value would look like this: Value = (100*.5) * 300 Or Value = 15,000, in terms of reuse. http://colab.cim3.net/file/work/SOACoP/2006_10_3031/Presentations/DLinthicum10302006.ppt

4. 4 Abstraction, Indirection, and Loose Coupling Architects of both software and physical structures routinely use the principle of abstraction to isolate complex components and reduce the scope of a problem to be solved (“see the forest for the trees”). –By definition, ontology is abstraction and is the ultimate abstraction tool for information. Indirection is a concept that is used to plan for future uncertainty. Simply put, indirection is when two things need to be coupled, but instead of coupling them directly, a third thing is used to mediate direct, brittle connections between them. Chapter 7 in Adaptive Information: Improving Business Through Semantic Interoperability, Grid Computing, and Enterprise Integration, Pollock and Hodgson, Wiley Inter-science, 2004.

5. 5 Getting Started A Practical Way to See If SOA Has Business Value for Your Organization: –Learn more about SOA by working on the Practical Guide to Federal SOA (PGFSOA). –Participate in the Phase 3 Super-pilot built on Open Source SOA Infrastructure. –Participate in the 3 rd SOA for E-Government Conference (May 1-2, 2007, MITRE). Registration: –http://www.mitre.org/register/soa/ ACT/IAC SOA Committee Survey: –http://www.soa-iac.org/soasurvey

6. 6 Phase 3 Super-pilot Built on Open Source SOA Infrastructure IONA Federal Jumpstart Program - Accelerate the adoption of Open Source SOA*: –Confusion about how to get started with SOA. –A Federally-applicable demonstration delivered on a pre-configured virtual appliance. –A reference implementation geared to incremental adoption of SOA components. –A “sandbox” for SOA experimentation - Allows experimentation of SOA components and/or intermediaries. –Visualize applicable use cases with a highly scalable, easily accessible SOA infrastructure. * IMPORTANT NOTE: All vendors with Open Source SOA Enterprise Service Buses (ESB) are especially invited to participate.

7. 7 Phase 3 Super-pilot Built on Open Source SOA Infrastructure Use Cases: –1. SOA CoP Phase 2 Demo: Cory Casanave, ModelDriven.Org, Lead –2. NCOIC: Bob Marcus, SRI, Bob Kilker, IONA, Chris Gunderson, Netcentric Certification Office and W2COG Initiatives, and Brand Niemann. –3. Maritime Domain Awareness, Bob Kilker, IONA –4. Financial Data, XML CoP, XBRL CoP, Association of Government Accounts, etc. Federal Funding Accountability and Transparency Act of 2006: –http://en.wikipedia.org/wiki/Federal_Funding_Accountability_an d_Transparency_Act_of_2006

8. 8 Discussion Topics The core concepts within a service oriented environment. Top concerns with implementing SOA. Key strategies (see slide 9). How SOA can positively impact your agency. Web services – a case study in SOA (see slide 10). See http://colab.cim3.net/cgi-bin/wiki.pl?SOAforEGovernment_2006_10_3031 for answers and best practice examples of all of these topics.

9. 9 Key Strategies US Government…SOA To the Rescue?, David Linthicum, Closing Keynote at the 2nd SOA for E-Government Conference, October 30-31, 2007: –5 Ways to Make Your SOA a Success: Understand the pain. Define the value. Focus on understanding (Steps to SOA). Remember the people. Focus longer term. http://colab.cim3.net/file/work/SOACoP/2006_10_3031/Presentations/DLinthicum10302006.ppt

10. 10 SOA CoP Phase 2 Demo Business Intelligence (Reports/Dashboard) NEF Program (Manages Projects) Employee (Reports Time) Finance LoB (Calculates Costs) HR/Payroll - LoB (Allocates Time to Projects) Contractor (Produces Invoices) MetaMatrix Data Services Sun MicroSystems DynAccSys Web Service Web Service Web Service Web Service Web Service Web Form Data Access Executable Model Data Access Executable Model Dashboard Client Implementation