欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PDF文档下载
    分享到微信 分享到微博 分享到QQ空间

    REG NASA-LLIS-5199-2012 Lessons Learned - Requirement Decision-Making Authority.pdf

    • 资源ID:1019489       资源大小:58.19KB        全文页数:2页
    • 资源格式: PDF        下载积分:10000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要10000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    REG NASA-LLIS-5199-2012 Lessons Learned - Requirement Decision-Making Authority.pdf

    1、Public Lessons Learned Entry: 5199 Lesson Info: Lesson Number: 5199 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Requirement Decision-Making Authority Abstract: The requirements development process for the Constellation Program was unnecessarily time-consuming. If the text met th

    2、e intent of the requirement, it should not be unnecessarily rewritten. For future programs, requirements writing should be limited to a working group of key stakeholders, with the project integrator responsible for the wording. Description of Driving Event: When project integrators (PIs) were writin

    3、g requirements and verification requirements (VRs) for Ground Systems in the Constellation Program, the review teams told the PIs how to write the requirements. However, there was a lack of consistency in the direction provided by the various review team members. As a result, the requirements were n

    4、ot always agreed upon by all stakeholders. Too much rewriting led to weeks or months of unnecessary rework, at a time when the PIs needed to devote more time to technical integration. Also, PIs were required to flow down a requirement even though they believed the requirement itself was unnecessary.

    5、 In some cases, requirements were approved and then reopened for further discussion and additional rewrites at the request of a team member that had been absent during the original discussion on the disposition of the requirement. Lesson(s) Learned: The requirements development process, as implement

    6、ed, did not work well. It was not necessary to use a group forum to develop or rewrite a requirement. Too much rewriting led to a great deal of rework, making the requirements development process unnecessarily time-consuming. If the text meets the intent of the requirement, it should not be unnecess

    7、arily rewritten. Recommendation(s): 1. Create a requirements development working group for each project. Limit this group to key stakeholders, including representatives from the technical integration, development, and operations organizations. 2. Clearly define the roles and responsibilities of each

    8、 stakeholder in the requirements development process. Make project integrators responsible for the wording of the requirement and for configuration management of the requirements document. Make operations personnel responsible for ensuring that the wording meets the original intent of the requiremen

    9、t. 3. If a working group member does not agree with the requirement wording used by the project integrator, he/she may elevate the issue to a technical authority. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Provided by IHSNot for ResaleN

    10、o reproduction or networking permitted without license from IHS-,-,-Exploration Systems Additional Key Phrase(s): Program Management. Program Management.Role of civil service technical staff versus contractor staff Additional Info: Project: Constellation Approval Info: Approval Date: 2012-05-08 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-


    注意事项

    本文(REG NASA-LLIS-5199-2012 Lessons Learned - Requirement Decision-Making Authority.pdf)为本站会员(arrownail386)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

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

    收起
    展开