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

    REG NASA-LLIS-5197-2012 Lessons Learned - Ground Systems Requirements Development.pdf

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

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

    REG NASA-LLIS-5197-2012 Lessons Learned - Ground Systems Requirements Development.pdf

    1、Public Lessons Learned Entry: 5197 Lesson Info: Lesson Number: 5197 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Ground Systems Requirements Development Abstract: During the Constellation Program, each Ground Systems element generated its requirements independently. Differences i

    2、n the terminology used by the different elements caused problems such as the inconsistent handling of interfaces between subsystems. Description of Driving Event: During the Constellation Program, each of the Ground Systems elements generated its own requirements independently, resulting in inconsis

    3、tent practices for writing and allocating requirements. In addition, the language used in requirements documents was not consistent among subsystems, nor were the requirements flow schemas. Valuable time was spent trying to reconcile these discrepancies. The Mobile Launch Element generated its own r

    4、equirements independently, using its own terminology. This resulted in inconsistent handling of interfaces between subsystems in regard to generating, providing, or receiving data and signals. The Command, Control and Communications Element did not have a single parent requirement for some of its ma

    5、jor subsystems (i.e., multiple requirements were related to key pieces of subsystem functionality). Lesson(s) Learned: Because the engineers did not have a clear understanding of requirement derivation and flow schemas, requirement writing became a learning process rather than the systematic task it

    6、 could have been. Recommendation(s): 1. Use a centralized Systems Engineering and Integration (SE&I) organization to establish standards for requirements development, including terminology and how interface requirements are worded. 2. Establish a training regimen for requirements development. 3. Hav

    7、e SE&I participate in the approval process to ensure that the standards are followed. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Program Management. Program Management.Organizational Plannin

    8、g Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Additional Info: Project: Constellation Approval Info: Approval Date: 2012-03-29 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-


    注意事项

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




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

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

    收起
    展开