1

Service Oriented Architecture:A Unifying Governance

Presentation by the SOA CoPFor the Architecture & Infrastructure Committee

Federal CIO CouncilMarch 16, 2006 (Updated March 29, 2006)

http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP

2

Overview• 1. Introduction

– Brand Niemann, Interim SOA CoP Co-Chair– Greg Lomow, Interim SOA CoP Co-Chair

• 2. IAC Committees:– SOA: Greg Hauser, Chair, and EA, John Dodd,

Member• 3. Reference Model Maintenance Process• 4. Some Next Steps:

– Susan Turnbull, Emerging Technology Subcommittee Co-Chair

• 5. Questions and Answers– All

3

1. Introduction

• The stars are aligning around the SOA galaxy: – Chief Architect Richard Burk spoke of needing “a real,

target architecture”, which is presumably SOA, at the Chief Architects Forum.

– The new AIC Leadership has proposed renaming the Components Subcommittee the Services Subcommittee that will include SOA.

– The Object Management Group, OASIS, etc. are all talking about SOA.

– The Industry Advisory Committee has a new SOA Committee.

– DRM 2.0 assumed that Data Services would be implemented with SOA.

4

1. Introduction

• SOA is already a common thread across the AIC Subcommittees:– Governance: SOA Governance and SOA in the Reference

Model Maintenance Process.– Services: Soon Services with SOA.– Emerging Technology: SOA for Data (XML CoP and SICoP):

• More agile than conventional data management and data standards approaches.

– And elevating Core.gov to serve all the SCs will promote collaboration and integration.

– Data Architecture (Announced March 16th - see next slide).• John Dodd Comment: Very good idea that would align

the many AIC initiatives around a given theme for both Enterprise SOA and Extended Enterprise SOA.

5

1. Introduction

SOA CoP

6

1. Introduction

• So AIC & OMB Leadership called for some focus on SOA and we did the following:– January 24th Workshop on Bootstrapping

Service-Oriented Architecture and Semantic Interoperability Toward Transformative Practice Featuring:

• SOA for E-Gov Initiatives Like E-Grants at the Federal and State Level and FHA Data Architecture.*

• SOA Governance.* (see next slide)• SOA Best Practices.*

* Will use selected slides posted at SOA CoP Wiki if time:http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP

7

1. Introduction

• Highlights of SOA Governance Issues:– Difficulty understanding the relationship between the

FEA and SOA (slides 9-15).– The need to understand the software design principle

of “abstraction and indirection” and its application to SOA to know when to apply SOA (slides 19-26).

– The need for some best practices of SOA, Composite Applications, SSOA, and their platforms (slide 44).

– The need for some best practices of SOA Governance approaches (slides 45-46).

– Comments at Chief Architects Forum, January 26, 2006 (slides 55-56).

See http://web-services.gov/scopesoa01242006.ppt

8

1. Introduction

• So AIC & OMB Leadership called for some focus on SOA and we did the following (continued):– January 26, 2006, Announcement at the Chief

Architects Forum Meeting.– January 27, 2006, General Call for Participation (Very

Positive Responses Received).– January 31, 2006, Greg Lomow, Bearing Point, and

Co-Author of "Understanding SOA with Web Services" Invited to be Co-Chair with Brand Niemann, SICoP, Chair, for the initial phase of the CoP.

9

1. Introduction

• So AIC & OMB Leadership called for some focus on SOA and we did the following (continued):– February 9-10, 2006, The 4th Semantic Interoperability for E-

Government Conference, where several Semantic (or Ontology-driven) SOA’s were presented and the SOA in E-Government Conference, May 23-24, 2006, at MITRE, McLean, Virginia, was announced.

– February 17, 2006, new IAC SOA Committee agreed to participate.

– February 22, 2006, First Meeting - Conference Call and Oracle-Reston.

– March 3, 2006, Wiki Training – Conference Call.– March 13, 2006, Conference Call with IAC SOA and EA

Committees.– March 17, 2006, Second Meeting - Conference Call.

10

1. Introduction

• Suggested Structure (patterned after the very successful DRM 2.0 CoP):– SOA Reference Models, Specifications, and

Standards:• Ken Laskey and Rebekah Metz, OASIS SOA-RM TC.

– SOA Governance:• Eric Marks, Recall February 16th Presentation.

– SOA Implementation and Testing:• Cory Casanave, Contactor to GSA CIO for MDA on FMEA.

– Plus Connections to the FEA Service Components Reference Model:

• George Thomas, GSA Chief Architect and RMMP Process Lead for the FEA SCRM.

11

1. Introduction• SOA for E-Government Conference, May 23, 2006:

– 7:30 – 8:30 AM, Conference Check In (must be pre-registered)– 8:30 – 8:45 AM, MITRE Welcome, Rick Tucker, Conference

Host– 8:45 - 9 AM, Welcome and Conference Overview, Co-Chairs:

Greg Lomow, Bearing Point and Brand Niemann, SICoP Chair– 9:00 - 10:30 AM, Opening Keynote and Demonstration:

• Ron Schmelzer, ZapThink and Author of “Service Orient or Be Doomed" (see next slide)

• Introduced by Cory Casanave, CEO/President, Data Access Technologies, Inc., SOA Demo Strawman

– 10:30 - 11:00 AM, BREAK– 11:00 - 12 NOON, Featured Presentation and Panel

• David Allen, DoD, The DoD CoI Forum SOA Governance Process• Six Panelists (Invited)

– 12 NOON - 2 PM, Networking Lunch (MITRE Cafeteria) and Posters/Vendors

12

1. Introduction• "This is by far the finest publication

