1: 2013-07-14 (日) 16:15:34 FujitaYutaka  |
現: 2013-07-22 (月) 04:59:31 ShioyaAtsuko |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| * 検証容易性 [#x35c4ee0] | * 検証容易性 [#x35c4ee0] | ||
| ** 参考定義 [#zb81fd14] | ** 参考定義 [#zb81fd14] | ||
| - | *** IEEE 830 [#nfe6681e] | + | *** IEEE std 830-1998 (Verifiable)[#nfe6681e] |
| An SRS is verifiable if, and only if, every requirement stated therein is verifiable. A requirement is verifiable if, and only if, there exists some finite cost-effective process with which a person or machine can check that the software product meets the requirement. In general any ambiguous requirement is not verifiable. | An SRS is verifiable if, and only if, every requirement stated therein is verifiable. A requirement is verifiable if, and only if, there exists some finite cost-effective process with which a person or machine can check that the software product meets the requirement. In general any ambiguous requirement is not verifiable. | ||
| + | |||
| Nonverifiable requirements include statements such as "works well," "good human interface," and "shall usually happen." These requirements cannot be verified because it is impossible to define the terms "good," "well," or "usually." The statement that "the program shall never enter an infinite loop" is nonverifiable because the testing of this quality is theoretically impossible. | Nonverifiable requirements include statements such as "works well," "good human interface," and "shall usually happen." These requirements cannot be verified because it is impossible to define the terms "good," "well," or "usually." The statement that "the program shall never enter an infinite loop" is nonverifiable because the testing of this quality is theoretically impossible. | ||
| + | |||
| An example of a verifiable statement is | An example of a verifiable statement is | ||
| Output of the program shall be produced within 20 s of event x 60% of the time; and shall be produced within 30 s of event x 100% of the time. | Output of the program shall be produced within 20 s of event x 60% of the time; and shall be produced within 30 s of event x 100% of the time. | ||
| Line 10: | Line 12: | ||
| If a method cannot be devised to determine whether the software meets a particular requirement, then that | If a method cannot be devised to determine whether the software meets a particular requirement, then that | ||
| requirement should be removed or revised. | requirement should be removed or revised. | ||
| + | |||
| + | *** IEEE std 830-1998 和訳例 [#c159919e] | ||
| + | SRSに含まれるすべての要求に対して有限のコストで評価可能な手続きが存在して検証できること~ | ||
| + | ([[月刊「ビジネスコミュニケーション」（(株)ビジネスコミュニケーション社）の「要求工学」第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:15:34 FujitaYutaka
- 2: 2013-07-14 (日) 16:20:39 FujitaYutaka
Counter: 4229,
today: 3,
yesterday: 0