SOA in the Federal Government Update and Status Report

1
SOA in the Federal GovernmentUpdate and Status
Report

• A Practical Guide to Federal SOA
• Presented by Daniel Ellis ( dellis_at_everware-cbdi.c
  om )
• IAC Task Lead for A PG to FSOA
• February 27, 2007

2
Agenda

• Putting SOA in Context
• Update on A Practical Guide to Federal SOA
• Looking ahead

3
Putting SOA in Context

• Commoditization of Information Technology and
  Telecommunications
• Standards drive commoditization
• Commoditization results in market consolidation,
  lower cost solutions that are more reliable, and
  higher availability of standard skills
• As commoditization occurs at one level it enables
  differentiation and innovation at the next level

4
The Life-Cycle of Technology-Driven Revolutions

• Two main periods Installation and Deployment
  separated by a market bubble and subsequent crash
• Each period is roughly 2-3 decades
• canal panic and railway panic in England,
  market crash in 1929
• The middle is characterized by a 2-13 year period
  of institutional recomposition

Carlota Perez is a research fellow at the
University of Sussex and the University of
Cambridge, and her book, Technological
Revolutions and Financial Capital The Dynamics
of Bubbles and Golden Ages (Edward Elgar, 2002),
is widely studied by the academic and business
communities. Talkin bout Information
Revolutions, CIO Insight, March 6, 2006
http//www.cioinsight.com/article2/0,1540,1940170,
00.asp
5
The Information Technology Revolution

• Beginning - introduction of the Intel
  microprocessor in 1971 (Perez)
• Middle stock market bubble and subsequent crash
  in 2001 (Perez)
• End circa 2031?

Now this is not the end. It is not even the
beginning of the end. But it is, perhaps, the end
of the beginning. -- Winston Churchill, 1942
6
Information Technology Revolution
IT Telecommunications Revolution Installation
Institutional Recomposition
Deployment
Stock market graphic with IT Revolution timeline
superimposed
7
SOA is Here

• Web Services Standards available since around
  2000 (e.g., WSDL, UDDI, SOAP)
• In 2005, Gartners Hype Cycle placed SOA near the
  bottom of the trough of disillusionment and
  projected it would achieve the plateau of
  productivity in 2-5 years.
• http//www.gartner.com/DisplayDocument?id484424
• Gartner Top 10 Technologies for 2006 highlights
  SOA as one of the most important technologies
  maturing today. 
• AFFIRM Federal CIO Survey for 2006 listed SOA as
  2 Critical Technology/Solution, behind only
  Security.
• Vendor investments have been made and SOA
  capabilities are embedded in their platforms,
  tools, and products
• Oct. 2006 IBM Announces 11 new SOA service
  offerings
• April, 2006 - Enterprise SOA, Designing IT for
  Business Innovation, by Dan Woods establishes SOA
  vision for SAP

8
SOA Stands on the Shoulders of Previous
Technologies

• Object orientation delivered a primary principle
  of SOA encapsulation
• Telecommunications enabled and stabilized the
  Internet providing the reliable platform for
  delivering messages globally
• Distributed component-based architectures solved
  many of the problems related to interoperability
  over networks (e.g., CORBA, JEE)

9
The Need for SOA and the PGFSOA

• Need is created by the natural evolution and
  adoption of information technology
• ERP Products
• Other 3rd Party COTS
• Outsourcing and Off-shoring
• Custom-built systems

10
Pressure is Becoming Acute in the Federal Space

• Presidents Management Agenda Line of Business
  Centers of Excellence to provide cross-agency and
  inter-departmental services for common business
  functions (HR, Payroll, Financial Management
  Services, Grants Management,)
• Enterprise Architecture - OMB Exhibit 300s
  process requires business cases vetted by an
  Enterprise Architecture to justify IT
  investments.
• Provides clear visibility to redundancies across
  all levels of federal government
• OMB ratchets up EA maturity requirements annually
• Federal Transition Framework (FTF) Catalogs 18
  cross-agency initiatives in the federal government

11
SOA Promises Business Agility But

• Every vendor has a different story
• Infrastructure can be costly
• Culture is not prepared for the change
• Organizations arent structured to manage the
  change
• Standards are proliferating how do they all
  relate?

12
(No Transcript)
13
Agenda

• Putting SOA in Context
• Update on A Practical Guide to Federal SOA
• Looking ahead

14
PGFSOA - Purpose of the Endeavor
Background

• Many initiatives in Federal agencies to explore
  adopt SOA
• Inconsistent approaches implementations
• AIC had chartered multiple SOA white papers

The Opportunity

• Convergence of approaches SOA vocabulary
• Abstract from specific differences to common
  aspects
• Highlight the major areas to address provide a
  customizable foundation for SOA adoption

15
PGFSOA - Objectives
Primary Objective

• Rapidly provide sound, practical guidance in
  support of agencies efforts to adopt SOA into
  their business, IT, and EA practices.

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 FY07.

16
Governance Structure
AIC Subcommittee Sponsors, IAC
8 Authoring Teams led by Co-Leads
Coordination (Execution)
Coordinator, Assistant, and Expert Advisors
Coordination
SOA Drivers Rationale
Security
Authoring
Executive Support and SOA Governance
SOA and Other Management Processes
SOA Adoption Management
Service Delivery and Composition
SOA and EA
SOA Infrastructure
17
Currently Over 50 Volunteers

