ImageVerifierCode 换一换
格式:PDF , 页数:4 ,大小:17.48KB ,
资源ID:1018304      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-1018304.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(REG NASA-LLIS-0657-2000 Lessons Learned Critical Design Review for Unmanned Missions.pdf)为本站会员(appealoxygen216)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

REG NASA-LLIS-0657-2000 Lessons Learned Critical Design Review for Unmanned Missions.pdf

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-03-03a71 Center Point of Contact: JPLa71 Submitted by: Wil HarkinsSubject: Critical Design Review for Unmanned Missions Practice: Practice: Conduct a formal Critical Design Review (CDR) of hardware, software, and firmware at

2、the subsystem and system levels. Schedule the review prior to the start of subsystem fabrication and assembly to assure that the design solutions satisfy the performance requirements established in the development specifications. Establish this review as a standard reliability engineering practice f

3、or flight hardware.Abstract: Preferred Practice for Design from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.Benefits:The Critical Design Review (CDR) provides increased assurance that the proposed design, and the planned manufacturing and test methods an

4、d procedures, will result in an acceptable product, with minimal project risk.Implementation Method:ResponsibilitiesThe responsible project or task manager defines the need to conduct a formal review and initiates action by contacting the convening authority (generally, the next higher management le

5、vel). The convening authority, in consultation with the responsible manager, appoints the review board and a chair and defines the board charter and schedule.The CDR ensures that all design considerations have been adequately incorporated and that all engineering analyses have been completed. Result

6、s of engineering model tests are presented to demonstrate that the hardware and software can be built to perform as planned. In addition, plans are presented for fabrication and testing, including qualification and acceptance.The review board, under direction of the chair, conducts the review and pr

7、epares a written report to the responsible manager on the findings and recommendations. The responsible manager then prepares a written response to the convening authority addressing the disposition of the review board findings and recommendations. The convening authority reviews and approves these

8、dispositions.CDR AgendaThe following items and issues are addressed at the CDR, where applicable:1. Functional description and block diagram.2. Functional requirements and compliance of the design, presented in matrix format with traceability references.Provided by IHSNot for ResaleNo reproduction o

9、r networking permitted without license from IHS-,-,-3. Disposition of subassembly/subsystem Preliminary Design Review (PDR) action items.4. Compliance of the design with accuracy requirements.5. Compliance of the design with interface requirements.6. Compliance of the design with mass requirements.7

10、. Compliance of the design with power requirements.8. Compliance of the design with memory requirements.9. Compliance of the design with environmental requirements.10. Compliance of the design with project Single Point Failure (SPF) policy.11. Compliance of the design with maintainability requiremen

11、ts.12. Status and plans for electronic piece part acquisition.13. Make or buy decisions and rationale.14. Compliance with project requirements for inherited hardware and software. Consideration of inheritance review results.15. Plans for compliance with spares requirements.16. Status of plan for mee

12、ting quality assurance requirements, procedures, and workmanship standards.17. Status of plan for meeting software assurance requirements.18. Status or results of plan for meeting reliability analyses requirements.19. Status or results of plan for meeting safety analyses requirements.20. Status of p

13、lan for meeting documentation requirements.21. Status of plan for meeting support equipment requirements.22. Status or results of plan for meeting structural analysis requirements.23. Status or results of plan for meeting thermal analysis requirements.24. Fabrication, assembly, and test schedule and

14、 constraints.25. Status or results of plan for meeting calibration requirements.26. Plans for compliance with testability requirements.27. Qualification (protoflight) test requirements and implementation plans.28. Acceptance test requirements and plans.29. Manufacturing and test facility requirement

15、s, availability and acceptability. Certification status and plans.30. Hazardous operations facility requirements, availability and acceptability. Certification status and plans.31. Results of detailed peer reviews, conclusions, and implementation plans.Technical Rationale:The CDR provides for the as

16、sessment of the design and fabrication plans by a group of knowledgeable persons not directly involved in the activity being reviewed. A formal review can focus many years of experience on the subject at hand.The CDR aids the responsible manager in evaluating the quality of the work and in making im

17、portant decisions, including those concerning completion of critical milestones and resolution of identified issues. The review process should aid in the identification of problems and the evaluation of design Provided by IHSNot for ResaleNo reproduction or networking permitted without license from

18、IHS-,-,-approaches and options.Related Practices:1. Preliminary Design Review, Reliability Preferred Practice No. PD-ED-1215.1.2. Subsystem Inheritance Review, Reliability Preferred Practice No. PD-ED-1262.3. Common Review Methods for Engineering Products, Reliability Preferred Practice No. PD-ED-12

19、15.4References:1. JPL Standard Practice Instruction (SPI) 4-16-1.2. Guidelines for Planning and Conducting Formal Reviews, Jet Propulsion Laboratory document JPL D-10401 (Office of Engineering and Mission Assurance).3. Technical Reviews and Audits for Systems, Equipment and Computer Software, MIL-ST

20、D-1521 (USAF).Impact of Non-Practice: Impact of Non-Practice: In the absence of a CDR, potential problems with adverse impacts on the subsystem, system, or project may not be identified in a timely manner. This oversight may later result in a condition having a significant effect on quality, reliabi

21、lity, capability, schedule, or cost.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-03-03a71 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-,-,-

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1