2: 2013-07-14 (日) 16:19:37 FujitaYutaka  |
現: 2013-07-22 (月) 05:07:08 ShioyaAtsuko |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| * 追跡性 [#m9ec0f3e] | * 追跡性 [#m9ec0f3e] | ||
| ** 参考定義 [#s2cd1e3d] | ** 参考定義 [#s2cd1e3d] | ||
| - | *** IEEE 830 (Traceable) [#d5e6496a] | + | *** IEEE std 830-1998 (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: | ||
| Line 12: | Line 12: | ||
| and maintenance phase. As code and design documents are modified, it is essential to be able to ascertain the | 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. | complete set of requirements that may be affected by those modifications. | ||
| + | |||
| + | *** IEEE std 830-1998 和訳例 [#t0938d99] | ||
| + | 要求の根拠が明確で、開発工程全体で参照できること~ | ||
| + | ([[月刊「ビジネスコミュニケーション」（(株)ビジネスコミュニケーション社）の「要求工学」第3回「要求仕様」>http://www.bcm.co.jp/site/2004/2004Dec/04-youkyuu-kougaku-12/04-youkyuu-kougaku-12.htm]]による） | ||
- 追跡性 のバックアップ一覧
- 追跡性 のバックアップ差分(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: 4903,
today: 1,
yesterday: 2