1 / 7

DoD Software Issues and Gap Identification

DoD Software Issues and Gap Identification. Kristen Baldwin Deputy Director, Software Engineering and System Assurance OUSD(AT&L) April 18, 2007. Published DoD Software Summit Report Held DoD Software Interchange meeting Confirmed Software Exec/Staff POCs across the DoD

mimi
Download Presentation

DoD Software Issues and Gap Identification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. DoD Software Issues and Gap Identification Kristen Baldwin Deputy Director, Software Engineering and System Assurance OUSD(AT&L) April 18, 2007

  2. Published DoD Software Summit Report Held DoD Software Interchange meeting Confirmed Software Exec/Staff POCs across the DoD Reviewed Top Software Issues Agreed to prioritize issues, identify gaps for attention Identified three communities of interest: Embedded (weapons systems) IT Business Navy Software presentation to SE Forum, Feb 07 OSD/Navy agreed to coordinate/leverage Navy and Tri-service activities Hosted software workshop, 21 March “Embedded software community” focus Reviewed ongoing initiatives, identified gaps Key Events - 2007 This briefing provides workshop summary and next steps

  3. Consolidated findings/recommendations from Top Software Issues Workshop, Program Support Reviews, and DoD Software Summit Identified 6 major focus areas Identified key recommendations for each area Developed Survey to map ongoing softwareinitiatives against the recommendations Services, MDA DCMA, SEI, L&MR, DAU, DDRE completed survey Held software working group session – 21 March 07 Reviewed Survey Results, Component Briefings Determined high level focus areas for attention (next chart) Binned activities against each area Identified areas where no activity existed (gaps) Software Issue/Gap Identification Process

  4. SW & SE Integration Software Acquisition Management Requirements – GAP SE/SW Process Int – O SW Council – N SW Dev Plan – N SW in SEP – N SW in Tech Reviews – N SW Quality Attributes - GAP Standards – O, N DAG Ch 4/7 – O, AF Prog Spt – O, All Contract Language – A, M, N SW Estimation – GAP Lifecycle Policy – AF Risk Identification - GAP Human Capital Knowledge Sharing Data and Metrics Education Sources – N, A Leadership Training – A, SEI SETA Quals – GAP SW Human Cap Strategy – GAP Industrial Base – O University Curriculum – O Worforce Survey - AF DAU Software ACC – DAU Best Practices Clearinghouse – DAU, O SW Inventory – LMR Lifecycle Guides – M, N Root Cause Analysis – O Local Knowledge Portals - N SW Metrics – A, O SW Cost – O SW EVM – DCMA SW Estimation - GAP SW Issue/GAP Workshop Findings *based on NDIA Top SW Issues, OSD Program Support Reviews, and DoD Software Summit findings Primary Software Focus Areas* Software Development Techniques Agile – O, SEI Architecture – A, SEI COTS – SEI Open Source – AF Sustainment – GAP SW Interoperability – GAP SW Test - GAP Ongoing Initiative Owners O – OSD/SSA A – Army N – Navy AF – Air Force M – MDA SEI DCMA DAU L&MR GAP – No activity Ongoing SW Initiatives (w/owners) and Gaps binned to Focus Areas

  5. Summary of Identified Software Gap Areas • Estimation • Risk Identification • Sustainment • Interoperability • Test • Requirements • Quality Attributes • SETA Qualifications • Human Capital Strategy

  6. Near Term: • Determine metrics for each of the 6 Focus Areas • Based upon source reports (ie. SW Summit, Top Issues, PSRs, Historical SW Studies) • Coordinate ongoing initiatives (via Working Group Participation, Defense Software Collaborators) • Support and/or leverage initiatives where appropriate • Provide visibility across the Department • Determine action plans for each gap based upon: • Priority • Near Term/Long Term impacts • NDIA SW Committee, others, interest in accepting gap(s) • Engage other communities and participants • IT, Business, Research • Over Time: • Reassess ongoing initiatives against focus area metrics • Determine new gaps, or additional effort required to address core issues • Reassess focus area metrics against systemic software issues • From future SW Summits, Systemic Analysis, etc… Next Steps

  7. Software Interchange Group / SE Forum Notional Oversight/Coordination MAIS & Business Work Groups System Assurance Work Group Software Work Group NDIA Software Committee Oversight/Coordination Software Acquisition Management Knowledge Sharing Human Capital Focus Areas SW & SE Integration Software Development Techniques SW Data and Metrics Integrate Across Focus Areas

More Related