Model-based requirement generation
Model-based requirement generation
复制标题
基于模型的需求生成
DOI：
--
复制
发表时间：
2014
期刊：
影响因子：
--
通讯作者：
P. Miotto
中科院分区：
文献类型：
--
作者：
Brian London;P. Miotto
基于模型的系统工程（MBSE）旨在通过从以文档为中心的工程的范式转换来提高生产力和质量。然而，大多数MBSE开发工具需要手动创建需求构造。这个耗时的步骤很容易受到人为错误的影响，并且随着高级设计不可避免地发展，必须重复这个步骤。本文描述了一种使用SysML结构和行为图自动生成文本需求的功能。使用修改过的现成MBSE软件，信息从SysML构造（例如，块、状态、活动）中提取出来，并组合到SysML需求对象中。需求语法符合NASA和DoD标准。需求基于SysML构造关系（例如，分配、控制流、对象流），通常在图中用于描述系统架构和设计。通过嵌入式错误检查器，设计人员可以确保需求是完整和一致的。当创建新的需求构造时，自动创建对“父”SysML构造的跟踪，以捕获基本原理。随着体系结构模型的发展，需求被更新，以确保与配置管理和其他基于模型的工具的一致性。这种方法允许设计人员快速评估需求变更的影响，并减少需求管理成本。通过将模型生成的需求与传统开发的GPS接收机规范进行比较，证明了该能力。
Model-based systems engineering (MBSE) is intended to enhance productivity and quality through a paradigm shift from document-centric engineering. However, most MBSE development tools require the manual creation of requirement constructs. This time consuming step is vulnerable to human error, and must be repeated as high-level designs inevitably evolve. This paper describes a capability that uses SysML structure and behavior diagrams to automatically generate textual requirements. Using modified off-the-shelf MBSE software, information is extracted from SysML constructs (e.g., blocks, states, activities) and combined in SysML requirement objects. The requirement syntax conforms to NASA and DoD standards. Requirements are based on SysML construct relationships (e.g., allocations, control flows, object flows) commonly used in diagrams to describe system architectures and designs. Through the embedded error checker, designers can ensure that requirements are complete and consistent. When new requirement constructs are created, traceability to the “parent” SysML constructs is automatically created to capture the rationale. As the architectural models evolve, the requirements are updated to ensure consistency with configuration management and other model-based tools. Such an approach allows designers to quickly assess the impact of requirement changes and reduces requirement management costs. The capability is demonstrated by comparing model generated requirements to a traditionally developed GPS receiver specification.