Recent Briefing at INPUT Event


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Good morning, it’s a pleasure to be here today. I am the IAC EA SIG task lead for A Practical Guide to Federal SOA. I believe I’m here is your Key Note speaker due to an unfortunate accident of timing – OMB EA submissions are due tomorrow and all of the Federal Government Chief Architect’s are hard at work finalizing their submissions
  • The importance of SOA can best be understood when it is viewed within the context of the Information Technology & Telecommunications revolution. This revolution continues to be a rapid-fire series of technological innovations, each building upon the other and eventually either being overcome by subsequent innovations or standardized and commoditized into technology layers that serve as the vital foundation for the next wave. (bullets)
  • To gauge where we are within the Info Tech & Tele revolution I turned to Carlota Perez, a fellow at the University of Sussex and the University fo Cambridge. Original industrial revolution – water powered machines and canal systems Second industrial revolution – 1830’s, steam and iron railways Age of Steel and heavy engineering – 1870’s Mass production revolution - 1920’s, established the “American Way of Life” Her book in 2002 was a comparative study of technological revolutions and their relationship to financial capital. CIO insight interviewed Perez last year and I think a brief recap can help us understand SOA within the larger framework of the ITT revolution. Two main periods The installation period is full of possibilities as understanding of the potential of the technological transformation grows. It’s a period of investment – and tends to favor those with investment capital. The deployment period sees a transfer of financial capital from the investment side to the production side. Between these two periods, and demarcated by a market bubble and subsequent crash, is a shorter period of institutional reconstitution were new governance structures and institutions must be established to deal with the new world the revolution has created.
  • After a series of defeats from Dunkirk to Singapore, Churchill could finally tell the House of Commons that "we have a new experience. We have victory - a remarkable and definite victory." Alexander and Montgomery turned back Rommel's forces at El Alamein, thus winning what Churchill called "The Battle of Egypt."
  • I have included bright red arrows to note the key events in 1971 and 2001, introduction of Intel’s microprocessor and the deflating of the stock market bubble respectively. So, according to Perez, we are in the middle of the primary inflection point of the ITT revolution. A 2-13 year period where we can expect to see institutional change of the largest order and a redistribution of capital from investment to production. SOA is the key technology that the entire IT marketplace seems to be coalescing around. We’ve seen buzz before, but here we have the entire software community - platform vendors, development tool vendors, ERP vendors, other 3 rd party COTS vendors, commercial organizations and federal government organizations as well as IT service providers. “ Well, the income polarization has occurred with each of the major bubbles, and the need to expand markets and to create opportunities for investment has appeared each time at this point in the surge. The Golden Age is essentially the flourishing of the full range of possibilities under more favorable institutional conditions, often with the intervention of the state reining in finance and redistributing income. But each revolution is unique both in its opportunities and its dangers, in the progress it brings and the problems it creates. That is the social challenge that faces us in each surge. Institutional innovations are needed now to accompany and foster the technological and organizational ones.” (Perez) Institutional Recomposition “ This is the period in which perverse trends have to be reversed: The income polarization and the madness of the bubble years have to be overcome, but also the decision-making power has to move (or be moved) from the hands of financial capital to those of production capital.”
  • Make no mistake, SOA is here, and it is a critical step toward realizing the full potential of IT. From the key enabling standards, to the support of pundits, industry research organizations, and investments made by industry leaders at all levels – SOA is here. If history serves a good reference, we will see a solid foundation in SOA be the key enabler for the next wave of IT innovation.
  • Like the other technology waves before it, SOA stands on the shoulders of prior successes, and borrows key innovations, reapplying them slightly differently or at a different scale in the new environment. Here I list only three of the many technology forerunners that pave the way for SOA today.
  • But the need for SOA, the drivers for it, are not something fabricated by the industry, but the natural result of all the technology consumption that has preceded it. As we see commoditization and consolidation we find less and less reliance on custom software and more and more on 3 rd party providers. Even here, there is an ongoing transformation from 3 rd party COTS to ERP to hosted services that can be outsourced and perhaps off-shored. Today’s IT environment is of immense complexity as these solutions combine, often in an ad-hoc, evolutionary fashion driven by today’s most urgent need. As a result there is a compelling need to have all these products interoperating in a manageable environment. SOA promises to deliver business agility through the appropriate use of encapsulation to define services, separate concerns, and reduce coupling. All this and reuse too.
  • There are also government specific drivers for SOA.
  • But SOA offers challenges too. It is not a silver bullet. (points above) Nonetheless, it is the best we have available today, and much, much better than the paradigms of the past. It is also happening, whether we buy into it or not, the tools, systems, and products today have SOA built into them – so our choice is to let services anarchy reign, where every developer or every project decides how they will adopt them, or to step up to the challenge of enterprise-wide adoption An important point is that the promised business agility cannot be realized by simply changing all our current integration points to service-based integration points. To achieve business agility we must purposefully define and identify the core collection of semantically interoperable services required to support each organization’s business. This requires both planning and new governance capabilities.
  • Many initiatives within the federal government rely on SOA and all of these have been and still are moving ahead in largely independent fashions. The Federal Transition Framework catalog identified 18 cross-agency initiatives underway today. At the same time, Dick Burke, Chief Architect of the Federal Government, has been espousing that we view the “enterprise” as the entire federal government. Ultimately the AIC decided that a single SOA white paper should proceed to lay a foundation for the others to launch from. This led to A PGFSOA which has been jointly chartered by the FCIOC AIC Services subcommittee and AIC Governance subcommittee The opportunity is to provide a demystification of SOA for the federal government, a common foundation to build upon, and a roadmap for federal government SOA adoption.
  • The objectives for A Practical Guide to Federal SOA is to follow in the footsteps of A Practical Guide to Federal EA and build upon the Service-Component Based Architecture white papers already published. The primary need is to get practical guidance into the hands of the Federal Governments chief architects so that as their organizations move to adopt SOA they can most effectively focus their resources. Secondary objectives are to establish an open and collaborative process that will result in a final release during this fiscal year.
  • AIC Governance Subcommittee Co-Chairs – Roy Mabry and Darren Ash AIC Services Subcommittee Co-Chairs – Kshemendra Paul and George Thomas IAC EA SIG Services Subcommittee Chair, David Mayo
  • We have been able to pull together a highly reliable group of volunteers that have really been driving ahead rapidly. In fact, both Dennis Wisnosky and Brand Niemann have been consistent contributors to this effort as have members of some of the other panelists organizations.
  • Our schedule is aggressive and while I hate to admit it I expect we’ll see it slip a little bit, but I think we need the aggressive push up front to hit our ultimate target for publication this fiscal year.
  • While we are close to closing out our authoring teams we do have some spots available. Shortly after March 12, there will be a final level-setting of the authoring teams by the Editorial Board, and after that it really won’t be practical bring in other folks. If you do have an interest in participating, please notify me soon and we can see if we can get you involved with the appropriate group.
  • Secondary audience is Chief Information Officers and Program Executives. Both in terms of directly reading the document and in terms of enabling the CA to explain, convince, and execute on SOA with these stakeholders. Business Case - in a way that support the development of Agency specific roadmaps with clear linkage to business benefits and risk mitigation at each step.
  • Good morning, it’s a pleasure to be here today. I am the IAC EA SIG task lead for A Practical Guide to Federal SOA. I believe I’m here is your Key Note speaker due to an unfortunate accident of timing – OMB EA submissions are due tomorrow and all of the Federal Government Chief Architect’s are hard at work finalizing their submissions
  • Recent Briefing at INPUT Event

    1. 1. SOA in the Federal Government Update and Status Report A Practical Guide to Federal SOA Presented by Daniel Ellis ( [email_address] ) IAC Task Lead for A PG to FSOA February 27, 2007
    2. 2. Agenda <ul><li>Putting SOA in Context </li></ul><ul><li>Update on “A Practical Guide to Federal SOA” </li></ul><ul><li>Looking ahead </li></ul>
    3. 3. Putting SOA in Context <ul><li>Commoditization of Information Technology and Telecommunications </li></ul><ul><ul><li>Standards drive commoditization </li></ul></ul><ul><ul><li>Commoditization results in market consolidation, lower cost solutions that are more reliable, and higher availability of standard skills </li></ul></ul><ul><ul><li>As commoditization occurs at one level it enables differentiation and innovation at the next level </li></ul></ul>
    4. 4. The Life-Cycle of Technology-Driven Revolutions <ul><li>Two main periods – Installation and Deployment – separated by a market bubble and subsequent crash </li></ul><ul><ul><li>Each period is roughly 2-3 decades </li></ul></ul><ul><ul><li>“ canal panic” and “railway panic” in England, market crash in 1929 </li></ul></ul><ul><ul><li>The middle is characterized by a 2-13 year period of institutional recomposition </li></ul></ul>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,1540,1940170,00.asp
    5. 5. The Information Technology Revolution <ul><li>Beginning - introduction of the Intel microprocessor in 1971 (Perez) </li></ul><ul><li>Middle – stock market bubble and subsequent crash in 2001 (Perez) </li></ul><ul><li>End – circa 2031? </li></ul>“ 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. 6. Information Technology Revolution Stock market graphic with IT Revolution timeline superimposed IT & Telecommunications Revolution Installation Institutional Recomposition Deployment You are here
    7. 7. SOA is Here <ul><li>Web Services Standards available since around 2000 (e.g., WSDL, UDDI, SOAP) </li></ul><ul><li>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. </li></ul><ul><ul><li> </li></ul></ul><ul><li>Gartner Top 10 Technologies for 2006 highlights SOA as one of the most important technologies maturing today.  </li></ul><ul><li>AFFIRM Federal CIO Survey for 2006 listed SOA as #2 Critical Technology/Solution, behind only Security. </li></ul><ul><li>Vendor investments have been made and SOA capabilities are embedded in their platforms, tools, and products: </li></ul><ul><ul><li>Oct. 2006 – IBM Announces 11 new SOA service offerings </li></ul></ul><ul><ul><li>April, 2006 - Enterprise SOA, Designing IT for Business Innovation, by Dan Woods establishes SOA vision for SAP </li></ul></ul>
    8. 8. SOA Stands on the Shoulders of Previous Technologies <ul><li>Object orientation delivered a primary principle of SOA – encapsulation </li></ul><ul><li>Telecommunications enabled and stabilized the Internet – providing the reliable platform for delivering messages globally </li></ul><ul><li>Distributed component-based architectures solved many of the problems related to interoperability over networks (e.g., CORBA, JEE) </li></ul>
    9. 9. The Need for SOA and the PGFSOA <ul><li>Need is created by the natural evolution and adoption of information technology: </li></ul><ul><ul><li>ERP Products </li></ul></ul><ul><ul><li>Other 3 rd Party COTS </li></ul></ul><ul><ul><li>Outsourcing and Off-shoring </li></ul></ul><ul><ul><li>Custom-built systems </li></ul></ul>
    10. 10. Pressure is Becoming Acute in the Federal Space <ul><li>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,…) </li></ul><ul><li>Enterprise Architecture - OMB Exhibit 300s process requires business cases vetted by an Enterprise Architecture to justify IT investments. </li></ul><ul><ul><li>Provides clear visibility to redundancies across all levels of federal government </li></ul></ul><ul><ul><li>OMB ratchets up EA maturity requirements annually </li></ul></ul><ul><li>Federal Transition Framework (FTF) – Catalogs 18 cross-agency initiatives in the federal government </li></ul>
    11. 11. SOA Promises Business Agility But… <ul><li>Every vendor has a different story </li></ul><ul><li>Infrastructure can be costly </li></ul><ul><li>Culture is not prepared for the change </li></ul><ul><li>Organizations aren’t structured to manage the change </li></ul><ul><li>Standards are proliferating – how do they all relate? </li></ul>
    12. 13. Agenda <ul><li>Putting SOA in Context </li></ul><ul><li>Update on “A Practical Guide to Federal SOA” </li></ul><ul><li>Looking ahead </li></ul>
    13. 14. PGFSOA - Purpose of the Endeavor <ul><li>Many initiatives in Federal agencies to explore & adopt SOA </li></ul><ul><li>Inconsistent approaches & implementations </li></ul><ul><li>AIC had chartered multiple SOA white papers </li></ul><ul><li>Convergence of approaches & SOA vocabulary </li></ul><ul><li>Abstract from specific differences to common aspects </li></ul><ul><li>Highlight the major areas to address & provide a customizable foundation for SOA adoption </li></ul>Background The Opportunity
    14. 15. PGFSOA - Objectives <ul><li>Rapidly provide sound, practical guidance in support of agencies’ efforts to adopt SOA into their business, IT, and EA practices. </li></ul><ul><li>Collaborative effort by knowledgeable individuals within government and industry. </li></ul><ul><li>Initial review with a select focus group to refine document. </li></ul><ul><li>Broad-based distribution for open review and comment period. </li></ul><ul><li>Final release by CIO Council by end of FY07. </li></ul>Primary Objective Secondary Objectives
    15. 16. Governance Structure Coordinator, Assistant, and Expert Advisors AIC Subcommittee Sponsors, IAC Coordination 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 Authoring 8 Authoring Teams led by Co-Leads Security Editorial Board Content & Revisions Executive Steering Committee
    16. 17. Currently Over 50 Volunteers <ul><li>Department of Defense </li></ul><ul><li>Department of Justice </li></ul><ul><li>Department of Transportation </li></ul><ul><li>General Services Administration </li></ul><ul><li>Internal Revenue Service </li></ul><ul><li>Library of Congress </li></ul><ul><li>US Patent and Trademark Office </li></ul><ul><li>Australian Government Information Management Office </li></ul><ul><li>NASCIO </li></ul><ul><li>Argosy Omnimedia </li></ul><ul><li>ASG </li></ul><ul><li>BAH </li></ul><ul><li>CGI Federal </li></ul><ul><li>Dovèl Technologies </li></ul><ul><li>EntArch </li></ul><ul><li>Everware-CBDI </li></ul><ul><li>Fujitsu </li></ul><ul><li>Harris </li></ul><ul><li>HP </li></ul><ul><li>IBM </li></ul><ul><li>INNOVIM </li></ul><ul><li>Lockheed Martin </li></ul><ul><li>MITRE </li></ul><ul><li>Mercury </li></ul><ul><li>Pearson-Blueprint </li></ul><ul><li>PPC </li></ul><ul><li>SAIC </li></ul><ul><li>SRA International </li></ul><ul><li>Thomas & Herbert </li></ul><ul><li>Telelogic </li></ul><ul><li>TowerStrides </li></ul><ul><li>Webmethods </li></ul>
    17. 18. PGFSOA - Schedule <ul><li>May – “Review Ready” Draft </li></ul><ul><li>May - June - Focus Group Review </li></ul><ul><li>June - August – Open Comment Period </li></ul><ul><li>September 30 – Final Release by CIO Council </li></ul>Q2 Final Fiscal Year 2007 Q3 Q4 Feb Mar Apr May Jun Jul Aug Sep Jan Oct Final Outline 1 st 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) Focus Group Review & Update
    18. 19. Collaborative Effort by Volunteers <ul><li>Editorial Board appointed </li></ul><ul><li>Executive Steering Committee established </li></ul><ul><li>Project Coordinator identified </li></ul><ul><li>Authoring Team Co-Leads identified </li></ul><ul><li>Over 50 volunteers engaged and contributing </li></ul><ul><li>Identified Chief Architects as the Target Audience </li></ul><ul><li>Key Messages submitted by authoring teams and currently under review by the Editorial Board – Next review session targeted for March 12 </li></ul><ul><li>Others who wish to participate: </li></ul><ul><ul><li>Send email to [email_address] and [email_address] and copy [email_address] </li></ul></ul><ul><ul><li>Indicate areas of interest & expertise – which authoring team(s) can you support? </li></ul></ul>
    19. 20. Key Value Proposition <ul><li>Establish a common body of knowledge (references to preceding works) and bring all together to form a common foundation. </li></ul><ul><li>Map SOA to Enterprise Architecture frameworks and models. </li></ul><ul><li>Conceive a common vocabulary and framework for SOA. </li></ul><ul><ul><li>Service Oriented Infrastructure </li></ul></ul><ul><ul><li>Service Oriented Architecture </li></ul></ul><ul><ul><li>Service Oriented Enterprise </li></ul></ul><ul><li>Explore the gap between where agencies are today and what the SOA vision promises for the future. </li></ul><ul><li>Provide a roadmap by Identifying groupings of discrete and concrete steps that as a group work across the gap on all three dimensions. </li></ul><ul><li>Articulate the business case drivers. </li></ul>
    20. 21. SOA Framework and Perspectives <ul><li>Service Oriented Infrastructure </li></ul><ul><ul><li>Focus is on message delivery and reliability and includes networks, ESBs and business process execution platforms. </li></ul></ul><ul><ul><li>Many standards and products are already available </li></ul></ul><ul><li>Service Oriented Architecture </li></ul><ul><ul><li>Identification and design of services, their interdependencies, and interoperability </li></ul></ul><ul><ul><li>There are many 3 rd party models, but they aren’t yet standardized. Mission drivers have government specific flavor (i.e., information sharing) </li></ul></ul><ul><li>Service Oriented Enterprise </li></ul><ul><ul><li>Includes governance, acquisition, and management issues </li></ul></ul><ul><ul><li>specifically focused on federal government environment (e.g., EA, CPIC) </li></ul></ul>
    21. 22. Open, Collaborative Effort <ul><li>Wiki site established but targeted to move to an alternative collaborative environment. The current URL is: </li></ul><ul><ul><li> </li></ul></ul><ul><li>Top-down approach </li></ul><ul><ul><ul><li>Outline </li></ul></ul></ul><ul><ul><ul><li>Key Messages </li></ul></ul></ul><ul><ul><ul><li>Text </li></ul></ul></ul><ul><li>Drafts will be posted (in process) </li></ul><ul><li>Only authoring teams can update Wiki </li></ul>
    22. 23. Agenda <ul><li>Putting SOA in Context </li></ul><ul><li>Update on “A Practical Guide to Federal SOA” </li></ul><ul><li>Looking ahead </li></ul>
    23. 24. Service and Standards Evolution Notional Service Service Specification Service Implementation Service Deployment Service Execution Standards Evolution * 1 * 1 * 1 * 1
    24. 25. UML Profile and Meta Model for Services <ul><li>OMG Object Management Group (RFP Stage) </li></ul><ul><li>A new Services Standard </li></ul><ul><ul><li>Enable interoperability and integration at the model level </li></ul></ul><ul><ul><li>At a higher-level of abstraction separate from platform variability </li></ul></ul><ul><ul><li>Address business integration and service interaction concerns at the architectural level - Architecture is the bridge between business requirements and IT solutions </li></ul></ul><ul><ul><li>Enable SOA on existing platforms through MDA </li></ul></ul><ul><ul><li>Allows for flexible platform choices </li></ul></ul><ul><ul><li>While preventing existing solutions from inhibiting platform evolution </li></ul></ul><ul><ul><li>Leverage and integrate with existing OMG standards for end-to-end lifecycle development and management </li></ul></ul><ul><li>For more information: </li></ul>
    25. 26. Service Component Architecture <ul><li>Open Service Oriented Architecture </li></ul><ul><li>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. </li></ul><ul><li>Service Component Architecture </li></ul><ul><ul><li>1. Java mappings for assembly model concepts such as &quot;component&quot; &quot;component type&quot;, “service”, &quot;reference&quot;, and &quot;property&quot; </li></ul></ul><ul><ul><li>2. Java mappings for implementing asynchronous and conversational services </li></ul></ul><ul><ul><li>3. Java mappings for specifying component lifecycle notifications </li></ul></ul><ul><ul><li>4. Java mappings for specifying service and implementation scopes </li></ul></ul><ul><li>For more information: </li></ul>
    26. 27. Summary <ul><li>The Information Technology and Telecommunications Revolution is at an inflection point </li></ul><ul><li>SOA is a transformational technology at this critical time </li></ul><ul><li>EA is a critical enabler within the federal government for achieving the business agility that SOA promises </li></ul><ul><li>This is an exciting time to be in the IT business – and federal SOA is a worthwhile endeavor </li></ul>
    27. 28. SOA in the Federal Government Update and Status Report A Practical Guide to Federal SOA Presented by Daniel Ellis ( [email_address] ) IAC Task Lead for A PG to FSOA February 27, 2007