Standardizing Software Development

1. Mike Nicol Air Force Aeronautical Systems Center Engineering Directorate 937-255-9566 Michael.Nicol@wpafb.af.mil Standardizing Software Development and Acquisition in DoD

2. Outline The Problem Air Force Acquisition Environment Process Improvement Looking Ahead Conclusions

3. The Problem Acquisition System Performance And Credibility Congress growing impatient with long-time 'high risk' areas of financial waste BY: STEPHEN BARR, WASHINGTON POST, 22/02/2005 The start of this year's Congress marked the 15th anniversary of the "high risk" list of federal activities. "Unfortunately," Sen. George V. Voinovich (R-Ohio) said, "this anniversary is not something worth celebrating." The list, prepared by the Government Accountability Office, points out troubled federal programs and projects that are vulnerable to waste, fraud and mismanagement. Many problem areas are complex and seem to defy remedy. But at a briefing on the list, members of Congress who deal with federal management issues signaled that there might be limits to their patience. Voinovich pointed out that six high-risk areas have been on the list from the start. "And I just think it's unacceptable . . . [Defense Department] supply chain management -- 15 years; DOD weapons system acquisition, we're talking billions and billions of dollars -- 15 years, and nothing's been done," Voinovich said.Congress growing impatient with long-time 'high risk' areas of financial waste BY: STEPHEN BARR, WASHINGTON POST, 22/02/2005 The start of this year's Congress marked the 15th anniversary of the "high risk" list of federal activities. "Unfortunately," Sen. George V. Voinovich (R-Ohio) said, "this anniversary is not something worth celebrating." The list, prepared by the Government Accountability Office, points out troubled federal programs and projects that are vulnerable to waste, fraud and mismanagement. Many problem areas are complex and seem to defy remedy. But at a briefing on the list, members of Congress who deal with federal management issues signaled that there might be limits to their patience. Voinovich pointed out that six high-risk areas have been on the list from the start. "And I just think it's unacceptable . . . [Defense Department] supply chain management -- 15 years; DOD weapons system acquisition, we're talking billions and billions of dollars -- 15 years, and nothing's been done," Voinovich said.

