ArchitecturePlusSeminar 2006 12 19Haycock

ArchitecturePlus Seminar December 19, 2006    (3CI2)

Purpose and Outcomes of Town Hall:    (3CH4)

• 1. Why we are here:    (3CH5)
  • Federal Departments are driving increasing levels of sharing, including moving towards Service Oriented Architecture-based approaches    (3CH6)
    • EA and the FEA have established the structured foundation for agencies to link their technology strategy to their business/program strategies    (3CH7)
    • EA provides the building blocks to identify key services that can be shared and increasingly identified as candidates for service oriented for reuse and leveraging    (3CH8)
    • While the technology involved is maturing nicely, there is a need to establish a best practices management framework for around governance for shared services with an emphasis on laying the groundwork to enable sharing and reuse of SOA-based services across (Government) organizational boundaries    (3CH9)
    • The business benefits for leveraging common services, service component reuse and a service orientation are substantial.    (3CHA)
  • Agency Executives, program managers, Enterprise Architects, Application Architects, and Data Architects Need SOA information and approaches to be successful    (3CHB)
    • Much vendor hype around SOA; how do we sort it out and help agencies decide how and when to move to SOA?    (3CHC)
    • How do agencies evolve effectively toward SOA using their EA?    (3CHD)
    • Can we identify pre-requisites in terms of governance processes and practices that need to be in place before it is prudent to try to deploy SOA-based applications? Can we tune this in terms of making sure to link the benefits promised in the business case with necessary operating governance?    (3CHE)
    • Agencies and their key IT players need consolidated information to help make informed decisions    (3CHF)
  • The AIC Leadership has requested a coordinated approach to addressing the challenges of SOA implementation in the Federal government.    (3CHG)
    • AIC subcommittees, the Best Practices Committee and the Industry Advisory Council (IAC) are joining together to deal with these challenges.    (3CHH)
    • The approach chosen is to develop a Practical Guide to Federal SOA Implementation as a joint effort    (3CHI)
    • A companion piece will be a composite SOA Maturity Framework that will outline the evolving stages of SOA implementation maturity tied to the key issues to be addressed that are discussed in the Practical Guide    (3CHJ)
• 2. Where have we come from and where are we going:    (3CHK)
  • Historical perspective and linkage with other EA/CIO Council efforts:    (3CHL)
    • Practical Guide to EA;    (3CHM)
    • GAO EA Assessment Guide;    (3CHN)
    • The FEA;    (3CHO)
    • Services and Component Based Architectures (SCBA) White Paper;    (3CHP)
    • OMB EA Assessment Guide;    (3CHQ)
    • Federal Transition Framework (FTF);    (3CHR)
  • What is the path forward:    (3CHS)
    • Series of Meetings on SOA this Coming Year so continue to develop understanding and guidance.    (3CHT)
    • SOA Joint Task Force to coordinate information gathering for and development of a Practical Guide for SOA Implementation.    (3CHU)
    • This is the first in a series of ArchitecturePlus meetings to help gather input to this development.    (3CHV)
    • Invite Your Suggestions for SOA Information and the Guide.    (3CHW)
    • Capture the SOA Information and Discussion in the Wiki.    (3CHX)
• 3. What are the outcomes we want to achieve:    (3CHY)
  • Development of useful information and guidance on SOA implementation that can help agency executives, CIO’s, Chief Architects, application/data/infrastructure architects.    (3CHZ)
  • Organize this information into a useful guide (A Practical Guide) that is easy to use, process oriented and helpful.    (3CI0)
  • Integrate the Practical Guide with a straightforward SOA Maturity Framework to give users a clear implementation roadmap.    (3CI1)