Software Engineering Framing DoD s Issues Ms. Kristen Baldwin Director, Systems Analysis 15 September 2009 09/15/09 Page-1
DDR&E Organization WSARA 2009 - D,DT&E - D,SE - Dev Planning Director, Defense Research and Engineering (DDR&E) Honorable Zachary J. Lemnios Principal Deputy Mr. Alan R. Shaffer Defense Advanced Research Projects Agency (DARPA) Dr. Regina Dugan Defense Technical Information Center (DTIC) Mr. Paul Ryan Director, Research Dr. David Honey Director, Systems Engineering Mr. Stephen Welby Director, Rapid Fielding Mr. Earl Wyatt Director, Developmental Test & Evaluation (DT&E) Mr. Chris DiPetto (Acting) Principal Deputy Dr. André van Tilborg Principal Deputy Mr. Terry Jaggers Principal Deputy Mr. Ben Riley Principal Deputy Mr. Chris DiPetto 09/15/09 Page-2
NDIA Top Software Issues September 2006 1. The impact of requirements upon software is not consistently quantified and managed in development or sustainment. Requirements 2. Fundamental system engineering decisions are made without full participation of software engineering. SE/SW Integration 3. Software life-cycle planning and management by acquirers and suppliers is ineffective. Sustainment 4. The quantity and quality of software engineering expertise is insufficient to meet the demands of government and defense industry. Human Capital 5. Traditional software verification techniques are costly and ineffective for dealing with the scale and complexity of modern systems. SW Testing 6. There is a failure to assure correct, predictable, safe, secure execution of complex software in distributed environments. Assurance 7. Inadequate attention is given to total lifecycle issues for COTS/NDI impacts on lifecycle cost and risk. SW COTS / NDI / Reuse 09/15/09 Page-3
09/15/09 Page-4
Issue 6: Software Assurance Better evidence needed to make software assurance claims Testing is necessary but not sufficient Evidence is available from many sources Software engineering field suffers from pervasive lack of evidence Incidence and severity of software failures Assurance of existing software systems Efficacy of particular software development approaches 09/15/09 Page-5
NDIA Top SW Issues - 2006 vs. SW Systemic Analysis - 2008 National Defense Industrial Association (NDIA) Top 7 Software Issues August 2006 DUSD(A & T) SSE Directorate Program Review Software Systemic Analysis Findings Software Human Capital Software Human Capital Resources Quality Level Software Requirements Systems/Software Integration Software Requirements Systems/Software Integration Engineering Management Acquisition Strategy Systems of Systems Interoperability Tech Refresh Software Assurance Software Assurance Software Testing Software Sustainment Software COTS/NDI Software Development Software Metrics Software Engineering Management Knowledge Sharing Software Testing* Software Sustainment/Maintenance* Software COTS/NDI* Technology Readiness Software Architecture Software Metrics EVM Project Planning Management Oversight Software Configuration Management Process Reporting 09/15/09 Page-6
Top SW Issues Oct 2008 NDIA SE Conference Workshop ranked 18 Software / System Acquisition & Process Initiatives on Payoff v. Ease of Implementation Top Four Issues: Start-up teams and infrastructure Software T&E approaches Incorporate core SW metrics in Tech Reviews, Milestones, processes, EV SE/SW architecture review boards early engagement Changes since Oct 2008 WSARA 2009 Competitive Prototyping Starting Acquisition Pre-MS B 100% 67% Software/Systems Acquisition & Process Initiatives Start-up teams and infrastructure SW test and evaluation approaches Incorporate "core SW metrics" into milestones/reviews/processes/ev SE/SW Architecture review board with early engagement Lifecycle cost estimation for reused SW assets Synergize the "core SW metrics" broadly and effectively use information Program Management interfaces across PM/SE/SW and PM s funding/decision sources SW aspects/issues in systems-of-systems Payoff Centers-of-excellence for contracts, EV, sim Collaborative approach for SW products that cross org/pm/se/sw/hw boundaries Educate key leadership using existing SW guidebooks Contracting approach for Incremental Commitment Model for evolutionary acquisition 33% TRL concepts/measurement for SW SW programs differences/commonality Capture best-of-class SW programs Harmonize the OSD/AirForce/Army/Navy guidebooks Adoption of new commercial best practices Roles for individual SW engineers to prioritize their workloads 0% 0% 33% 67% 100% Ease 09/15/09 Page-7
Recent DDR&E / D,SE Software Maturity Efforts Renewed emphasis on systems reliability and lifecycle costs of shortfalls Consolidating SW reliability guidance Use of parametric models to project numbers of latent SW defects and discovery rates Support planning for satellite launches Aircraft production decisions Operational Test Readiness IOT&E System Testing - DT events 09/15/09 Page-8
Challenges Advance and Employ Systems Engineering Manage complexity the role of software engineering Reduce risk, measure Assurance the role of evaluation and testing Earlier engagement - Development Planning Pre-Milestone A, Pre-Acquisition Foundation for software engineering, test and evaluation DDR&E Imperative 3 Reduce the Cost, Acquisition Time, and Risk of our Major Defense Systems 09/15/09 Page-9
BACKUP 09/15/09 Page-10
New Emphasis on Development Planning and Early SE CBA ICD MDD Materiel Solution Analysis A Technology Development PDR B CDD Engineering and Manufacturing Development CDR C CPD Production and Deployment FRP DR O&S Development Planning Development DP (Early SE) DT&E SE LCS DP: Development Planning DT&E: Developmental Test and Evaluation LCS: Life Cycle Sustainment SE: System Engineering CBA: Capabilities Based Assessment CDD: Capability Development Document CPD: Capability Production Document ICD: Initial Capabilities Document MDD: Materiel Development Decision 09/15/09 Page-11
New Challenges for Programs Need for Program Office formation and PM skill-sets after MDD and prior to MS A Increased importance of the Technology Development Strategy (TDS) (as a surrogate Acquisition Strategy) at MS A Schedule and funding shifts EMD into TD Earlier engagement with industry and different contracting strategies for technology maturation, competitive prototyping, data rights, PDR before MS B, etc. Explicit need for earlier, formal SE process application (e.g., data, configuration, and risk management) 09/15/09 Page-12
09/15/09 Page-13