Automatic requirements specification update processing from a requirements management tool perspective
Automatic requirements specification update processing from a requirements management tool perspective
复制标题
从需求管理工具的角度自动进行需求规格更新处理
DOI：
10.1109/ecbs.1997.581763
复制
发表时间：
1997
期刊：
影响因子：
--
通讯作者：
L. James
中科院分区：
文献类型：
--
作者：
L. James
大多数系统工程活动最初都是从以流行的桌面出版工具格式（例如 Interleaf、Framemaker 和 Word）编写的各种客户或公司规范的早期版本或草稿版本开始的。使用更先进的需求和可追溯性管理 (RTM) 工具（直接嵌入到这些桌面发布系统中），可以将与项目相关的信息从这些文档中“捕获”到工具的需求存储库中，以用于审计跟踪、工程和可追溯性目的。通常，几个月后（经过大量的系统工程活动、需求编辑/分解/聚焦、CASE 工具建模以及通过生命周期可追溯性创建）会收到这些文档的更新副本。这会严重扰乱项目流程，因为必须以变更识别、影响分析以及迄今为止在项目数据库中进行的系统工程工作与更新文档中的最新信息之间的一致性检查的形式完成大量无效的手动返工。本文从需求和可追溯性管理工具的角度研究了自动文档更新处理所涉及的问题。尽管熟悉一般 RTM 操作哲学概念将会有所帮助，但本文并未对读者对任何特定需求管理工具的了解做出任何重大假设。
Most systems engineering activities initially start out with early or draft version of various customer or company specifications written in popular desktop publishing tool formats (e.g. Interleaf, Framemaker and Word). Using the more advanced requirements and traceability management (RTM) tools (which are embedded directly into these desktop publishing systems) information relevant to the project can then be "captured" from these documents into the tool's requirements repository for audit trail, engineering and traceability purposes. Then typically, several months later (after much systems engineering activity, requirements editing/decomposition/focusing, CASE tool modelling and through lifecycle traceability creation) updated copies of these documents are received. This then severely disrupts the flow of the project as much nugatory manual re-work has to be done in the form of change identification, impact analysis and consistency checking between the systems engineering work carried out so far in the project database and the latest information in the updated documents. The paper examines the issues involved in automatic document update processing from a requirements and traceability management tool perspective. The paper does not make any major assumptions about the reader's knowledge of any particular requirements management tool, although familiarity with general RTM operational philosophy concepts would be of benefit.