Skip to content

Attifunel process req test description added #679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
attifunel wants to merge 4 commits into
base: main
Choose a base branch
from
+21 −0
Open

Attifunel process req test description added #679

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fb3d3ba
attifunel added requirement testing description
attifunel May 11, 2026
9bb64b2
attifunel improved clarification
attifunel May 11, 2026
0eeb805
attifunel added ref. to interface testing as well
attifunel May 11, 2026
859aef8
attifunel unified naming
attifunel May 11, 2026
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
21 changes: 21 additions & 0 deletions process/process_areas/verification/guidance/verification_methods.rst
View file
Open in desktop
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 on lines +185 to +186
Copy link
Copy Markdown
Member

@pahmann pahmann May 11, 2026

Choose a reason for hiding this comment

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

Suggested change
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.).
Requirements analysis is a test derivation technique where tests are designed based on the
requirements assigned to the software under test (unit, component, feature, etc.).

Copy link
Copy Markdown
Contributor Author

@attifunel attifunel May 11, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

I would still keep "SW element" as it's the most generic definition in ISO 26262 of any hierarchical piece of SW

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 on lines +190 to +194
Copy link
Copy Markdown
Member

@pahmann pahmann May 11, 2026

Choose a reason for hiding this comment

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

Suggested change
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).
Requirements should always be tested against their "nominal" behaviour: i.e. "if input
x = A, the output y of SW component Z 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).

Copy link
Copy Markdown
Contributor Author

@attifunel attifunel May 11, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

I would also change the negative case input to something different than B...


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.
Comment on lines +196 to +198
Copy link
Copy Markdown
Member

@pahmann pahmann May 11, 2026

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 •
edited
Loading

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?


.. _ver_boundary:

Boundary Values
Expand Down
Loading