REG NASA-LLIS-5203-2011 Lessons Learned Design Verification Development.pdf

《REG NASA-LLIS-5203-2011 Lessons Learned Design Verification Development.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-5203-2011 Lessons Learned Design Verification Development.pdf（2页珍藏版）》请在麦多课文档分享上搜索。

1、Public Lessons Learned Entry: 5203 Lesson Info: Lesson Number: 5203 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Design Verification Development Abstract: Design verification methods chosen early in a programs life cycle allow the group responsible for implementing those methods

2、to contribute to the selection process. Description of Driving Event: As part of the development of requirements for the Constellation Program, methods were also developed to verify that those requirements were met. Verification methods were assigned early in the project life cycle; and for the most

3、 part, they were determined by teams or individuals who were not part of the design or implementation team. Later, when these methods were addressed by the engineers responsible for implementing the subsystem design, those engineers preferred different methods or found the ones originally assigned t

4、o be impractical. Lesson(s) Learned: When selecting a design verification method, the group responsible for implementing the design should weigh in on the practicality of the proposed method. The likelihood of success will be slim if the wrong method is forced upon the implementing organization. All

5、 stakeholders should have a vote in determining the verification method used. This can be done by allowing the stakeholders to participate throughout the design life cycle (at design reviews, etc.). Recommendation(s): Include all stakeholders (customers, operations, design/implementing organization,

6、 and users) in the initial selection of the verification method. Throughout the design life cycle, reevaluate the methods originally selected to confirm they remain valid as the design matures. By formally addressing verification methods at each design review, the implementing organization will ensu

7、re it can execute the chosen methods. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Program Management. Additional Categories.Test & Verification Integration and Testing Provided by IHSNot for

8、ResaleNo reproduction or networking permitted without license from IHS-,-,-Program Management.Communications between different offices and contractor personnel Additional Info: Project: Constellation Approval Info: Approval Date: 2011-10-20 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-