on SOA of our time. From cover to back, Service Orient or Be Doomed! strips away the layers of confusion most IT stakeholders face when confronted with enterprise architecture, and illustrates pragmatic and practical paths towards a sustainable and efficient enterprise architecture. Both the technically savvy and the bean counters will enjoy this book that speaks to the critical points they need to understand."– Duane A. Nickull Senior Standards

Strategist, Adobe Systems, Inc. Chair, OASIS SOA Reference Model Technical Committee Vice chair, United Nations CEFACT (UN/CEFACT)

13

1. Introduction

• SOA for E-Government Conference, May 23, 2006 (continued):– 2 - 3:45 PM, Summary Reports (20 minutes each and then 90

minutes each on the May 24th Agenda)• SOA Reference Models, Specifications, and Standards, Rebekah

Metz, Booz Allen Hamilton• SOA Governance, President/CEO, AgilePath• SOA Implementation and Testing, Cory Casanave, CEO/President,

Data Access Technologies, Inc.• Connections to the FEA Service Components Reference Model,

George Thomas, Chief Architect, GSA– 3:45-4 PM, SHORT BREAK– 4 - 5 PM, Closing Keynote and Dialogue, Richard Soley, CEO,

OMG– 5 - 5:30 PM, Special Recognitions, Networking, and Then Must

Leave the Facility

14

1. Introduction• SOA for E-Government Conference, May 24, 2006:

– 7:30 – 8:30 AM, Conference Check In (must be pre-registered)– 8:00 AM - 4:15 PM, Tutorials (LIMITED TO 40) (room for two -

1/2/ day or one full-day)• CBDI , David Sprott• Sandpiper Software - MDA and Semantic Web Services and Case

Study, Elisa Kendall and Sam Chance– Breakout Session (Auditorium Foyer): 12 Presentations– Auditorium Sessions:– 8:30 - 10 AM, SOA Reference Models, Specifications, and

Standards, Rebekah Metz, Booz Allen Hamilton• Featured Presentations/Demonstrations and Open Discussions

– 10:00-10:30 AM, BREAK– 10:30 AM – 12 NOON, SOA Governance, Eric Marks,

President/CEO AgilePath• Featured Presentations/Demonstrations and Open Discussions

– 12 NOON - 1 PM, Networking Lunch (MITRE Cafeteria)

15

1. Introduction

• SOA for E-Government Conference, May 24, 2006 (continued):– 1 - 2:30 PM, SOA Implementation and Testing, Cory Casanave,

CEO/President, Data Access Technologies, Inc.– Featured Presentations/Demonstrations and Open Discussions:

• Chris Smith, GSA Director of Financial Management Systems, Financial Management EA Project Supporting an SOA architecture for a government line of business.

– 2:30-2:45 PM, SHORT BREAK– 2:45 - 4:15 PM, Connections to the FEA Service Components

Reference Model, George Thomas, Chief Architect, GSA.• Featured Presentations/Demonstrations and Open Discussions.

– 4:15 - 5 PM, Networking and Then Must Leave the Facility.

16

1. Introduction

• E-Government needs a comprehensive guide to SOA with Web Services standards and best practices for implementation to get from the current "as is" to the future "to be" architecture. This book meets that need superbly.– Brand Niemann, Ph.D., Co-

Chair, SICoP, U.S. Federal CIO Council

Introducing

17

2. IAC Committees

• SOA:– Greg Hauser, Chair

• Webworld Technologies– Gerry Anderson, Programs Chair

• Oracle– Bob Brogan, Software Focus Group Manager

• BEA– Jana Jackson, SOA Benefits & Cultural Change Focus Group

Manage• Avanziamo

• EA:– John Dodd, Member, CSC:

• Other IAC Members in Attendance.• Provide High-Level Summary and Schedule for Discussion.

18

2. IAC Committees

• Conference Call, March 13th:– Overview of New AIC Subcommittee Structure.– Agreement to Coordinate Across Two IAC

Committees (SOA and EA) in the SOA CoP.– Focus Shifts from FEA Reference Model Taxonomies

to SOA in the FEA Reference Models (slides 17-18).– Focus Shifts from White Papers to SOA

Demonstrations of Interoperability:• The full life-cycle of a multi-party SOA solution using multiple

participants and multiple technologies collaborating via SOA standards in an architected community (see Cory Casanave, SOA Demo Strawman).

19

3. Reference Model Maintenance Process

• What is the RMMP?:– Evolves and modifies the FEA reference models.– Ensures all Federal agencies have a mechanism by

which to help shape the FEA reference models.– Provides transparency into the reference model

development process.

• Contacts:– Rick Murphy, lead (Richard.Murphy@gsa.gov)– Roy Mabry, Co-Chair, AIC Governance

Subcommittee (Roy.Mabry@osd.mil)

20

3. Reference Model Maintenance Process

• What have we learned?:– Consequences of Change:

• Impact on OMB analytical processes.• Vendors.

– Identifying Trends:• Large scale modifications to the Service Reference

Model (SRM) as it relates to Service Oriented Architecture (SOA) seem to be emerging.

• Requires further collaboration.

21

4. Some Next Steps

• Susan Turnbull, Emerging Technology Subcommittee Co-Chair:– Participate in Regular Wiki Training.– Participate in Building the SOA CoP and its Dynamic

Knowledge Repository for AIC Needs.• An Email Discussion Group Has Been Established.

– Register for the SOA for E-Government Conference, May 23-24, 2006.

– Provide suggestions for Future Workshops:• E.g., Networking the DRM 2.0 and Records Management

Profile CoPs.

22

5. Questions and Answers

• Now or email to SOA CoP Email Discussion List