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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

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

REG NASA-LLIS-1504-2003 Lessons Learned - Orbital Space Plane - Technical Rigor& Integrity.pdf

1、Lessons Learned Entry: 1504Lesson Info:a71 Lesson Number: 1504a71 Lesson Date: 2003-07-01a71 Submitting Organization: MSFCa71 Submitted by: Lisa CarrSubject: Orbital Space Plane - Technical Rigor & Integrity Abstract: The Orbital Space Plane (OSP) Program technical content and review standards were

2、diluted as the program accelerated and budgets adjusted. Altered plans produce altered results. Address technical excellence and the increase in program risk when modifying the program to meet revisions to schedules and budgets. Description of Driving Event: Technical products were compromised by ab

3、andoning established processes, tools, and standards of performance.Lesson(s) Learned: The OSP Program technical content and review standards were diluted as the program accelerated and budgets adjusted. Technical products were compromised by abandoning established processes, tools, and standards of

4、 performance. The intent was to catch up later, but the bow wave was growing.Additionally: a. Milestone Review Deliverables OSP milestone review deliverables did not effectively communicate the work performed by the contractors to the reviewers. Contractor requirements traceability matrices did not

5、fully address the issues of requirement rationale and allocation. The number of documents delivered and the lack of clear organization for traceability of requirements hampered the milestone (SRR, SDR) review process.b. Life Cycle Cost (LCC) Estimate Requirements OSP requirements for LCC estimates w

6、ere not clearly defined. Contractors were asked to minimize LCC, but were constrained by a lack of Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-information on government facilities and government touch labor. Additionally, launch vehicle informati

7、on was provided at the “service” level in order to maintain dual vehicle compatibility.c. Synchronize Development Requirement development, analyses, and system design activities were not synchronized. No system design activity was integrating size, weight, volume, surface area, power, cabling, tubin

8、g, line layout, acoustic noise, induced environments, maintainability, life-cycle cost, etc.d. Review Integrity The System Requirements Review (SRR) was successfully held according to the schedule, yet a large part of the contractor submitted documentation was de-emphasized by the Program, and there

9、 was little or no feedback to the initiators on the comments and Review Item Discrepancies (RIDs) submitted on the documents that were reviewed. Only Program (government) developed documentation was reviewed for the success criteria. Recommendation(s): Altered plans produce altered results. Address

10、technical excellence and the increase in program risk when modifying the program to meet revisions to schedules and budgets. A fully defined requirements rationale table should provide information during a review to determine if the top level system design meets the system requirements. NASA should

11、specify contractor document formats such that the information will allow for a timely, efficient and thorough review process.It is apparent that the greater the schedule pressure, the more important it is to establish, follow, and enforce NASA and contractor Systems Engineering Management Plans. Pla

12、ns should be developed to catch-up to normally accepted review levels through the use of Interim Design Reviews. Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 Exploration Systemsa71 Space Operationsa71 Aeronautics ResearchAdditional Key

13、Phrase(s): Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Administration/Organizationa71 Policy & Planninga71 Program and Project ManagementAdditional Info: Approval Info: a71 Approval Date: 2005-04-01a71 Approval Name: Lisa Carra71 Approval Organization: MSFCa71 Approval Phone Number: 256-544-2544Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

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