NAVAIR. Software Acquisition Process Improvement. Debra Borden, NAVAIR SRC Don Beynon, SEI Gerry Imai, STSC John Kennedy, MITRE.

Transcription

1 NAVAIR Debra Borden, NAVAIR SRC Don Beynon, SEI Gerry Imai, STSC John Kennedy, MITRE Software Acquisition Process Improvement page 1

2 Report Documentation Page Form Approved OMB No Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. 1. REPORT DATE JAN REPORT TYPE 3. DATES COVERED to TITLE AND SUBTITLE Software Acquisition Process Improvement 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER 5e. TASK NUMBER 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Naval Air Systems Command,NAVAIR SRC,47123 Buse Road Bldg 2272,Patuxent River,MD, PERFORMING ORGANIZATION REPORT NUMBER 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR S ACRONYM(S) 12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited 13. SUPPLEMENTARY NOTES 14. ABSTRACT 11. SPONSOR/MONITOR S REPORT NUMBER(S) 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT a. REPORT unclassified b. ABSTRACT unclassified c. THIS PAGE unclassified Same as Report (SAR) 18. NUMBER OF PAGES 28 19a. NAME OF RESPONSIBLE PERSON Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

3 Topics Background Process Improvement Journey NAVAIR Acquisition Improvement Plan page 2

4 NAVAIR Products & Capabilities AIR ASW / ASUW SEA BASED AIRCRAFT AND SYSTEMS MARITIME WEAPONS MARINE EXPEDITIONARY AVIATION SYSTEMS OUR CORE PROCESSES WE EXECUTE (ON BEHALF OF THE USER) AIRCREW / MAINTENANCE TRAINING SYSTEMS ACQUISITION MANAGEMENT REPAIR / MODIFICATION TEST AND EVALUATION IN-SERVICE ENGINEERING AND LOGISTICS SUPPORT TECHNOLOGY, RESEARCH & DEVELOPMENT, HARDWARE & SOFTWARE PRODUCTS... MORE THAN AIRCRAFT AND WEAPONS, TOTAL SYSTEM CAPABILITY AND SUSTAINMENT

5 NAVAIR SUPPORT EQUIPMENT System Support 6% CASS ARC-210, AYK-14, GPWS, GPS, TAMMAC, TCAS, CAINS, CSFIR, ALFS, AN/ALR-76, AIM-9X, HARM AH-1W, UH-1N, UH-3H, VH-3D, CH-53E, MH-53E, MH-60, SH-60, VH-60N, H-46 Nav MPS, AV-8B MPS AVIONICS 5% WEAPONS 2% ROTARY WING AIRCRAFT 8% Activities MISSION PLANNING 4% FIXED WING AIRCRAFT 75% F/A-18 A/B,C/D,E/F, E-2C, C-2A, F-14, F-16, T45, AV-8B, V-22, EA-6, EA-6B, P-3C, S-3B, EP-3, C-130, KC-130 Over $2B on on Software Development and Related Activities Per Fiscal Year 65M SLOC Operational Software 31M SLOC Support Software Represents Approximately 50% Of NAVAIR Software page 4

6 System Environment F/A-18C/D SMUG/ RUG 14268K F/A-18E/F 17101K JSF UAVs NCW Inter-System Operability KSLOC A-4 (ARBS) 16K F-14 80K E-A6B ICAP1 48K A-7E 16K A-6E 64K EA-6B ICAP2 BLK K F/A-18C/D 2130K F-14B 364K EA-6B ICAP2 BLK K F/A-18A/B 943K AV-8B 764K F/A-18 Night Attack 3054k F/A-18C/D XN K F-14D 416K AV-8B Radar 3748K F-14B 2866K AV-8B Night EA-6B ICAP2 Attack 1780K AH-1 764K A-E SWIP 364K BLK K AH-1 NTS 1000K Aircraft IOC Year page 5

7 Setting the Stage SW BPR 1999 Software Business Process Engineering Study The compelling reason to change System Leadership Council The Enablers & Policy Makers Software Leadership Team The Facilitators & Planners NAVAIR Software Strategic Plan Software Resource Center The Coaches & Doers

8 SW-CMM LEVEL RATINGS SOFTWARE SUPPORT ACTIVITIES (29 TOTAL) 100% 95% 90% 85% 80% 75% 70% 65% 60% 55% AV-8B 22 Others AV-8B Others Level 5 Level 4 Level 3 Level 2 Level 1 50% Nov '01(approx) Nov '03 page 7

9 Team Software Process Used by organic maintenance and developer programs 11 projects ongoing 7 projects planned Resulted in improved predictability of cost, schedule and quality Four NAVAIR personnel have been trained as PSP instructors and TSP coaches page 8

10 NAVAIR MITRE SEI STSC Collaboration Integration Transition Partner MOU MITRE MOU Transition Partner page 9

11 NMSS Collaboration Objectives Support NAVAIR activities with the implementation of disciplined and rigorous software and system engineering practices. to the acquisition of software intensive systems To meet the requirements of Public Law , Section 804 Enhance and accelerate technology transition to NAVAIR organic resources Assist in the continued development of current organic acquisition process improvement capabilities and expertise Positively impact NAVAIR s ability to acquire near defect free software intensive systems on time, every time. page 10

