REG NASA-LLIS-1176--2001 Lessons Learned - Implementation of Software Standards and Processes for Building Testing and Verifying Software at NASA.pdf

1、Lessons Learned Entry: 1176Lesson Info:a71 Lesson Number: 1176a71 Lesson Date: 2001-02-01a71 Submitting Organization: HQa71 Submitted by: David M. LengyelDescription of Driving Event: Implementation of Software Standards and Processes for Building, Testing, and Verifying Software at NASALesson(s) Le

2、arned: NASA has initiated plans to have its critical systems processes evaluated according to the Capability Maturity Model (CMM) of the Software Engineering Institute and to work toward increasing the CMM level of its critical systems processes.Recommendation(s): Implement the plan and ensure that

3、all critical systems development programs comply.Evidence of Recurrence Control Effectiveness: Code AE - Concur: One of the major actions of the NASA initiative to improve the quality and reliability of software developed by or acquired by NASA, is to develop and implement a plan for all the Centers

4、 to achieve a level of capability commensurate with CMM level 3 for areas responsible for critical software development. The Office of the Chief Engineer has chartered the NASA Software Working Group, comprised of senior software experts from all the Centers to develop, facilitate, and oversee the i

5、mplementation of such a plan. The plan is scheduled for completion in FY01. We will begin implementing appropriate elements in FY01 through pilots at first, to be followed by larger scale implementation consistent with the availability of funds for such effort.Furthermore, JSC has taken the initiati

6、ve to have its critical systems processes evaluated according to the Capability Maturity Model (CMM) of the Software Engineering Institute (SEI). ISS has a plan in place for implementation of the SEI 5-level CMM model on all of its software processes and is Provided by IHSNot for ResaleNo reproducti

7、on or networking permitted without license from IHS-,-,-working closely with Boeing on this effort. The plan lays out a short-term goal of achieving a CMM level 3 and a long-term goal of level 5 on all of its critical software processes.Documents Related to Lesson: N/AMission Directorate(s): a71 Exp

8、loration Systemsa71 Space Operationsa71 Aeronautics ResearchAdditional Key Phrase(s): a71 Administration/Organizationa71 Aerospace Safety Advisory Panela71 Computersa71 Configuration Managementa71 Independent Verification and Validationa71 Information Technology/Systemsa71 Policy & Planninga71 Risk

9、Management/Assessmenta71 Softwarea71 Test & VerificationAdditional Info: Approval Info: a71 Approval Date: 2002-03-18a71 Approval Name: Bill Loewya71 Approval Organization: HQa71 Approval Phone Number: 202-358-0528Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-