[一貫性のバックアップ差分(No.2)] - 用語wiki - システム開発文書品質研究会

[ トップ ] [ 差分 | バックアップ | NOTE ] [ 新規 | 一覧 | 検索 | 最新 | ヘルプ ]

現在との差分を表示
ソースを表示
一貫性へ行く。

--- 1: 2013-07-14 (日) 16:06:51 FujitaYutaka
+++ 2: 2013-07-14 (日) 16:25:06 FujitaYutaka
@@ Line 2: / Line 2: @@
 ** 参考定義 [#j9f859d5]
-*** IEEE 830 [#d0d58e48]
+*** IEEE 830 (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]
 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:
-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;
 ) The format of an output report may be described in one requirement as tabular but in another as
-textual.
+textual.&br;
 ) One requirement may state that all lights shall be green while another may state that all lights
 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;
-) One requirement may specify that the program will add two inputs and another may specify that the program will multiply them.
+) One requirement may specify that the program will add two inputs and another may specify that the program will multiply them.&br;
 ) One requirement may state that "A" must always follow "B," while another may require that "A and B" occur simultaneously.