recent briefing at input event
TRANSCRIPT
Independent Guidance for Service Architecture and Engineering
SOA in the Federal GovernmentUpdate and Status Report
A Practical Guide to Federal SOAPresented by Daniel Ellis ( [email protected] )IAC Task Lead for A PG to FSOA
February 27, 2007
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Agenda
Putting SOA in Context Update on “A Practical Guide to Federal SOA” Looking ahead
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Information Technology Revolution
Stock market graphic with IT Revolution timeline superimposed
IT & Telecommunications RevolutionInstallation Institutional Recomposition Deployment
You are
here
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
SOA is Here
Web Services Standards available since around 2000 (e.g., WSDL, UDDI, SOAP)
In 2005, Gartner’s 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?id=484424
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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)
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Pressure is Becoming Acute in the Federal Space
President’s 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, Grant’s 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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
SOA Promises Business Agility But…
Every vendor has a different story
Infrastructure can be costly
Culture is not prepared for the change
Organizations aren’t structured to manage the change
Standards are proliferating – how do they all relate?
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Agenda
Putting SOA in Context Update on “A Practical Guide to Federal SOA” Looking ahead
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
PGFSOA - Purpose of the Endeavor
Many initiatives in Federal agencies to explore & adopt SOA
Inconsistent approaches & implementations AIC had chartered multiple SOA white papers
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
PGFSOA - Objectives
Rapidly provide sound, practical guidance in support of agencies’ efforts to adopt SOA into their business, IT, and EA practices.
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.
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Governance Structure
Coordinator, Assistant, and Expert Advisors
AIC SubcommitteeSponsors, IAC
Editorial Board
Content&
Revisions
Coordination(Execution)
SOA Drivers & Rationale Executive
Support and SOA
Governance
SOA Adoption &
Management SOA and EA SOA
Infrastructure
Service Delivery and Composition
SOA and Other
Management Processes
8 Authoring Teams led by Co-Leads
Security
Executive Steering
Committee
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
PGFSOA - Schedule
May – “Review Ready” Draft May - June - Focus Group Review June - August – Open Comment Period September 30 – Final Release by CIO Council
Q2
Final
Fiscal Year 2007
Q3 Q4
Feb Mar Apr May Jun Jul Aug SepJan Oct
Final Outline
1st Draft of Each Section
Key Messages for Each Section
“Review Ready” Draft Available
Draft to Editorial Board for Review
Open Comment Period
Q1
FY08
Revised Draft Available (focus group)FocusGroup
Review & Update
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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 [email protected] and
[email protected] and copy [email protected] Indicate areas of interest & expertise – which authoring team(s) can
you support?
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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.
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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 aren’t 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)
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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?PracticalGuideToFederalSOA
Top-down approach Outline Key Messages Text
Drafts will be posted (in process) Only authoring teams can update Wiki
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Agenda
Putting SOA in Context Update on “A Practical Guide to Federal SOA” Looking ahead
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
Service and Standards Evolution
Notional
Service
Service Specification
Service Implementation
Service Deployment
Service Execution
*
1
*
1
*
1
*
1
Standards Evolution
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
© 2006 Everware-CBDI Inc
Independent Guidance for Service Architecture and Engineering
www.cbdiforum.com
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
Independent Guidance for Service Architecture and Engineering
SOA in the Federal GovernmentUpdate and Status Report
A Practical Guide to Federal SOAPresented by Daniel Ellis ( [email protected] )IAC Task Lead for A PG to FSOA
February 27, 2007