MSFC-PLAN-3204 REV C-2010 MARSHALL SPACE FLIGHT CENTER SOFTWARE ENGINEERING IMPROVEMENT PLAN《马歇尔航天飞行中心软件工程改善方案》.pdf

1、 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE MSFC - Form 454 (Rev. October 1992) MSFC-PLAN-3204 National Aeronautics and Revision C Space Administration EFFECTIVE DATE: 6/2/10 George C. Marshall Space Flight Center Marshall Space Flight Center, Alabama 35812 ES50 MSFC TE

2、CHNICAL STANDARD MARSHALL SPACE FLIGHT CENTER SOFTWARE ENGINEERING IMPROVEMENT PLAN Approved for Public Release; Distribution is Unlimited. . Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering

3、Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 2 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE DOCUMENT HISTORY LOG Status (Baseline/ Revision/ Canceled) Document Revision Effective Date Description Baseline 9/21/01 Baseline Release Revision

4、A 5/4/04 Update for FY04/05 Revision B 10/25/04 Editorial update to clarify requirements language in response to Headquarters Rules Review Action. Update to reflect 10/04 center reorganization. Revision C 6/2/10 Update for FY06 through FY10; General Revision Provided by IHSNot for ResaleNo reproduct

5、ion or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 3 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Table of Contents Paragraph Pa

6、ge 1. SCOPE/PURPOSE . 5 1.1. Introduction . 5 1.2. Goal 5 1.2.1. Rationale for Implementing this Plan . 5 1.2.2. Benefits . 6 1.2.3. Challenges 7 1.2.4. FY02 Accomplishments 8 1.2.5. FY03 Accomplishments 8 1.2.6. FY04/FY05 Accomplishments 9 1.2.7. FY06/FY07/FY08 Accomplishments . 10 1.2.8. FY09/FY10

7、 Objectives 10 1.3. Scope. 11 1.3.1. Organizational Elements Involved 12 1.3.2. Criteria . 12 2. APPLICABLE DOCUMENTS 12 3. DEFINITIONS/ACRONYMS . 12 3.1. Definitions 12 3.1.1. Class A: Human Rated Space Software Systems 12 3.1.2. Class B: Non-Human Space Rated Software Systems or Large Scale Aerona

8、utics Vehicles . 13 3.1.3. Class C: Mission Support Software or Aeronautic Vehicles, or Major Engineering/Research Facility software . 13 3.2. Acronyms/Abbreviations 13 4. OWNERSHIP 13 5. STRATEGIES AND OBJECTIVES . 14 5.1 Support of NASA Software Engineering Initiative Strategy 1: Implement a conti

9、nuous software process and product improvement program across NASA and its contract community 14 5.2 Support of NASA Software Engineering Initiative Strategy 2: Improve safety, reliability and quality of software products through the integration of sound software engineering principles and standards

10、 16 5.3 Support of NASA Software Engineering Initiative Strategy 3: Improve software engineering through research 17 5.4 Support of NASA Software Engineering Initiative Strategy 4: Attract and retain software engineers and improve their knowledge and skills . 18 6. SCHEDULE. 19 7. RECORDS . 20 Provi

11、ded by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 4 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFOR

12、E USE List of Tables Table No. Page Table I Software Process Improvement across MSFC and on Applicable MSFC Contracts . 14 Table II Software Metrics 16 Table III Support of NASA Software Initiative Strategy 2 . 17 Table IV Conduct Research in Software Process and Product Improvement Techniques and M

13、ethods 17 Table V Professional Development for the MSFC Software Staff 18 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 P

14、age 5 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE 1. SCOPE/PURPOSE 1.1. Introduction The purpose of this plan is to define the implementation of the Marshall Space Flight Center (MSFC) software development process improvement effort and to document MSFC support of

15、the National Aeronautics and Space Administration (NASA) Software Engineering Initiative Implementation Plan. In compliance with the NASA Engineering and Program/Project Management Policy NPD 7120.4, a major benefit that MSFC derives from the implementation of this initiative is improved software de

16、velopment and acquisition processes enabling MSFC to develop and acquire higher quality software. A major focus of this effort is to improve the processes and practices in use at MSFC by continually measuring the level of process maturity against the Software Engineering Institutes Capability Maturi

17、ty Model-Integration (CMMI) for development. In accordance with MWI 7120.4, this document adheres to the mandatory template for a MSFC Technical Standard document. Sections 1 through 3 of the center plan required content as defined in Appendix C of the NASA Software Engineering Initiative Implementa

18、tion Plan are addressed in Section 1.1, Section 1.2, and Section 1.3 of this plan, respectively. 1.2. Goal The goal of the NASA Software Engineering Initiative Implementation Plan is to “advance software engineering practices to effectively meet the scientific and technological objectives of NASA.”

19、The goal of the MSFC Software Engineering Improvement Plan is to improve the quality of software produced by MSFC, in terms of planning, implementation, testing, and support. These goals are realized by addressing the following areas: a. Improvement in software engineering processes across MSFC. b.

20、Improvement in software acquisition processes on MSFC contracts. c. Collection and use of software metrics in the management of software development projects. d. Professional development for the MSFC software engineers. e. Research in software process and product improvement techniques and methods.

21、1.2.1. Rationale for Implementing this Plan The highest priority of this plan is to improve NASAs capability to deliver safe, reliable, quality software that meets system and software requirements. Rationale for continuous software engineering improvement includes: Provided by IHSNot for ResaleNo re

22、production or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 6 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE a. Reduction in the ris

23、k of mission failure. b. Reduction in cost and schedule overruns. c. Fulfillment of mission performance requirements. d. Provision for uniform procurement policies to ensure quality of software. e. Ability to deal effectively with the growing scope and complexity of software systems. (1) Exponential

