首页> 外文会议>Systems engineering: managing complexity and change >Inside-Out Systems Architecting: An Approach to Architecting the NASA Orbital Space Plane
【24h】

Inside-Out Systems Architecting: An Approach to Architecting the NASA Orbital Space Plane

机译:由内而外的系统架构:NASA轨道空间平面架构的一种方法

获取原文
获取原文并翻译 | 示例

摘要

NASA has published the Level One requirements for the Orbital Space Planerndevelopment. Those requirements leave open opportunities for creative development of arnspacecraft that not only will provide the world with efficient travel to and from low-earth orbit,rnbut also for crew rescue capability from the International Space Station. The success of thernOrbital Space Plane development phase will depend strongly on the ability of competingrncontractors to establish criteria for gathering the needs of the stakeholders and develop modelsrnwhich are technically achievable, have acceptable risks, have acceptable costs, while adequatelyrnmeeting the NASA needs.rnThis paper proposes a hypothesis for architecting the NASA Orbital Space Plane. Beginning withrnthe level one system requirements, this approach defines a “system of systems” approach thatrnmoves from the “inside-out” in an iterative fashion. This process allows the system architect tornunderstand the out-lying systems and when/where the architecting process should stop. Systemsrnare inherently boundless and knowing also where are the client’s core needs versus what are thern“desirements”. Fundamentally, both the System Life Cycle functions (process architecting) andrnthe System Functions (product architecting) need to be addressed in this way and in an integratedrnfashion. Each system level would address both the System Life-Cycle Function as well as thernSystem Functions.
机译:美国国家航空航天局(NASA)已发布了轨道空间规划开发的一级要求。这些要求为无人飞行器的创造性发展提供了开放的机会,这不仅将为世界提供往返低地球轨道的有效旅行,而且还将为国际空间站的机组人员救援提供支持。轨道空间飞机开发阶段的成功将在很大程度上取决于竞争承包商制定标准以收集利益相关者的需求并开发模型的能力,这些模型在技术上可以实现,具有可接受的风险,具有可接受的成本,同时又能充分满足NASA的需求。构造NASA轨道空间平面的假设。从一级系统要求开始,此方法定义了一种“系统的系统”方法,该方法以迭代的方式从“由内而外”移动。该过程使系统架构师可以了解外围系统以及架构流程应在何时/何处停止。系统天生就是无穷无尽的,他们还知道客户的核心需求在哪里,而不是什么“需求”。从根本上讲,系统生命周期功能(流程架构)和系统功能(产品架构)都需要以这种方式和集成的方式解决。每个系统级别都将处理系统生命周期功能以及系统功能。

著录项

  • 来源
  • 会议地点 Toulouse(FR);Toulouse(FR);Toulouse(FR)
  • 作者

    Kevin E. Post; Cihan H. Dagli;

  • 作者单位

    3118 Ravens Lake Circle League City, Texas 77573 USA;

    Systems Engineering Graduate Program Smart Engineering Systems Laboratory 229 Engineering Management 1870 Minors Circle University of Missouri - Rolla Rolla, MO 65409-0370 USA;

  • 会议组织
  • 原文格式 PDF
  • 正文语种 eng
  • 中图分类 系统工程;自动化系统;
  • 关键词

  • 入库时间 2022-08-26 14:03:58

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号