90 likes | 195 Views
PGFSOA - Purpose of the Endeavor. Background. Many initiatives in Federal agencies to explore & adopt SOA Inconsistent approaches & implementations AIC Services & Governance Subcommittees were targeting multiple documents. The Opportunity. Convergence of approaches & SOA vocabulary
E N D
PGFSOA - Purpose of the Endeavor Background • Many initiatives in Federal agencies to explore & adopt SOA • Inconsistent approaches & implementations • AIC Services & Governance Subcommittees were targeting multiple documents The Opportunity • Convergence of approaches & SOA vocabulary • Codify rationale, target, keys to implementation • Help illustrate roadmap alternatives based on current state, and sequential, practical steps that minimize risk and have tangible benefit
PGFSOA - Objectives Primary Objective 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 2007.
Governance Structure Executive Steering Committee Editorial Board Content & Revisions Darren Ash Roy Mabry Kshemendra Paul John Sullivan George Thomas AIC Subcommittee Sponsors, IAC Reorganized into four Authoring Teams aligned with document structure Coordination (Execution) Coordinator, Assistant, and Expert Advisors Coordination Authoring Roadmap to SOA (TBD, Bob Haycock) Co-Leads Tom Lucas, Raphael Malveaux SOA Target Architecture (vision) (George Thomas, Dave Mayo) Co-Leads Gary Berg-Cross*, Craig Miller* Keys to Implementation (Roy Mabry, Dan Ellis) Co-Leads Chris Gunderson, TBD Rationale for SOA (Kshemendra Paul, Bob Haycock) Co-Leads Mel Greer, Ira Sachs Unifying Examples preferably within the US Federal Government * Co-Lead Candidates – have not yet accepted the role
Team / Section Status Teams are “performing” project is “norming”
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 EPA Australian Government Information Management Office NASCIO Global Justice National Center for State Courts * Multiple representatives 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 31 team members actively authoring
PGFSOA - Schedule Calendar Year 2007 Q2 Q3 Q4 Apr May Jun Jul Aug Sep Oct Nov Dec Final Outline Key Messages for Each Section Draft Rationale Section Draft of Target Arch Section Draft Keys for Implementation Draft Roadmap Section Overlaying Examples Team Review Initial Draft Review & Update Open Comment Final
Core Ideas • Written for Chief Architects: • To inform conversations with CIOs and Program Execs • To influence architectural and investment planning • Reference established external bodies of knowledge • Focus on what is unique about the (Federal) government • Use Federal and private sector examples to anchor
PGFSOA High Level Outline • Exec Summary and Introduction • Articulate the rationale • Put forward a concrete target • Service Oriented Infrastructure • Service Oriented Architecture • Service Oriented Enterprise • Keys for Implementation – limiting factors to be addressed • Provide a roadmap with concrete actions across SOI, SOA, and SOE linked to business benefit with explicit scope
Still Open to New Participants • Others who wish to participate: • Send email to dmayo@everware-cbdi.com and mike.dunham@thcllc.com and copy dellis@everware-cbdi.com • Indicate areas of interest & expertise – which authoring team(s) or aspects of the outline can you support?