1: 2013-07-14 (日) 16:19:11 FujitaYutaka  |
2: 2013-07-14 (日) 16:19:37 FujitaYutaka |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| * 追跡性 [#m9ec0f3e] | * 追跡性 [#m9ec0f3e] | ||
| ** 参考定義 [#s2cd1e3d] | ** 参考定義 [#s2cd1e3d] | ||
| - | *** IEEE 830 [#d5e6496a] | + | *** IEEE 830 (Traceable) [#d5e6496a] |
| 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: | 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). | a)Backward traceability (i.e., to previous stages of development). | ||
| - | This depends upon each requirement explicitly referencing its source in earlier documents. | + | This depends upon each requirement explicitly referencing its source in earlier documents.&br; |
| b)Forward traceability (i.e., to all documents spawned by the SRS). | 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. | This depends upon each requirementin the SRS having a unique name or reference number. | ||
- 追跡性 のバックアップ一覧
- 追跡性 のバックアップ差分(No. All)
- 1: 2013-07-14 (日) 16:19:11 FujitaYutaka
- 2: 2013-07-14 (日) 16:19:37 FujitaYutaka
- 現: 2013-07-22 (月) 05:07:08 ShioyaAtsuko
Counter: 4732,
today: 2,
yesterday: 1