Process requirements alignment - review fixes

Ref: Resolves: #98

Author: aschemmel-tech

process/general_concepts/score_review_concept.rst

@@ -160,8 +160,10 @@ Process Requirements
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
    :satisfies: wf__monitor_verify_requirements
 
-   The version of a requirement shall not change by an inspection. In case the status of the
-   requirement is used to notify if a requirement is inspected (or another attribute is introduced),
+   The version of a requirement shall not change by an inspection.
+
+   This means: In case the status of the requirement (see :need:`gd_req__req__attr_status`)
+   is used to notify if a requirement is inspected (or another attribute is introduced),
    this shall be ignored for versioning.
 
 .. gd_req:: Version for inspected architecture
@@ -171,9 +173,13 @@ Process Requirements
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
    :satisfies: wf__mr_vy_arch
 
-   The version of architecture element shall not change by an inspection. In case the status of the
-   element is used to notify if it is inspected (or another attribute is introduced),
-   this shall be ignored for versioning. (Note: this applies only if architecture also has a version.)
+   The version of architecture element shall not change by an inspection.
+
+   This means: In case the status of the element (see :need:`gd_req__arch__attr_status`)
+   is used to notify if it is inspected (or another attribute is introduced),
+   this shall be ignored for versioning.
+
+   Note: this applies only if architecture also has a version.
 
 .. gd_req:: Checklist templates in pull requests
    :id: gd_req__general__checklist_templates
@@ -187,11 +193,20 @@ Process Requirements
    Ideally this is automatically applied based on the files modified in the PR.
    The requirements and architecture inspections are not automatically applied.
 
-.. gd_req:: Status Check
-   :id: gd_req__general__status_check
+.. gd_req:: Status Set Check
+   :id: gd_req__general__status_set_check
    :status: valid
    :tags: prio_2_automation, general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
    :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
 
    It shall be checked that only a PR with the inspection checklist filled out can set a status to valid(inspected).
+
+.. gd_req:: Status Reset Check
+   :id: gd_req__general__status_reset_check
+   :status: valid
+   :tags: prio_2_automation, general
+   :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
+   :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
+
+   It shall be checked that the status is reset to valid whenever a requirement is modified (changes version).

process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst

@@ -234,6 +234,8 @@ Process Requirements Checks
    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, the attribute requirement (or test) covered shall be set to "No"
 
+   Note: This refers to :need:`gd_req__req__attr_req_cov` and :need:`gd_req__req__attr_test_covered`
+
 .. gd_req:: Requirements mandatory attributes provided
    :id: gd_req__req__attr_mandatory
    :status: valid
@@ -284,7 +286,14 @@ Process Requirements Checks
 
    It shall be checked if every feature- and component requirement is linked at least to one valid architectural element on the same level.
 
-   Note: This check should only be enabled for a release build, otherwise it would block creating requirements first without architecture.
+.. gd_req:: Requirements linkage architecture switch
+   :id: gd_req__req__linkage_architecture_switch
+   :status: valid
+   :tags: prio_2_automation, attribute, check
+   :complies: std_req__iso26262__support_6423
+   :satisfies: wf__req__feat_req, wf__req__comp_req
+
+   The check :need:`gd_req__req__linkage_architecture` shall only be enabled for a release build, otherwise it would block creating requirements first without architecture.
 
 .. gd_req:: Requirements linkage safety
    :id: gd_req__req__linkage_safety
@@ -293,7 +302,7 @@ Process Requirements Checks
    :satisfies: wf__req__stkh_req, wf__req__feat_req, wf__req__comp_req
    :complies: std_req__iso26262__support_6422
 
-   It shall be checked that (child) QM requirements (Safety = QM) can not be linked against a (parent) safety requirement (Safety != QM).
+   It shall be checked that (child) QM requirements (Safety == QM) can not be linked against a (parent) safety requirement (Safety != QM).
 
    Note: This ensures that safety requirements are properly derived into their children. Also a mix of safe and QM aspects in a parent is avoided by this.
 

process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst

@@ -68,7 +68,7 @@ Process Safety Analysis Attributes
    :complies: std_req__iso26262__analysis_844, std_req__iso26262__analysis_746, std_req__iso26262__analysis_747
 
    Each violation shall have an associated mitigation. The mitigation may be a requirement or a brief description of the mitigation.
-   Use "None" if a mitigation has not yet been implemented, and update it once completed.
+   If mitigation has not yet been implemented, do not use this option.
 
 .. gd_req:: Safety Analysis attribute: mitigation issue
    :id: gd_req__saf__attr_mitigation_issue