1: 2013-07-14 (日) 16:06:51 FujitaYutaka |
現: 2013-07-22 (月) 04:29:49 ShioyaAtsuko |
| | | |
| ** 参考定義 [#j9f859d5] | | ** 参考定義 [#j9f859d5] |
- | *** IEEE 830 [#d0d58e48] | + | *** IEEE std 830-1998 (Consistent) [#d0d58e48] |
- | Consistency refers to internal consistency. If an SRS does not agree with some higher-level document, such as a system requirements specification, then it is not correct (see 4.3.1). | + | Consistency refers to internal consistency. If an SRS does not agree with some higher-level document, such as a system requirements specification, then it is not correct. |
| **** Internal consistency [#m8fa158f] | | **** Internal consistency [#m8fa158f] |
| An SRS is internally consistent if, and only if, no subset of individual requirements described in it conflict. | | An SRS is internally consistent if, and only if, no subset of individual requirements described in it conflict. |
| The three types of likely conflicts in an SRS are as follows: | | The three types of likely conflicts in an SRS are as follows: |
- | a) The specified characteristics of real-world objects may conflict. For example, | + | |
| + | a) The specified characteristics of real-world objects may conflict. For example,&br; |
| 1) The format of an output report may be described in one requirement as tabular but in another as | | 1) The format of an output report may be described in one requirement as tabular but in another as |
- | textual. | + | textual.&br; |
| 2) One requirement may state that all lights shall be green while another may state that all lights | | 2) One requirement may state that all lights shall be green while another may state that all lights |
| shall be blue. | | shall be blue. |
| | | |
- | b) There may be logical or temporal conflict between two specified actions. For example, | + | b) There may be logical or temporal conflict between two specified actions. For example,&br; |
- | 1) One requirement may specify that the program will add two inputs and another may specify that the program will multiply them. | + | 1) One requirement may specify that the program will add two inputs and another may specify that the program will multiply them.&br; |
| 2) One requirement may state that "A" must always follow "B," while another may require that "A and B" occur simultaneously. | | 2) One requirement may state that "A" must always follow "B," while another may require that "A and B" occur simultaneously. |
| | | |
| object. For example, a program's request for a user input may be called a "prompt" in one requirement | | object. For example, a program's request for a user input may be called a "prompt" in one requirement |
| and a "cue" in another. The use of standard terminology and definitions promotes consistency. | | and a "cue" in another. The use of standard terminology and definitions promotes consistency. |
| + | |
| + | *** IEEE std 830-1998 和訳例 [#gacfa1f5] |
| + | SRSに含まれる要求間で矛盾がないこと~ |
| + | ([[月刊「ビジネスコミュニケーション」((株)ビジネスコミュニケーション社)の「要求工学」第3回「要求仕様」>http://www.bcm.co.jp/site/2004/2004Dec/04-youkyuu-kougaku-12/04-youkyuu-kougaku-12.htm]]による) |