add first linkage

Author: RolandJentschETAS

process/folder_templates/features/feature_name/requirements/chklst_req_inspection.rst

@@ -94,12 +94,6 @@ Requirement Inspection Checklist
         -
         -
       * - REQ_03_01
-        - For stakeholder requirements: Is the *rationale* correct?
-        - Rationales explain why the top level requirements were created. Do those cover the requirement?
-        -
-        -
-        -
-      * - REQ_03_02
         - Is the *linkage to the parent requirement* correct?
         - Linkage to correct levels and ASIL attributes is checked automatically, but it needs checking if the child requirement implements (at least) a part of the parent requirement.
         -
@@ -142,12 +136,6 @@ Requirement Inspection Checklist
         -
         -
       * - REQ_09_01
-        - For stakeholder requirements: Do those cover assumed safety mechanisms needed by the hardware and system?
-        - Note that stakeholder requirements covering safety mechanisms come from rationales, whereas feature requirements are covering safety mechanisms coming from :need:`gd_chklst__safety_analysis`
-        -
-        -
-        -
-      * - REQ_09_02
         - Do the feature requirements defining a safety mechanism contain the error reaction leading to a safe state?
         - Alternatively to the safe state there could also be "repair" mechanisms. Also do not forget to consider REQ_05_01 for these.
         -

process/folder_templates/modules/module_name/component_name/docs/requirements/chklst_req_inspection.rst

@@ -94,12 +94,6 @@ Requirement Inspection Checklist
         -
         -
       * - REQ_03_01
-        - For stakeholder requirements: Is the *rationale* correct?
-        - Rationales explain why the top level requirements were created. Do those cover the requirement?
-        -
-        -
-        -
-      * - REQ_03_02
         - Is the *linkage to the parent feature/component requirement* correct?
         - Linkage to correct levels and ASIL attributes is checked automatically, but it needs checking if the child requirement implements (at least) a part of the parent requirement.
         -
@@ -142,12 +136,6 @@ Requirement Inspection Checklist
         -
         -
       * - REQ_09_01
-        - Note that stakeholder requirements covering safety mechanisms come from rationales, whereas component requirements are covering safety mechanisms coming from :need:`gd_chklst__safety_analysis`
-        -
-        -
-        -
-        -
-      * - REQ_09_02
         - Do the requirements that define a safety mechanism specify the error reaction leading to a safe state?
         - Alternatively to the safe state there could also be "repair" mechanisms. Also do not forget to consider REQ_05_01 for these.
         -

process/process_areas/architecture_design/guidance/architecture_guideline.rst

@@ -20,7 +20,7 @@ Architecture Guideline
 .. gd_guidl:: Architectural Design
    :id: gd_guidl__arch_design
    :status: valid
-   :complies: std_req__isopas8926__44411, std_req__isopas8926__44412, std_req__iso26262__software_745
+   :complies: std_req__isopas8926__44411, std_req__isopas8926__44412, std_req__iso26262__software_744, std_req__iso26262__software_745
 
 The guideline focuses on the steps which need to be performed in order to create the architectural design. The concept behind those steps is described in the :need:`[[title]] <doc_concept__arch_process>`.
 

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -206,6 +206,7 @@ Checks for Architectural Design
    :status: valid
    :tags: prio_1_automation, attribute, check
    :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :complies: std_req__iso26262__software_748
 
    It shall be checked that valid safety architectural elements (Safety != QM) can only be linked against valid safety architectural elements.
 

process/process_areas/architecture_design/guidance/component_architecture_template.rst

@@ -19,6 +19,6 @@ Component Architecture Template
     :id: gd_temp__arch_comp
     :status: valid
     :tags: architecture_design
-    :complies: std_req__iso26262__software_741, std_req__iso26262__software_742, std_req__iso26262__software_743
+    :complies: std_req__iso26262__software_741, std_req__iso26262__software_742, std_req__iso26262__software_743, std_req__iso26262__software_744
 
     For the content see here: :ref:`component_architecture_template`

process/process_areas/implementation/guidance/detailed_design_template.rst

@@ -19,6 +19,6 @@ Detailed Design Template
 .. gd_temp:: Detailed Design Templates
    :id: gd_temp__detailed_design
    :status: valid
-   :complies: std_req__iso26262__software_542, std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425
+   :complies: std_req__iso26262__software_542, std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__iso26262__software_744
 
    For the content see here: :ref:`component_detailed_design_template`

process/process_areas/implementation/guidance/implementation_checklist.rst

@@ -20,7 +20,7 @@ Implementation Inspection Checklist
     :id: gd_chklst__impl_inspection_checklist
     :status: valid
     :tags: implementation
-    :complies: std_req__iso26262__software_942
+    :complies: std_req__iso26262__software_942, std_req__iso26262__software_748
 
 Purpose
 -------

process/process_areas/implementation/guidance/implementation_guideline.rst

@@ -18,6 +18,7 @@ Guideline
 .. gd_guidl:: Implementation Guideline
    :id: gd_guidl__implementation
    :status: valid
+   :complies: std_req__iso26262__software_744
 
 This document describes the general guidances for implementation based on the concept which is defined :need:`[[title]]<doc_concept__imp_concept>`.
 In the concept is a example of a Detailed Design included.

process/process_areas/safety_analysis/guidance/dfa_failure_initiators.rst

@@ -20,7 +20,7 @@ DFA failure initiators
 .. gd_guidl:: DFA failure initiators
   :id: gd_guidl__dfa_failure_initiators
   :status: valid
-  :complies: std_req__iso26262__software_7411
+  :complies: std_req__iso26262__software_7411, std_req__iso26262__software_748
 
 
 .. note:: Use all applicable failure initiators to ensure a structured analysis. If there are additional failure initiators needed, please enlarge the list of fault models.