1、Lessons Learned Entry: 1021Lesson Info:a71 Lesson Number: 1021a71 Lesson Date: 1997-02-01a71 Submitting Organization: HQa71 Submitted by: David M. LengyelSubject: Computer Software/Software Safety Policy Requirements/Potential Inadequacies Description of Driving Event: Potential Inadequacy of NASA A
2、gencywide Software Safety Policy RequirementsLesson(s) Learned: NASAs Agencywide software safety policy allows projects latitude to tailor their software safety plan for safety-critical software. It does not, however, require projects to obtain center Safety and Mission Assurance (S however, it is N
3、ASAs position that all software determined to be safety-critical by engineering or safety analyses need not be subjected to IV the directive requires program managers to employ IV&V, V&V, and other proven verification techniques for risk mitigation, based on cost, complexity, risk, and consequence o
4、f failure. NPG 7120.5, “NASA Program/Project Management Guide“ (currently under development), will reflect some of the requirements now found in documents that program managers may not normally review for compliance.Documents Related to Lesson: N/AMission Directorate(s): a71 Exploration Systemsa71 A
5、eronautics ResearchAdditional Key Phrase(s): a71 Aerospace Safety Advisory Panela71 Computersa71 Independent Verification and Validationa71 Policy & Planninga71 Research & Developmenta71 Safety & Mission Assurancea71 SoftwareAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2001-11-20a71 Approval Name: Bill Loewya71 Approval Organization: QSa71 Approval Phone Number: 202-358-0528Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
