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

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

--- 1: 2013-07-14 (日) 15:53:00 FujitaYutaka
+++ 2: 2013-07-14 (日) 16:24:34 FujitaYutaka
@@ Line 2: / Line 2: @@
 ** 参考定義 [#lfdc953b]
-*** IEEE830 [#f1f0c82f]
+*** IEEE830 (Correct) [#f1f0c82f]
 An SRS is correct if, and only if, every requirement stated therein is one that the software shall meet.
-There is no tool or procedure that ensures correctness. The SRS should be compared with any applicable superior speciÞcation, such as a system requirements speciÞcation, with other project documentation, and with other applicable standards, to ensure that it agrees. Alternatively the customer or user can determine if the SRS correctly reßects the actual needs. Traceability makes this procedure easier and less prone to error.
+There is no tool or procedure that ensures correctness. The SRS should be compared with any applicable superior specification, such as a system requirements specification, with other project documentation, and with other applicable standards, to ensure that it agrees. Alternatively the customer or user can determine if the SRS correctly reflects the actual needs. Traceability makes this procedure easier and less prone to error.