diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-05-28 09:21:38 +0200 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-05-29 08:21:03 +0200 |
| commit | 23ab40d3e6899c5956c26770f07f3a5eb910be8b (patch) | |
| tree | f03dc4c0a50ae7e205b5de02da9b32c2d0d6ec30 /eng/req/validation.rst | |
| parent | eng: Split up requirements engineering chapter (diff) | |
| download | rtems-docs-23ab40d3e6899c5956c26770f07f3a5eb910be8b.tar.bz2 | |
eng: Add generated documentation of spec items
The documentation of the specification items is generated by an RTEMS
qualification tool from a specification of specification items.
Move non-generated content to "req-for-req.rst".
Update #3715.
Diffstat (limited to '')
| -rw-r--r-- | eng/req/validation.rst | 46 |
1 files changed, 0 insertions, 46 deletions
diff --git a/eng/req/validation.rst b/eng/req/validation.rst deleted file mode 100644 index b4d4286..0000000 --- a/eng/req/validation.rst +++ /dev/null @@ -1,46 +0,0 @@ -.. 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. |