add more links

Author: RolandJentschETAS

process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst

@@ -162,3 +162,14 @@ Checklist
       -
       -
       -
+    * - ARC_04_01
+      - If software partitioning (different operting system processes) is used to implement freedom from interference:
+        a) shared resources (cpu time, shared memory, ...) are used so that freedom from interference between the processes is ensured,
+        b) the operating system supports freedom from interference between the processes
+
+        Note: see ISO 26262-6, 7.4.9 and Annex D for partitioning
+      - manual
+      -
+      -
+      -
+      -

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -106,9 +106,9 @@ Attributes of Architectural Elements
 
    Each architectural element shall have a unique ID. It shall be in a format which is also human readable and consists of
 
-      * type of architectural element
-      * structural element (e.g. some part of the feature tree, component acronym)
-      * keyword describing the content of the architectural element
+   * type of architectural element
+   * structural element (e.g. some part of the feature tree, component acronym)
+   * keyword describing the content of the architectural element
 
    Check your project's naming conventions (should be called "doc__naming_conventions")
 
@@ -120,8 +120,8 @@ Attributes of Architectural Elements
 
    Each architectural element shall have a security relevance identifier:
 
-      * Yes
-      * No
+   * Yes
+   * No
 
 .. gd_req:: Architecture attribute: safety
    :id: gd_req__arch_attr_safety
@@ -132,8 +132,8 @@ Attributes of Architectural Elements
 
    Each architectural element shall have a automotive safety integrity level (ASIL) identifier:
 
-      * QM
-      * ASIL_B
+   * QM
+   * ASIL_B
 
 .. gd_req:: Architecture attribute: status
    :id: gd_req__arch_attr_status
@@ -144,8 +144,8 @@ Attributes of Architectural Elements
 
    Each architectural element shall have a status:
 
-      * valid
-      * invalid
+   * valid
+   * invalid
 
 Traceability to Requirements
 ----------------------------
@@ -206,7 +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
+   :complies: std_req__iso26262__software_746, 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/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, std_req__iso26262__software_748
+  :complies: std_req__iso26262__software_7411, std_req__iso26262__software_748, std_req__iso26262__software_749
 
 
 .. 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.

process/process_areas/verification/verification_workproducts.rst

@@ -34,12 +34,16 @@ Platform
 .. workproduct:: Platform Integration Test
    :id: wp__verification_platform_int_test
    :status: valid
-   :complies: std_wp__iso26262__support_952
+   :complies: std_wp__iso26262__support_952, std_req__iso26262__software_749
 
    Platform Integration Testing verifies Stakeholder Requirements performed on reference HW.
    Depending on the nature of the project, respective tailoring (e.g. for reduced requirements
    coverage) has to be reflected in the :need:`wp__verification_plan` and :need:`wp__platform_safety_plan`.
 
+   If software partitioning (operating system processes) is used to implement freedom from interference
+   effectiveness evidence shall be generated during integration and verification tests
+
+
 .. workproduct:: Platform Verification Report
    :id: wp__verification_platform_ver_report
    :status: valid
@@ -66,14 +70,17 @@ Feature
 .. workproduct:: Feature Integration test
    :id: wp__verification_feat_int_test
    :status: valid
-   :complies: std_wp__iso26262__software_1051, std_wp__iso26262__support_952
+   :complies: std_wp__iso26262__software_1051, std_wp__iso26262__support_952, std_req__iso26262__software_749
 
    Integration Testing verifies feature requirements and architecture:
 
    - all interfaces from Static view and
    - all flows from Dynamic View and
    - performance and resource consumption: i.e. RAM and processor usage
      on reference HW
+   - If software partitioning (operating system processes) is used to implement freedom from interference
+     effectiveness evidence shall be generated during integration and verification tests
+
 
 Module
 ******