From f42d40ab8a627c4514cb17a3a61e0a36dca1122b Mon Sep 17 00:00:00 2001 From: chidananda Date: Thu, 26 Feb 2026 09:49:39 +0000 Subject: [PATCH] Improvements on safety process requirements Issue#589 --- process/general_concepts/score_review_concept.rst | 8 ++++---- .../guidance/configuration_process_req.rst | 2 +- .../guidance/problem_resolution_reqs.rst | 2 +- .../guidance/safety_analysis_process_reqs.rst | 2 +- .../guidance/security_analysis_process_reqs.rst | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/process/general_concepts/score_review_concept.rst b/process/general_concepts/score_review_concept.rst index ea7887c8ff..a165b830c4 100644 --- a/process/general_concepts/score_review_concept.rst +++ b/process/general_concepts/score_review_concept.rst @@ -217,10 +217,10 @@ Process Requirements :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414, std_req__iso26262__software_942 :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch - For all the pull requests modifying a work product subject to inspection, - a template for the pull request containing the applicable checklist items shall be provided. - Ideally this is automatically applied based on the files modified in the PR. - The requirements and architecture inspections are not automatically applied. + For every pull request that modifies a work product subject to inspection, + a pull‑request template containing the applicable inspection checklist items shall be provided. + When possible, the template should be applied automatically based on the files modified in the pull request. + As of now, requirements and architecture inspection checklists shall be added manually because they are not automatically applied. .. gd_req:: Status Set Check :id: gd_req__general_status_set_check diff --git a/process/process_areas/configuration_management/guidance/configuration_process_req.rst b/process/process_areas/configuration_management/guidance/configuration_process_req.rst index f60bea17c3..6f366a26dd 100644 --- a/process/process_areas/configuration_management/guidance/configuration_process_req.rst +++ b/process/process_areas/configuration_management/guidance/configuration_process_req.rst @@ -49,7 +49,7 @@ Configuration Management Process Requirements The content of pull requests (conversation, commits, files changed) shall be stored permanently for every release. - Note: The reason is that the PRs could be altered after the release and therefore for example the inspection documented within the review would be corrupted. + Note: This requirement exists because PRs may be modified after a release, which could corrupt the documented inspection results recorded during the review. .. gd_req:: Baseline Differences :id: gd_req__config_baseline_diff diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst index a770206e02..5f4b1fdd45 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst @@ -153,7 +153,7 @@ Problem Resolution Checks It shall be checked if all mandatory attributes for each Problem is provided by the user. Following attributes shall be mandatory: - .. needtable:: Overview mandatory problem attributes + .. needtable:: Overview of mandatory problem attributes :filter: "mandatory" in tags and "attribute" and "problem_resolution" in tags and is_external == False :style: table :columns: title diff --git a/process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst b/process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst index d1b335abfa..bccc9e319e 100644 --- a/process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst +++ b/process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst @@ -81,7 +81,7 @@ Process Safety Analysis Attributes :satisfies: wf__analyse_platform_featarch, wf__analyse_featarch, wf__analyse_comparch :complies: std_req__iso26262__analysis_844, std_req__iso26262__analysis_746, std_req__iso26262__analysis_747 - If a new mitigation (e.g. prevention, detection or mitigation) is needed link to the issue and keep status invalid until mitigation is sufficient. + If a new mitigation (e.g. prevention, detection or mitigation) is needed, link to the issue and keep status invalid until mitigation is sufficient. .. gd_req:: Safety Analysis attribute: sufficient :id: gd_req__saf_attr_sufficient diff --git a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst index 6d96f451cb..194dc0c44b 100644 --- a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst +++ b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst @@ -83,7 +83,7 @@ Process Security Analysis Attributes :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: - If a new mitigation is needed link to the issue and keep status invalid until mitigation is sufficient. + If a new mitigation is needed, link to the issue and keep status invalid until mitigation is sufficient. .. gd_req:: Security Analysis attribute: sufficient :id: gd_req__sec_attr_sufficient