REG NASA-LLIS-0921-2000 Lessons Learned Acquisition and Oversight of Contracted Software Development (1999).pdf

1、Lessons Learned Entry: 0921Lesson Info:a71 Lesson Number: 0921a71 Lesson Date: 2000-10-05a71 Submitting Organization: JPLa71 Submitted by: D. Oberhettinger/M. JahanSubject: Acquisition and Oversight of Contracted Software Development (1999) Abstract: The loss of MCO was attributed to, among other ca

2、uses, the lack of a controlled and effective process for acquisition of contractor-developed, mission critical software. NASA Centers should develop and implement acquisition plans for contractor-developed software and this should be described in each Project Implementation Plan. These plans must pr

3、ovide for Software Requirements, Software Management Planning, and Acceptance Testing and assure NASA Center verification of the adequacy of the software design approach and overall contractor implementation throughout the software life cycle.Description of Driving Event: The loss of Mars Climate Or

4、biter (MCO) was attributed to, among other causes, the lack of a controlled and effective process for acquisition of contractor-developed, mission critical software. Under the MCO procurement strategy, JPL placed full responsibility for flight software development in the hands of a contractor/indust

5、rial partner and did not monitor the quality of the contractors product. (See References 1 & 2.)Reference(s):1. “Report on Project Management in NASA by the Mars Climate Orbiter Mishap Investigation Board,“ NASA, March 13, 2000.2. Corrective Action Notice No. Z66254, MCO-JPL/SRB Finding #4.2: “Softw

6、are Development Process“3. JPL Policy: Design, Build, Assemble, and Test Process, Section 2.4: Software Acquisition, July 7, 2000.4. ”Deficiencies in Mission Critical Software Development for Mars Climate Orbiter,“ Lesson Provided by IHSNot for ResaleNo reproduction or networking permitted without l

7、icense from IHS-,-,-Learned Number 0740, April 4, 2000.Additional Key Words: Contract Monitoring, Performance Based Contracting, Software IV&V, Software Quality Assurance (SQA), Software Standards, System Contractor OversightLesson(s) Learned: Tailorable acquisition management and oversight processe

8、s for NASA contracted software development are essential to ensure that customers receive a quality product.Recommendation(s): NASA Centers should develop and implement acquisition plans for contractor-developed software. The management approach for such software acquisition should be described in e

9、ach Project Implementation Plan. These plans must provide for Software Requirements, Software Management Planning, and Acceptance Testing. Assure NASA Center verification of the adequacy of the software design approach and overall contractor implementation throughout the software life cycle.Evidence

10、 of Recurrence Control Effectiveness: A JPL Corrective Action Notice was assigned, and practices are being modified as appropriate.Documents Related to Lesson: N/AMission Directorate(s): N/AAdditional Key Phrase(s): a71 Procurement Small Business & Industrial Relationsa71 Softwarea71 Spacecrafta71 T

11、est & VerificationAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2000-11-07a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-