Skip to content

Correct Requirement check: suspicious #746

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
aschemmel-tech merged 2 commits into from
Jul 14, 2026
+4 −4
Merged

Correct Requirement check: suspicious #746

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
01de0da
Correct Requirement check: suspicious
aschemmel-tech Jul 14, 2026
79fbab0
Correct Requirement check: suspicious - fix
aschemmel-tech Jul 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
6 changes: 3 additions & 3 deletions ...s/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,13 +320,13 @@ Process Requirements Checks
.. gd_req:: Requirement check: suspicious
:id: gd_req__req_suspicious
:status: valid
:version: 2
:version: 3
:tags: prio_2_automation, check
:satisfies: wf__req_stkh_req[version==1], wf__req_feat_req[version==1], wf__req_comp_req[version==1]
:complies: std_req__iso26262__support_6425[version==1], std_req__iso26262__support_6434[version==1], std_req__aspice_40__iic-13-51[version==1]

Based on the requirement versioning it shall be checked if a parent requirement was updated but not the linked child requirements (or tests).
In case an update was detected, additionally the attribute `complete test coverage` shall be set to "No"
Based on the requirement versioning it shall be checked if a requirement was updated but not the linked tests.
In case an update was detected the attribute `complete test coverage` shall be set to "No"

Note: This refers to :need:`gd_req__req_attr_test_covered`

Expand Down
2 changes: 1 addition & 1 deletion process/process_areas/verification/verification_workflows.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -212,7 +212,7 @@ For a detailed explanation of workflows and their role within the process model,
wp__requirements_feat_aou[version==1],
wp__requirements_comp[version==1],
wp__requirements_comp_aou[version==1]
:contains: gd_req__req_attr_test_covered[version==1], gd_req__req_suspicious[version==2], gd_guidl__verification_guide[version==2]
:contains: gd_req__req_attr_test_covered[version==1], gd_req__req_suspicious[version==3], gd_guidl__verification_guide[version==2]
:has: doc_concept__verification_process[version==1], doc_getstrt__verification_process[version==1]

The requirement attribute `complete test coverage` is set to `yes` by a :need:`rl__committer` when it is verified
Expand Down
Loading