12 The Software Engineering Institute DoD R&D laboratory FFRDC sponsored by the Undersecretary of Defense for Acquisition, Technology, and Logistics Situated as a college level unit at Carnegie Mellon University, Pittsburgh, PA Mission is to provide leadership in software engineering and to transition new software engineering technology Encouraged to support industry in pre-competitive technology R&D and in technology transition activities page 11

13 Best Practices Used Software Acquisition CMM Software Acquisition Planning Source Selection Technical Reviews Appraisals and Assessments (SCAMPI) Training Executive Overviews Model Appraisal Methodology Measurement Programs page 12

14 Best Practices Used -2 PSP/TSP CMMI S/W Architecture Pre-RFP Strategies (Documentation, Acquisition Strategy, Technical Advisors to Source Selection) page 13

15 The MITRE Corporation Operates three FFRDCs Systems engineering and integration work for Department of Defense C3I. Systems research and development work for the FAA and other civil aviation authorities. Strategic, technical and program management advice to the IRS and Treasury Department. A not-for-profit corporation combining systems engineering and information technology to address issues of critical national importance. page 14

16 Multi Mission Maritime Aircraft (MMA) Program early in the life cycle RFP development included systems & software engineering verbiage SCAMPI appraisals of contractor process capability Introduced process-based philosophy in the acquisition Prepared government integrated program team for appraisals Future architecture focus anticipated page 15

17 Software Technology Support Center (STSC) US Air Force at Ogden Air Logistics Center, Hill AFB Provides best software practice consulting services CMMI Software Acquisition Assessments Project Management Test Engineering Systems Engineering Personal Software Process (PSP) An SEI Transition Partner page 16

18 STSC NAVAIR Partnership China Lake, CA AV-8B PSP I/II for Engineers CMM Snapshot F-18 CMM Snapshot Intro to CMMI Jacksonville, FL PSP I/II for Engineers PSP/TSP for Executives/Managers page 17

19 STSC NAVAIR Partnership Orlando, FL PSP/TSP for Executives/Managers Patuxent River, MD P-3 Intro to PSP PSP I/II for Engineers PSP/TSP for Executives/Managers TSP page 18

20 STSC NAVAIR Partnership Pt. Mugu, CA F-14 Intro to PSP PSP I/II for Engineers PSP/TSP for Executives/Managers CMM snapshot San Diego, CA PSP I/II for Engineers PSP/TSP for Executives/Managers page 19

21 Lessons Learned Developer-focused SW Improvement Experiences Senior management support & involvement Set policy, vision, strategies & goals Identify measures & monitor performance Dedicated resources to execute the strategies Educating project team leaders on benefits Educating practitioners on methods Seed funding for project team SW improvement initiatives Improvement initiatives must be run like a projects page 20

22 Defense Authorization Act of Fiscal Year 2003, Section 804 A new public law Enacted by Congress December 2002 DoD guidance issued March 2003 Requires military departments and select defense agencies to establish software acquisition process improvement programs Focus is on improving how the DoD acquires software page 21

23 Required Software Acquisition Improvement Process Areas DoD s initial minimum set Acquisition planning Requirements development & management Configuration management Risk management Project management & oversight Test & evaluation Integrated team management Solicitation & source selection Performance measurement (added by NAVAIR) Processes must be documented, performed and continuously improved page 22

24 NAVAIR s 804 Implementation Phase 1 Requirements (done 12/03) A. Build an SW acquisition process improvement CoP B. Identify NAVAIR Instructions that map to 804 C. Communicate 804 requirements PEO(A) 11/17; PEO(W) 11/24; PEO /2; PEO(T) 12/5 Phase 2 Gap Analysis & Planning (mostly by 4/04) A. Revise NAVAIR Instructions as necessary B. Develop a NAVAIR Software Acquisition Process Improvement Program (SAPIP) C. Build or identify a support infrastructure Phase 3 Implementation A. PMs execute to NAVAIR Instructions page 23

25 NAVAIR Plan (Software Acquisition Process Improvement Program SAPIP) Owned by the Program Mgmt Competency Approved by the SLC (target March 04) Implemented by Assistant PEOs Supported by the SRC & Competencies SAPIP status Phase 1 of plan has been implemented Outstanding tasks: Continue orientations, define compliance measurements, execute & track progress page 24

26 Implementation Steps for NAVAIR PMs Gauge whether you comply with the updated NAVAIR Instructions Validate and document your acquisition processes Processes include entry criteria, steps, exit criteria and measurements Competencies are responsible for any additional how-to processes Develop and implement software acquisition process improvement plans and measurement programs [per NAVAIRINST & ] page 25

27 Acquisition-focused SW Improvement Hypotheses Do what makes sense for your organization (Section 804 is not prescriptive) No clear, singular improvement model for benchmarking; pick one that supports your business goals Need to emphasize and re-emphasize that Section 804 is about the acquirer Lessons learned from SW development improvement are directly applicable page 26

28 Support for Software Acquisition Process Improvement NAVAIR s Software Resource Center (SRC) will help acquisition programs to: Identify their improvement goals and performance measures Identify, document and baseline their current processes against best practices Develop a measurement program and process improvement POA&M Define their improvement program training and support needs Find resources to help satisfy those needs page 27

29 Acquisition Improvement Is Underway Within NAVAIR page 28