完全性 :: システム開発文書品質研究会

用語wiki完全性

Page Top

参考定義 anchor.png

Page Top

IEEE std 830-1998 (Complete) anchor.png

An SRS is complete if, and only if, it includes the following elements:

a) All significant requirements, whether relating to functionality, performance, design constraints, attributes, or external interfaces. In particular any external requirements imposed by a system specification should be acknowledged and treated.

b) Definition of the responses of the software to all realizable classes of input data in all realizable classes of situations. Note that it is important to specify the responses to both valid and invalid input values.

c) Full labels and references to all figures, tables, and diagrams in the SRS and definition of all terms and units of measure.

Page Top
Use of TBDs anchor.png

Any SRS that uses the phrase "to be determined" (TBD) is not a complete SRS. The TBD is, however, occasionally necessary and should be accompanied by a) A description of the conditions causing the TBD (e.g., why an answer is not known) so that the situation can be resolved; b) A description of what must be done to eliminate the TBD, who is responsible for its elimination, and by when it must be eliminated.

Page Top

IEEE std 830-1998 和訳例 anchor.png

SRSが、次をすべて含んでいること

      • すべての必要な要求
      • すべての入力データと状況に関する応答の定義
      • 用語および図表の説明

(月刊「ビジネスコミュニケーション」((株)ビジネスコミュニケーション社)の「要求工学」第3回「要求仕様」による)


Front page   Freeze Diff Backup Copy Rename Reload   New Page Page list Search Recent changes   Help   RSS of recent changes (RSS 1.0) RSS of recent changes (RSS 2.0) RSS of recent changes (RSS Atom)
Counter: 3386, today: 1, yesterday: 5
Last-modified: 2013-07-22 (Mon) 04:52:52 (JST) (2164d) by ShioyaAtsuko