Merge pull request #433 from eclipse-score/aschemmel-tech-kroehnd-safety-mgt

Safety management update - Repeat

Author: masc2023

process/folder_templates/modules/module_name/docs/manual/safety_manual.rst

@@ -66,7 +66,7 @@ List of AoUs expected from the environment the platform / module runs on:
 
 Assumptions on the User
 ^^^^^^^^^^^^^^^^^^^^^^^
-| As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform SEooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform SEooC safety case.
+| As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform SEooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform SEooC safety package.
 | Additionally the components of the platform may have additional specific assumptions how they are used. These are part of every module documentation: <link to add>. Assumptions from components to their users can be fulfilled in two ways:
 | 1. There are assumption which need to be fulfilled by all SW components, e.g. "every user of an IPC mechanism needs to make sure that he provides correct data (including appropriate ASIL level)" - in this case the AoU is marked as "platform".
 | 2. There are assumption which can be fulfilled by a safety mechanism realized by some other project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module SEooC stand-alone - in this case the AoU is marked as "module". An example would be the "JSON read" which requires "The user shall provide a string as input which is not corrupted due to HW or QM SW errors." - which is covered when using together with safe project platform persistency feature.

process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan_fdr.rst

@@ -58,7 +58,7 @@ The purpose of this safety plan formal review checklist is to report status of t
           - <Rationale for result>
 
         * - 3
-          - Does the safety plan define all needed activities for safety management (incl. Confirmation review and Safety Audit)?
+          - Does the safety plan define all needed activities for safety management (incl. formal document review and Safety Audit)?
           - [YES | NO ]
           - <Rationale for result>
 

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
+   :complies: std_req__isopas8926__44411, std_req__isopas8926__44412, 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

@@ -127,7 +127,7 @@ Attributes of Architectural Elements
    :id: gd_req__arch_attr_safety
    :status: valid
    :tags: manual_prio_1, attribute, mandatory
-   :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425
+   :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__iso26262__software_746
    :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a automotive safety integrity level (ASIL) identifier:

process/process_areas/change_management/change_management_workproducts.rst

@@ -38,6 +38,7 @@ Change Management Work Products
    | Safety anomaly: Conditions that deviate from expectations and that can lead to harm.
    | The documentation of a change request shall contain the list of changed work products,
    | the details of the change and the planned date of deployment of the change.
+   | In case a anomaly cannot be closed it shall be escalated to the :need:`Project Lead <rl__project_lead>`.
 
 .. workproduct:: Feature Request
    :id: wp__feat_request

process/process_areas/change_management/guidance/change_management_feature_template.rst

@@ -20,6 +20,6 @@ Feature Template
 .. gd_temp:: Feature Request Template
    :id: gd_temp__change_feature_request
    :status: valid
-   :complies: std_req__aspice_40__SUP-10-BP1, std_req__aspice_40__SUP-10-BP2, std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__iic-18-57, std_req__iso26262__support_8422, std_req__iso26262__support_8431, std_req__iso26262__support_8432
+   :complies: std_req__aspice_40__SUP-10-BP1, std_req__aspice_40__SUP-10-BP2, std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__iic-18-57, std_req__iso26262__support_8422, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__iso26262__management_644
 
    for the content see :need:`doc__feature_name`

process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst

@@ -20,7 +20,7 @@ Impact Analysis Template
 .. gd_temp:: Impact Analysis Template
    :id: gd_temp__change_impact_analysis
    :status: valid
-   :complies: std_req__aspice_40__SUP-10-BP2, std_req__aspice_40__iic-18-57, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__isopas8926__4462
+   :complies: std_req__aspice_40__SUP-10-BP2, std_req__aspice_40__iic-18-57, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__isopas8926__4462, std_req__iso26262__management_644, std_req__iso26262__management_6452
 
 Type of Change Request
 ----------------------

process/process_areas/implementation/guidance/software_development_template.rst

@@ -26,8 +26,8 @@ Purpose
 The main purpose of the software development plan is to define several software development related conditions:
 
 * selection of design and programming language
-* design guideline
-* coding guideline (e.g. MISRA, can also include style guide or naming convention)
+* design guideline (e.g. Enforcement of low complexity, Use of naming conventions, etc)
+* coding guideline (e.g. MISRA, can also include style guide or naming convention; Furthermore the coding guideline should respect the usual topics like Use of language subsets, Use of style guides, etc.)
 * SW configuration guideline
 * development tools
 

process/process_areas/quality_management/guidance/quality_plan_guideline.rst

@@ -20,7 +20,7 @@ Guideline Quality Management Plan
 .. gd_guidl:: Quality Management Plan Definitions Guideline
    :id: gd_guidl__qlm_plan_definitions
    :status: valid
-   :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6, std_req__aspice_40__PIM-3-BP8
+   :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6, std_req__aspice_40__PIM-3-BP8, std_req__iso26262__management_5451
 
    | **Overall quality management:**
    |

process/process_areas/quality_management/guidance/quality_plan_template.rst

@@ -20,7 +20,7 @@ Template Quality Plan
 .. gd_temp:: Quality Management Plan Template
    :id: gd_temp__qlm_plan
    :status: valid
-   :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7
+   :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP1, std_req__aspice_40__SUP-1-BP2, std_req__aspice_40__SUP-1-BP3, std_req__aspice_40__SUP-1-BP4, std_req__aspice_40__SUP-1-BP7, std_req__aspice_40__PIM-3-BP1, std_req__aspice_40__PIM-3-BP2, std_req__aspice_40__PIM-3-BP3, std_req__aspice_40__PIM-3-BP4, std_req__aspice_40__PIM-3-BP5, std_req__aspice_40__PIM-3-BP6, std_req__aspice_40__PIM-3-BP7, std_req__iso26262__management_5451
 
 :note: The quality management plan shall be continuously maintained during the project.
        Deviations to the platform plan should be documented here.