Merge pull request #470 from etas-contrib/improvement_process_linking_safety_audit_architecture

add linking to iso26262 and add requirements according to ISO

Author: masc2023

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

@@ -151,7 +151,7 @@ Checklist
         allocated to single design element, number of interfaces and operations in an interface,
         function parameters, global variables, complex types, limited comprehensibility.
 
-        Note: If the "number" above exceeds "3" a design rationale is mandatory (for all types)
+        Note: If the "number" above exceeds "3" a design rationale is mandatory (for all types).
       -
       -
       -
@@ -165,7 +165,7 @@ Checklist
     * - ARC_04_01
       - If software partitioning (different operating system processes) is used to implement freedom from interference between the processes with different rating (QM/ASIL), is effectiveness evidence generated during integration and verification tests?
 
-        Note: see ISO 26262-6, 7.4.9 and Annex D for partitioning
+        Note: see :need:`std_req__iso26262__software_749` and Annex D for partitioning
       - manual
       -
         a) the usage of shared resources (cpu time, shared memory, ...) are checked in a way that freedom from interference between the processes is ensured,
@@ -176,7 +176,16 @@ Checklist
     * - ARC_04_02
       - Is an upper estimation of the required resources (RAM, ROM, non volatile memory, communication) available and documented?
 
-        Note: see ISO 26262-6, 7.4.11
+        Note: see :need:`std_req__iso26262__software_7411`
+      - manual
+      -
+      -
+      -
+      -
+    * - ARC_04_03
+      - Are the the scheduling properties for the component defined and documented?
+
+        Note: see :need:`std_req__iso26262__software_743`
       - manual
       -
       -

process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst

@@ -145,13 +145,19 @@ Checklist
       -
       -
     * - ARC_03_03
-      - Are simplicity and avoidance of unnecessary complexity present in the software architecture?
+      - Are simplicity and avoidance of unnecessary complexity present in the software architecture and the component?
       - manual
       - Indicators for complexity are: number of use cases (corresponding to dynamic diagrams)
         allocated to single design element, number of interfaces and operations in an interface,
         function parameters, global variables, complex types, limited comprehensibility.
+        The belonging code metrics should be checked.
+
+        Notes:
+
+        If the "number" above exceeds "3" a design rationale is mandatory (for all types)
+
+        See also if component classification :need:`gd_temp__component_classification` as measure is present.
 
-        Note: If the "number" above exceeds "3" a design rationale is mandatory (for all types)
       -
       -
       -

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_744, std_req__iso26262__software_745
+   :complies: std_req__isopas8926__44411, std_req__isopas8926__44412, std_req__iso26262__software_743, 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_inspection_checklist.rst

@@ -21,7 +21,7 @@ Inspection Checklist Template
     :id: gd_chklst__arch_inspection_checklist
     :status: valid
     :tags: architecture_design
-    :complies: std_req__iso26262__software_647, std_req__iso26262__software_749, std_req__iso26262__software_7413
+    :complies: std_req__iso26262__software_647, std_req__iso26262__software_743, std_req__iso26262__software_749, std_req__iso26262__software_7413
 
     For the content see here:
 

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -33,13 +33,13 @@ Architectural Model
    :id: gd_req__arch_hierarchical_structure
    :status: valid
    :tags: done_automation
-   :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
+   :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432, std_req__iso26262__software_743
    :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    The architectural elements shall be hierarchically structured on two levels:
 
    * Feature Level (=Logical Level)
-   * Component Level
+   * Component Level (allows also recursive decomposition on lower levels)
 
 .. gd_req:: Structuring of the architectural elements
    :id: gd_req__arch_build_blocks
@@ -218,15 +218,15 @@ Checks for Architectural Design
    :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
    :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.
+   It shall be checked that valid safety architectural elements (Safety!=QM) can only be linked against valid safety architectural elements.
 
 .. gd_req:: Architecture linkage security
    :id: gd_req__arch_linkage_security_trace
    :status: valid
    :tags: prio_2_automation, attribute, check
    :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
-   It shall be checked that security relevant architectural elements (Security == YES) can only be linked against security relevant architectural elements.
+   It shall be checked that security relevant architectural elements (Security==YES) can only be linked against security relevant architectural elements.
 
 .. gd_req:: Architecture linkage requirement
    :id: gd_req__arch_linkage_requirement

process/process_areas/implementation/guidance/implementation_process_reqs.rst

@@ -327,3 +327,15 @@ Dependency Analysis
 
 .. needextend:: docname is not None and "process_areas/implementation" in docname
    :+tags: implementation
+
+
+Complexity Analyses
+'''''''''''''''''''
+
+.. gd_req:: Design Complexity Analysis
+   :id: gd_req__impl_complexity_analysis
+   :status: valid
+   :tags: prio_3_automation, model, check
+   :complies: std_req__iso26262__software_743, std_req__aspice_40__SWE-3-BP3
+
+   A complexity analysis for the components shall be performed. It shall consider appropriate code metrics like lines of code, cyclomatic complexity, number of public interfaces, number of parameters and so on. The results of the analysis shall be documented in the SW Verification Report. The project specific limits for the complexity measures shall be defined in the project guidelines.

process/process_areas/safety_management/guidance/template_component_classification.rst

@@ -18,7 +18,7 @@ Component Classification Template
 .. gd_temp:: Component Classification Template
    :id: gd_temp__component_classification
    :status: valid
-   :complies: std_req__isopas8926__441, std_req__isopas8926__4421, std_req__isopas8926__4422, std_req__isopas8926__4423, std_req__isopas8926__4424, std_req__isopas8926__4425, std_req__isopas8926__4426, std_req__isopas8926__4427, std_req__isopas8926__4428, std_req__isopas8926__4429, std_req__isopas8926__44210
+   :complies: std_req__isopas8926__441, std_req__isopas8926__4421, std_req__isopas8926__4422, std_req__isopas8926__4423, std_req__isopas8926__4424, std_req__isopas8926__4425, std_req__isopas8926__4426, std_req__isopas8926__4427, std_req__isopas8926__4428, std_req__isopas8926__4429, std_req__isopas8926__44210, std_req__iso26262__software_743
 
 
 | Classification of <component>

process/standards/aspice_40/swe/swe.3.rst

@@ -110,7 +110,7 @@ Base practices
 
       Examples for coding principles at capability level 1 are not to use implicit type conversions,
       only one entry and one exit point in subroutines, and range checks (design-by-contract, defensive
-      programming). Further examples see e.g, ISO 26262-6 clause 8.4.5 together with table 6.
+      programming). Further examples see e.g, :need:`std_req__iso26262__software_845` together with table 6.
 
 
 .. std_req:: SWE.3.BP4: Ensure consistency and establish bidirectional traceability
@@ -150,5 +150,5 @@ Base practices
    affected parties.
 
 
-.. needextend:: "c.this_doc()" 
-   :+tags: aspice40_swe3
+.. needextend:: "c.this_doc()"
+   :+tags: aspice40_swe3