24、 growth in scope, size, and complexity of software is expected to continue. Ground and flight software represent an ever increasing share of the end-to-end system. Growth stresses our capability to manage and engineer software systems effectively. (2) Safety, quality and reliability of software syst

25、ems are at risk. 1.2.2. Benefits The primary motivation for implementing this software engineering improvement plan is to assure and improve the quality of software products developed by and/or for MSFC. The following subsections address benefits anticipated for Project Managers/Lead System Engineer

26、s/Chief Engineers, MSFC Management, and Software Engineering resulting from the improvement activities. 1.2.2.1. Project Manager/Lead System Engineer/Chief Engineer a. Identification and recommendation of key software management metrics. b. Assessment of existing software engineering processes. c. A

27、ccess to data from multiple software projects; data can be used as a method of comparison of existing project software metrics and software data. d. Provision of a common foundation and infrastructure for software process improvement across or within software development organizations. e. Improvemen

28、t of the projects ability to manage software activities. f. Reduction of defects. g. Reduction of schedule overruns and software costs. h. Reduction of software development risks. i. Improvement of software safety and mission success. j. Reduction of system integration and test risks. k. Enhancement

29、 in the ability to retain and improve software engineering skills. l. Development of procurement language and contract language to meet the NASA Software Engineering Initiative guidelines for Software Process Improvement on MSFC contracts. 1.2.2.2. MSFC Management a. All of the benefits listed above

30、 for Project Managers/Lead System Engineers/Chief Engineers. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 7 of 20 C

31、HECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE b. Provision of data on the state, status, scope, size and amount of MSFC software development projects. c. Provision of data to determine strategy and set priorities to address deficiencies. d. Review of existing technologies f

32、or incorporation into existing software processes and products. e. Identification and conduct of research in software process and product improvement techniques and methods. f. Support of the MSFC training process to annually prioritize software training needs. g. Provision of a basis for employee c

33、areer development planning. Help address retention 1.2.2.3. Software Engineering The Software Engineering Institutes Software CMMI serves as a guide for the supporting infrastructure and the standard software best practices upon which to base the improvement activities. The standard software best pr

34、actice areas in which to focus improvement activities include as appropriate: a. Requirements Management b. Requirements Development c. Project Planning d. Project Monitoring and Control e. Supplier Agreement Management f. Process and Product Quality Assurance g. Software Configuration Management h.

35、 Risk Management i. Measurement and Analysis j. Organizational Process Focus k. Organizational Process Definition l. Organizational Training m. Integrated Project Management n. Technical Solution o. Product Integration p. Verification q. Validation r. Decision Analysis and Resolution. 1.2.3. Challen

36、ges The following areas have been identified as challenges to the implementation of this software engineering process improvement plan: a. Maintaining management commitment. b. Maintaining resources and adequate skills. c. Coordinating activities across organizational elements. Provided by IHSNot fo

37、r ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 8 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE d. Organiz

38、ational acceptance of standard processes. e. Inordinate focus on achieving specific CMMI Level versus effecting true technical capability improvement. f. Determining a realistic time frame to achieve improvement goals. 1.2.4. FY02 Accomplishments The following list is a set of the primary objectives

39、 accomplished in FY02. The main objective in FY02 was to establish a baseline on which to improve. a. Surveyed the state of software at MSFC. (1) Collected data on each project and on process improvement activities. (2) Reviewed existing contracts and in-house development organizations that include

40、software development. (3) Determined deficiencies with respect to meeting the intent of the software CMM Level 2 and 3 key practice areas. (4) Identified best practices. (5) Identified formality of software Verification and Validation (V reviews activities, status, and results of the initiative; and

41、 resolves issues as necessary. The chair of the SPI Initiative Management Steering Group serves as the Center Software Engineering Process Champion. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engin

42、eering Improvement Plan MSFC-PLAN-3204 Revision: C Effective Date: 6/2/10 Page 14 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE The Software Engineering Process Group (SEPG) is comprised of members of the Flight and Ground Software Division and Safety and Mission Ass

43、urance. The chair of the SEPG serves as the SPI Initiative project lead. 5. STRATEGIES AND OBJECTIVES This section correlates the MSFC FY09/FY10 objectives and products to the Strategy Areas of the NASA Software Engineering Initiative. 5.1 Support of NASA Software Engineering Initiative Strategy 1:

44、Implement a continuous software process and product improvement program across NASA and its contract community Table I addresses Software Process Improvement across MSFC and on applicable MSFC contracts. Table II addresses software metric activities. Table I Software Process Improvement across MSFC

45、and on Applicable MSFC Contracts Initiative Responsibility Metric/Product Maintain this multi-year Center-level implementation plan for advancing software engineering practices. SPI Initiative Management Steering Group MSFC status reports on the MSFC Software Engineering Improvement Plan to the NASA

46、 Office of Chief Engineer and to the NASA Software Working Group; Revisions to MSFC-PLAN-3204. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MSFC Technical Standard OPR: ES50 MSFC Software Engineering Improvement Plan MSFC-PLAN-3204 Revision: C Eff

47、ective Date: 6/2/10 Page 15 of 20 CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE Initiative Responsibility Metric/Product Use software CMMI as a benchmark to measure process improvement within applicable software development organizations. - Conduct CMMI workshops and appra

48、isals. - Provide process training for Ares project and flight software organizations. - Maintain and improve processes and documentation for CMMI level 3 process areas. - Work with the Avionics and Software Ground Systems Test Branch toward CMMI level 2. - Conduct CMMI assessments of the Avionics and Software Ground Systems Test Branch for CMMI level 2 process areas. - Conduct CMMI assessments of the flight software branches for CMMI level 3 process areas. - Determine the progression approach toward CMMI level 4/5. - SEPG; MSFC software