从需求管理工具的角度来看,自动需求规范更新处理

L. James
{"title":"从需求管理工具的角度来看,自动需求规范更新处理","authors":"L. James","doi":"10.1109/ECBS.1997.581763","DOIUrl":null,"url":null,"abstract":"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.","PeriodicalId":240356,"journal":{"name":"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems","volume":"66 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1997-03-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":"{\"title\":\"Automatic requirements specification update processing from a requirements management tool perspective\",\"authors\":\"L. James\",\"doi\":\"10.1109/ECBS.1997.581763\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"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.\",\"PeriodicalId\":240356,\"journal\":{\"name\":\"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems\",\"volume\":\"66 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1997-03-24\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"6\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ECBS.1997.581763\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ECBS.1997.581763","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 6

摘要

大多数系统工程活动最初都是从各种客户或公司规范的早期或草案版本开始的,这些规范是用流行的桌面发布工具格式编写的(例如Interleaf、Framemaker和Word)。使用更高级的需求和可追溯性管理(RTM)工具(直接嵌入到这些桌面发布系统中),与项目相关的信息可以从这些文档中“捕获”到工具的需求存储库中,用于审计跟踪、工程和可追溯性目的。然后,典型地,几个月后(在许多系统工程活动、需求编辑/分解/聚焦、CASE工具建模和通过生命周期可追溯性创建之后),这些文档的更新副本被接收。这就严重扰乱了项目的流程,因为必须以变更识别、影响分析和一致性检查的形式进行大量无用的手工重做,这些一致性检查是迄今为止在项目数据库中执行的系统工程工作与更新文档中的最新信息之间的一致性。本文从需求和可追溯性管理工具的角度研究了自动文档更新处理中涉及的问题。本文没有对读者对任何特定需求管理工具的知识做出任何主要假设,尽管熟悉一般的RTM操作哲学概念将是有益的。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
Automatic requirements specification update processing from a requirements management tool perspective
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.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
An improved system engineering model The insides and outsides of computer-based system complexity Concepts for computer assisted engineering process management Complex systems Model driven development: integrating tools with practices
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1