首页> 外文会议>INCOSE 2009 symposium: East meets west: the human dimension to systems engineering >Global Systems Engineering at Rolls-Royce: Using Stories toExplore Ambiguous Standards and Emergent Architecture
【24h】

Global Systems Engineering at Rolls-Royce: Using Stories toExplore Ambiguous Standards and Emergent Architecture

机译:罗尔斯·罗伊斯公司的全球系统工程:利用故事探索模棱两可的标准和新兴架构

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

摘要

This paper discusses Rolls-Royce’ experience in implementing a standardized set of rolesrnand control system requirements for its product development projects. It reviews thernresponsibilities of systems and software engineers, the task of system architecture and itsrnimplications on documentation structures. Industry guidelines allow for the definition of morerndetailed item-level requirements arising from the system architecture process. However, there isrnconsiderable ambiguity in the information transfers to the component life cycle processes and therndistinction between these “item/ derived requirements” and “system requirements” in general. Arnreview of projects shows that Rolls-Royce programs have developed different approaches to thernsystem architecting process. This demonstrates the variety of interpretations for the industryrnstandards such as DO-178B and ARP-4754. It also provides a broad set of potential resourcesrnfor a globally managed development program. However, the ambiguity in the industry standardsrnmeans that the system architecting process is not always straightforward (as evidenced by itsrnvarying Rolls-Royce embodiments). The paper concludes by developing stories and use casesrnthat help to address differing cultural perspectives, and to replace existing local stories with arnnew set of stories that can be globally recognized and adopted.
机译:本文讨论了罗尔斯·罗伊斯(Rolls-Royce)在为其产品开发项目实施一套标准化的角色和控制系统要求方面的经验。它回顾了系统和软件工程师的职责,系统架构的任务及其对文档结构的影响。行业准则允许定义因系统架构过程而产生的更详细的项目级要求。但是,在向组件生命周期过程的信息传递中,以及在这些“项目/派生要求”与“系统要求”之间的区别通常存在很大的歧义。项目的Arnreview显示,罗尔斯·罗伊斯(Rolls-Royce)计划开发了不同的方法来构建系统。这证明了对工业标准(例如DO-178B和ARP-4754)的各种解释。它还为全球管理的开发计划提供了广泛的潜在资源。然而,行业标准中的歧义意味着系统架构过程并不总是那么简单(如其罗尔斯·罗伊斯实施方案的变化所证明的)。本文通过开发故事和用例来结束,这些故事和用例有助于解决不同的文化观点,并用一组新的故事替代现有的本地故事,这些故事可以被全球认可和采用。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号