Skip to content

Fix typo in verificaiton guidance #508

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

Merged
masc2023 merged 2 commits into from
Jan 14, 2026
Merged

Fix typo in verificaiton guidance #508

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
279c0a5
Fix typo in verificaiton guidance
pahmann Jan 14, 2026
c3b07cd
remove empty line
pahmann Jan 14, 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
3 changes: 1 addition & 2 deletions process/process_areas/verification/guidance/verification_guideline.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,6 @@ create test cases using the same.

Tailoring
=========

.. gd_guidl:: Verification Requirements Tailored
:id: gd_guidl__verification_req_tailored
:status: valid
Expand All @@ -161,7 +160,7 @@ Tailoring
The reasoning is:

- For SW requirement 945 & 1047 tests are executed in target environment regarding code and hardware architecture.
An integrator of the software can re-execute them on source or unmodified binary in the product environnment.
An integrator of the software can re-execute them on source or unmodified binary in the product environment.
- For SW requirement 1045 "Function and call coverage" are not considered explicitly due to lower target safety integrity level (ASIL_B).
- For SW requirement 1046 the software is not a production release, but work for the system integrator or distributor with a production release.
- For SW requirement 1141, 1143, 1144 the SW only points to AoUs, but will not be executed on the final product environment as part of the project scope.
Expand Down
Loading