• Department of Defense
• Department of Justice
• Department of Transportation
• General Services Administration
• Internal Revenue Service
• Library of Congress
• US Patent and Trademark Office
• Australian Government Information Management
  Office
• NASCIO

• Argosy Omnimedia
• ASG
• BAH
• CGI Federal
• Dovèl Technologies
• EntArch
• Everware-CBDI
• Fujitsu
• Harris
• HP
• IBM

• INNOVIM
• Lockheed Martin
• MITRE
• Mercury
• Pearson-Blueprint
• PPC
• SAIC
• SRA International
• Thomas Herbert
• Telelogic
• TowerStrides
• Webmethods

18
PGFSOA - Schedule
Fiscal Year 2007
FY08
Q2
Q3
Q4
Q1
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Jan
Oct
Final Outline
Key Messages for Each Section
1st Draft of Each Section
Draft to Editorial Board for Review
Review Ready Draft Available
Focus Group
Revised Draft Available (focus group)
Open Comment Period
Review Update
Final

• May Review Ready Draft
• May - June - Focus Group Review
• June - August Open Comment Period
• September 30 Final Release by CIO Council

19
Collaborative Effort by Volunteers

• Editorial Board appointed
• Executive Steering Committee established
• Project Coordinator identified
• Authoring Team Co-Leads identified
• Over 50 volunteers engaged and contributing
• Identified Chief Architects as the Target
  Audience
• Key Messages submitted by authoring teams and
  currently under review by the Editorial Board
  Next review session targeted for March 12
• Others who wish to participate
• Send email to dmayo_at_everware-cbdi.com and
  mike.dunham_at_thcllc.com and copy
  dellis_at_everware-cbdi.com
• Indicate areas of interest expertise which
  authoring team(s) can you support?

20
Key Value Proposition

• Establish a common body of knowledge (references
  to preceding works) and bring all together to
  form a common foundation.
• Map SOA to Enterprise Architecture frameworks and
  models.
• Conceive a common vocabulary and framework for
  SOA.
• Service Oriented Infrastructure
• Service Oriented Architecture
• Service Oriented Enterprise
• Explore the gap between where agencies are today
  and what the SOA vision promises for the future.
• Provide a roadmap by Identifying groupings of
  discrete and concrete steps that as a group work
  across the gap on all three dimensions.
• Articulate the business case drivers.

21
SOA Framework and Perspectives

• Service Oriented Infrastructure
• Focus is on message delivery and reliability and
  includes networks, ESBs and business process
  execution platforms.
• Many standards and products are already available
• Service Oriented Architecture
• Identification and design of services, their
  interdependencies, and interoperability
• There are many 3rd party models, but they arent
  yet standardized. Mission drivers have
  government specific flavor (i.e., information
  sharing)
• Service Oriented Enterprise
• Includes governance, acquisition, and management
  issues
• specifically focused on federal government
  environment (e.g., EA, CPIC)

22
Open, Collaborative Effort

• Wiki site established but targeted to move to an
  alternative collaborative environment. The
  current URL is
• http//colab.cim3.net/cgi-bin/wiki.pl?PracticalG
  uideToFederalSOA
• Top-down approach
• Outline
• Key Messages
• Text
• Drafts will be posted (in process)
• Only authoring teams can update Wiki

23
Agenda

• Putting SOA in Context
• Update on A Practical Guide to Federal SOA
• Looking ahead

24
Service and Standards Evolution
Notional Service
Service Specification
Service Implementation
Standards Evolution
Service Deployment
Service Execution
25
UML Profile and Meta Model for Services

• OMG Object Management Group (RFP Stage)
• A new Services Standard
• Enable interoperability and integration at the
  model level
• At a higher-level of abstraction separate from
  platform variability
• Address business integration and service
  interaction concerns at the architectural level -
  Architecture is the bridge between business
  requirements and IT solutions
• Enable SOA on existing platforms through MDA
• Allows for flexible platform choices
• While preventing existing solutions from
  inhibiting platform evolution
• Leverage and integrate with existing OMG
  standards for end-to-end lifecycle development
  and management
• For more information http//www.osoa.org/display/
  Main/Home

26
Service Component Architecture

• Open Service Oriented Architecture
• The Open SOA Collaboration represents an
  informal group of industry leaders that share a
  common interest defining a language-neutral
  programming model that meets the needs of
  enterprise developers who are developing software
  that exploits Service Oriented Architecture
  characteristics and benefits.
• Service Component Architecture
• 1. Java mappings for assembly model concepts such
  as "component" "component type", service,
  "reference", and "property"
• 2. Java mappings for implementing asynchronous
  and conversational services
• 3. Java mappings for specifying component
  lifecycle notifications
• 4. Java mappings for specifying service and
  implementation scopes
• For more information http//www.osoa.org/display/
  Main/Home

27
Summary

• The Information Technology and Telecommunications
  Revolution is at an inflection point
• SOA is a transformational technology at this
  critical time
• EA is a critical enabler within the federal
  government for achieving the business agility
  that SOA promises
• This is an exciting time to be in the IT business
  and federal SOA is a worthwhile endeavor

28
SOA in the Federal GovernmentUpdate and Status
Report

• A Practical Guide to Federal SOA
• Presented by Daniel Ellis ( dellis_at_everware-cbdi.c
  om )
• IAC Task Lead for A PG to FSOA
• February 27, 2007