追跡性 :: システム開発文書品質研究会

用語wiki追跡性

Page Top

参考定義 anchor.png

Page Top

IEEE std 830-1998 (Traceable) anchor.png

An SRS is traceable if the origin of each of its requirements is clear and if it facilitates the referencing of each requirement in future development or enhancement documentation. The following two types of traceability are recommended:

a)Backward traceability (i.e., to previous stages of development). This depends upon each requirement explicitly referencing its source in earlier documents.
b)Forward traceability (i.e., to all documents spawned by the SRS). This depends upon each requirementin the SRS having a unique name or reference number.

The forward traceability of the SRS is especially important when the software product enters the operation and maintenance phase. As code and design documents are modified, it is essential to be able to ascertain the complete set of requirements that may be affected by those modifications.

Page Top

IEEE std 830-1998 和訳例 anchor.png

要求の根拠が明確で、開発工程全体で参照できること
(月刊「ビジネスコミュニケーション」((株)ビジネスコミュニケーション社)の「要求工学」第3回「要求仕様」による)


Front page   Freeze Diff Backup Copy Rename Reload   New Page Page list Search Recent changes   Help   RSS of recent changes (RSS 1.0) RSS of recent changes (RSS 2.0) RSS of recent changes (RSS Atom)
Counter: 3064, today: 1, yesterday: 0
Last-modified: 2013-07-22 (Mon) 05:07:08 (JST) (2223d) by ShioyaAtsuko