4. Air Force Acquisition EnvironmentEarly 90�s... DoDI 5000.2, Part 6-D, Computer Resources Computer Resources Life-Cycle Management Plan (CRLCMP), Software Metrics, Software Test Management, Ada, Software Engineering Practices Air Force Regulation (AFR) 800-14, Life Cycle Management of Computer Resources in Systems Air Force Materiel Command (AFMC) Pamphlets Software IV&V, Software Risk Abatement, Software Management Indicators, Software Quality Measurement, Software Development Capability Assessments, Etc. Air Force Acquisition Memos Software Engineering, Ada, Metrics, Software Estimating, Software Reuse, Best Practices, Use of Software Development Capability Evaluation in Source Selection, Etc. From DoD 5000.2-R; Mandatory Procedures for MDAPs and MAIS Acquisition Programs; (Includes Change 4); 11 May 1999, 4.3.5 -- Software Engineering Software shall be managed and engineered using best processes and practices that are known to reduce cost, schedule, and performance risks. It is DoD policy to design and develop software systems based on systems engineering principles (CCA to include: 1. Developing software system architectures that support open system concepts; exploit commercial off-the-shelf (COTS) computer systems products; and provide for incremental improvements based on modular, reusable, extensible software; 2. Identifying and exploiting software reuse opportunities, Government and commercial, before beginning new software development; 3. Selection of programming language in the context of the systems and software engineering factors that influence overall life-cycle costs, risks, and potential for interoperability. Additional guidance is contained in ASD(C3I) memorandum, "Use of the Ada Programming Language," April 29, 1997; 4. Use of DoD standard data. Additional guidance is contained in DoDD 8320.1; 5. Selecting contractors with the domain experience in developing comparable software systems, a successful past performance record, and a demonstrable mature software development capability and process; and 6. Use of a software measurement process in planning and tracking the software program, and to assess and improve the software development process and associated software product. 7. Ensuring that information operations risks have been assessed (DoDD S-3600.1*). 8. Ensuring software is Year-2000 compliant. * Department of Defense Directive S-3600.1, Information Operations, December 9, 1996 From DoD 5000.2-R; Mandatory Procedures for MDAPs and MAIS Acquisition Programs; (Includes Change 4); 11 May 1999, 4.3.5 -- Software Engineering Software shall be managed and engineered using best processes and practices that are known to reduce cost, schedule, and performance risks. It is DoD policy to design and develop software systems based on systems engineering principles (CCA to include: 1. Developing software system architectures that support open system concepts; exploit commercial off-the-shelf (COTS) computer systems products; and provide for incremental improvements based on modular, reusable, extensible software; 2. Identifying and exploiting software reuse opportunities, Government and commercial, before beginning new software development; 3. Selection of programming language in the context of the systems and software engineering factors that influence overall life-cycle costs, risks, and potential for interoperability. Additional guidance is contained in ASD(C3I) memorandum, "Use of the Ada Programming Language," April 29, 1997; 4. Use of DoD standard data. Additional guidance is contained in DoDD 8320.1; 5. Selecting contractors with the domain experience in developing comparable software systems, a successful past performance record, and a demonstrable mature software development capability and process; and 6. Use of a software measurement process in planning and tracking the software program, and to assess and improve the software development process and associated software product. 7. Ensuring that information operations risks have been assessed (DoDD S-3600.1*). 8. Ensuring software is Year-2000 compliant. * Department of Defense Directive S-3600.1, Information Operations, December 9, 1996

5. Air Force Acquisition EnvironmentEarly 90�s...(Cont.) Development Standards DOD-STD-2167/2168, MIL-STD-498, MIL-STD-1803 MIL-STD-882, MIL-STD-490, MIL-STD-499, DOD-STD-1521 Relatively Large Government Program Offices At Least One Senior Software Engineer Additional Software Expertise Based On Magnitude of Software Development Effort, Program Phase, Etc. Air Force Systems Acquisition School Training Computer Resources Acquisition Course (CRAC)

6. Air Force Acquisition EnvironmentLate 90�s... Limited Policy / Guidance Specific To The Acquisition Of Software Intensive Systems Almost None Of It Mandatory No Standard Way Of Doing Business Decreasing Oversight / Insight Process Focus At Odds With Demands For Reduced Cycle Time Aging and Diminishing Workforce ASC Experienced 10 Year Gap For New Hires Acquisition Workforce Still Being Downsized Training Available Through DoD Courses Limited Exposure?

7. Air Force Acquisition EnvironmentNow... Agile Acquisition Focus Decrease Acquisition Cycle Time Increase Credibility In Execution Recognition of Systems Engineering Challenges Commitment To Disciplined Application of Capable Processes For software, this translates to�

8. Process ImprovementHelp from Congress National Defense Authorization Act for Fiscal Year 2003, Section 804, Improvement Of Software Acquisition Processes

9. Process ImprovementAir Force Response Air Force Software Intensive Systems Strategic Improvement Program (AFSSIP)

10. Air Force Policy

11. AFSSIP Core Metrics

12. High Payoff Focus Areas High Confidence Estimates Difficult To Accomplish Answer Is Often Difficult To Accept Realistic Program Baselines Program Should Be Funded And Scheduled At 80-90% Confidence Can Manage More Aggressively Manage Overall Expectations High confidence estimates The estimate is based upon well defined, stable requirements The estimate accounts for the confidence to accurately estimate software size The estimate is based on realistic productivity rates The estimate includes appropriate factors for software reuse, software size growth during development, etc. The estimate is developed within the framework of a detailed, comprehensive, and realistic software development schedule Actual cost, productivity, software size, etc. data is available on the same program or an analogous program at same contractor facility The estimating techniques used are appropriate to the program situation and comprehensiveness of available data The estimate has been independently reviewed and crosschecked at the aggregate level High confidence estimates The estimate is based upon well defined, stable requirements The estimate accounts for the confidence to accurately estimate software size The estimate is based on realistic productivity rates The estimate includes appropriate factors for software reuse, software size growth during development, etc. The estimate is developed within the framework of a detailed, comprehensive, and realistic software development schedule Actual cost, productivity, software size, etc. data is available on the same program or an analogous program at same contractor facility The estimating techniques used are appropriate to the program situation and comprehensiveness of available data The estimate has been independently reviewed and crosschecked at the aggregate level

13. Looking Ahead Software Development Standard? Collaboration With Other Services And DoD Agencies Common Policy, Guidance, Standards, Training Collaboration With Industry Contribute To Development Of Improvement Products Partner In Application

14. Conclusions We Can Speed Capability Delivery Do It Right The First Time We Must Improve Credibility Set Up Executable Acquisition Programs Standardized Software Management Approaches, Properly Implemented, Are A Key Part Of The Solution