summaryrefslogtreecommitdiffstats
path: root/eng/req/validation.rst
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2020-05-20 19:42:11 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2020-05-29 07:14:53 +0200
commit59312aa9653a9d4133209e25e21ff9724ecd476f (patch)
tree0aed3794cd2ddec18bca4fe12ab22f995326ed7b /eng/req/validation.rst
parentSpelling/Grammar Mistakes (diff)
downloadrtems-docs-59312aa9653a9d4133209e25e21ff9724ecd476f.tar.bz2
eng: Split up requirements engineering chapter
This allows to more easily generate the specification item section with a script using specification items. Update #3715.
Diffstat (limited to '')
-rw-r--r--eng/req/validation.rst46
1 files changed, 46 insertions, 0 deletions
diff --git a/eng/req/validation.rst b/eng/req/validation.rst
new file mode 100644
index 0000000..b4d4286
--- /dev/null
+++ b/eng/req/validation.rst
@@ -0,0 +1,46 @@
+.. SPDX-License-Identifier: CC-BY-SA-4.0
+
+.. Copyright (C) 2019, 2020 embedded brains GmbH (http://www.embedded-brains.de)
+
+.. _ReqEngValidation:
+
+Requirement Validation
+======================
+
+The validation of each requirement shall be accomplished by one or more of
+the following methods and nothing else:
+
+* *By test*: A :ref:`ReqEngTestCase` specification item is provided to
+ demonstrate that the requirement is satisfied when the software product is
+ executed on the target platform.
+
+* *By analysis*: A statement is provided how the requirement is met, by
+ analysing static properties of the software product.
+
+* *By inspection*: A statement is provided how the requirement is met, by
+ inspection of the :term:`source code`.
+
+* *By review of design*: A rationale is provided to demonstrate how the
+ qualification requirement is satisfied implicitly by the software design.
+
+Validation by test is strongly recommended. The choice of any other validation
+method shall be strongly justified. The requirements author is obligated to
+provide the means to validate the requirement with detailed instructions.
+
+For a specification item in a parent directory it could be checked that at
+least one item in a subdirectory has a link to it. For example a subdirectory
+could contain validation items. With this feature you could check that all
+requirements are covered by at least one validation item.
+
+The requirement validation by analysis, by inspection, and by design
+specification items shall have the following attribute specializations:
+
+type
+ The type attribute value shall be *validation-by-analysis*,
+ *validation-by-inspection*, or *validation-by-review-of-design*.
+
+link
+ There shall be exactly one link to the validated requirement.
+
+text
+ The statement or rational of the requirement validation.