From requirements change to design change: a formal path
From requirements change to design change: a formal path
复制标题
从需求变更到设计变更：正式路径
DOI：
10.1109/sefm.2004.20
复制
发表时间：
2004
期刊：
影响因子：
--
通讯作者：
R. Dromey
中科院分区：
文献类型：
--
作者：
Lian Wen;R. Dromey
我们可以快速确定系统功能要求的变化时所寻求的理想。 （1）在哪里进行更改； （2）变化如何影响现有系统的体系结构； （3）系统的哪些组件受变化的影响； （4）并且，需要对受变化影响的组件（及其界面）进行哪些行为更改。更改问题是复杂的，因为需求更改是在问题域中指定的，而设计响应和需要进行的实现更改是在解决方案域中。要求和设计表示形式在他们为可容纳需求变化的支持方面差异很大。减少内存超负荷和与更改相关的困难的一种重要方法是使用相同的表示形式以及对更改的初始设计响应。在本文中，我们为此目的使用了称为行为树的正式组件状态表示。它允许将单个功能要求转化为相应的行为树；这些树一次组成，以创建一个集成的设计行为树（DBT）。系统中每个组件的架构，组件接口和组件行为都是DBT的新兴属性。我们通过提出一种形式的方法来扩展这种设计方法，以映射系统功能需求的更改，以更改体系结构，单个组件的行为及其接口。此类更改在受影响的设计过程的工作产品上以视觉显示。一种工具用于实施变更过程。
The ideal we seek when responding to a change in the functional requirements for a system is that we can quickly determine; (1) where to make the change; (2) how the change affects the architecture of the existing system; (3) which components of the system are affected by the change; (4) and, what behavioral changes will need to be made to the components (and their interfaces) that are affected by the change. The change problem is complicated because requirements changes are specified in the problem domain, whereas the design response and the implementation changes that need to be made are in the solution domain. Requirements and design representations vary significantly in the support they provide for accommodating requirements changes. An important way of cutting down the memory overload and difficulties associated with making changes is to use the same representation for requirements and the initial design response to the change. In this paper we use a formal component-state representation called behavior trees for this purpose. It allows individual functional requirements to be translated into their corresponding behavior trees; these trees are composed, one at a time, to create an integrated design behavior tree (DBT). The architecture, the component interfaces and the component behaviors of each component in the system are all emergent properties of the DBT. We extend this design approach, by proposing a formal method for mapping changes in a system's functional requirements, to changes in the architecture, the behavior of individual components and their interfaces. Such changes are shown visually on the work products of the design process that are affected. A tool is used to implement the change process.