Skip to content
Open
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -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.).
Comment thread
attifunel marked this conversation as resolved.
Outdated
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).
Comment thread
attifunel marked this conversation as resolved.
Outdated

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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Note that requirement-based testing derivation is typically covered by other techniques
and methods mentioned here, such as Boundary Values, Equivalence Classes, and Fuzzy Testing.

Interface testing is verification method, but according to the iso not a derivation technique. Same holds true for Fault injection.

Copy link
Copy Markdown
Contributor Author

@attifunel attifunel May 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mhmhm... I have this opinion that ISO 26262 makes a bit of mixed bag there by mixing "derivation methods" and "techniques". I wanted to stay generic speaking of "techniques" without derivation, but maybe this causes confusion?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My point of concern is where it says typically covered by do you mean it gets extended by or enhanced by? With the current wording it sounds much more like being included in the other techniques.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to "Note that requirement-based dervied test case may also cover other techniques". Agree?


.. _ver_boundary:

Boundary Values
Expand Down
Loading