一貫性 :: システム開発文書品質研究会

用語wiki一貫性

Page Top

参考定義 anchor.png

Page Top

IEEE std 830-1998 (Consistent) anchor.png

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.

Page Top
Internal consistency anchor.png

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,
1) The format of an output report may be described in one requirement as tabular but in another as textual.
2) 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,
1) One requirement may specify that the program will add two inputs and another may specify that the program will multiply them.
2) One requirement may state that "A" must always follow "B," while another may require that "A and B" occur simultaneously.

c) Two or more requirements may describe the same real-world object but use different terms for that 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.


トップ   凍結 差分 バックアップ 複製 名前変更 リロード   ページ新規作成 全ページ一覧 単語検索 最新ページの一覧   ヘルプ   最新ページのRSS 1.0 最新ページのRSS 2.0 最新ページのRSS Atom
Counter: 2535, today: 1, yesterday: 0
Last-modified: 2013-07-22 (月) 04:29:49 (JST) (1976d) by ShioyaAtsuko