diff --git a/process/process_areas/verification/guidance/verification_methods.rst b/process/process_areas/verification/guidance/verification_methods.rst
index 221ba97bac..54a65f148e 100644
--- a/process/process_areas/verification/guidance/verification_methods.rst
+++ b/process/process_areas/verification/guidance/verification_methods.rst
@@ -172,10 +172,31 @@ Derivation Techniques
 
    Following derivation techniques are explained
 
+   * :ref:`Requirements analysis <ver_req_anal>`
    * :ref:`Boundary Values <ver_boundary>`
    * :ref:`Equivalence Classes <ver_equivalence>`
    * :ref:`Fuzzy Testing <ver_fuzzy>`
 
+.. _ver_req_anal:
+
+Requirements analysis
+"""""""""""""""""""""
+
+Requirements analysis is a testing technique where tests are designed based on the
+requirements assigned to the software element under test (component, module, unit etc.).
+If available, the verification method defined for each requirement should be used as
+the basis of the test cases design.
+
+Requirements should always be tested  against their "nominal" behaviour: i.e. "if input
+x = A, the output y of SW component X shall be equal to b". This leads to a test case
+injection value x = A and verifying that output y = B. "Negative" testing technique should
+be also considered: i.e. testing what happens when input x = B (if not already specified
+in other requirements).
+
+Note that requirement-based testing derivation is typically covered by other techniques
+mentioned here, such as Boundary Values, Equivalence Classes, Fuzzy Testing, Interface
+Testing and Fault Injection.
+
 .. _ver_boundary:
 
 Boundary Values