docs: create safety mgt process - finding fixes

Closes: #333
eclipse-score · Feb 14, 2025 · 55f7fcf · 55f7fcf
1 parent 10026ce
commit 55f7fcf
Show file tree

Hide file tree

Showing 10 changed files with 64 additions and 17 deletions.
diff --git a/docs/_tooling/extensions/score_metamodel/metamodel.py b/docs/_tooling/extensions/score_metamodel/metamodel.py
@@ -130,6 +130,15 @@
             ("id", "^STD_REQ__[0-9a-z_]*$"),
             ("status", "^(valid)$"),
         ],
+    },
+        {
+        "directive": "std_wp",
+        "title": "Standard Workproduct",
+        "prefix": "STD_WP__",
+        "req_opt": [
+            ("id", "^STD_WP__[0-9a-z_]*$"),
+            ("status", "^(valid)$"),
+        ],
     },
     ##############################################################
     #  Score Metamodel

diff --git a/docs/platform_management_plan/safety_management.rst b/docs/platform_management_plan/safety_management.rst
@@ -40,6 +40,14 @@ Because these are in responsibility of the system integrator: :need:`STD_WP_ISO2
 :need:`STD_WP_ISO26262__system_8`, :need:`STD_WP_ISO26262__system_9`, :need:`STD_WP_ISO26262__system_10`,
 :need:`STD_WP_ISO26262__system_11`
 
+Note that stakeholder requirements (:need:`STD_WP_ISO26262__system_1`) are in scope of the project,
+to be able to cover System and HW related failures which are usually covered by SW (e.g. end to end protection for ECU external communication).
+But those are the "Assumed Technical Safety Requirements" of the SW platform SEooC and do not need to be tested by SEooC supplier.
+I.e. the system testing is out of scope.
+There will be HW/SW integration tests of feature requirements, as required by ISO 26262 part 6.
+These may be reused by the user on his HW platform also to cover his Technical Safety Requirements towards the SW platform.
+But this is the decision of the user.
+
 Because there is no calibration used for the SCORE SW platform components, only configuration: :need:`STD_WP_ISO26262__software_19`,
 :need:`STD_WP_ISO26262__software_21`, :need:`STD_WP_ISO26262__software_24`
 

diff --git a/...rocess/process_areas/safety_management/guidance/guideline_safety_management.rst b/...rocess/process_areas/safety_management/guidance/guideline_safety_management.rst
@@ -32,6 +32,12 @@ Safety Management Guideline
    | Quality Management:
    | ASPICE standard is selected for quality management. Processes will always link to the :ref:`standard_iso26262` standard and to the ASPICE (todo, add link) standard.
    |
+   | Competence management:
+   | The :need:`RL__safety_manager` on SW platform level is responsible to define a competence management for the whole platform.
+   | Expectation is that the safety competence of the persons nominated for the roles is already given and only has to be checked.
+   | The exception from this are the committers, for these no safety competence needs to be enforced.
+   | So the module safety managers shall consult the :ref:`safety_management` and perform accordingly in their module project.
+   |
    | Communication:
    | Development teams are interdisciplinary, so the regular (sprint) planning and review meetings enable communication (as defined in :ref:`project_management_plan`). Another main communication means are the Pull Request reviews.
    | Also the standard Eclipse Foundation communication strategies are used (e.g. mailing lists)
@@ -87,6 +93,10 @@ Safety Management Guideline
    | Tool Management planning is part of the :need:`WP_PLATFORM_MGMT`. The respective work product to be planned as an issue of the generic safety plan is the :need:`WP_TOOL_EVAL`, which contains tool evaluation and if applicable qualification of the SW platform toolchain.
    | Components developed in C++ and Rust will have different toolchains. Both will be qualified once for the SW platform. Tool requirements will be documented in :need:`WP_TOOL_REQ`
    |
+   | **(OSS) Component qualification planning:**
+   | Based on the component classification as described in :need:`GD_GUIDL__component_classification`,
+   | the qualification of the component is planned as part of the :need:`GD_TEMP__module_safety_plan`.
+   | The template contains guidance how to do this and to document in the "OSS (sub-)component <name> Workproducts" list.
 
 .. gd_guidl:: Safety manual generation
    :id: GD_GUIDL__saf_man

diff --git a/...rocess/process_areas/safety_management/guidance/template_module_safety_plan.rst b/...rocess/process_areas/safety_management/guidance/template_module_safety_plan.rst
@@ -243,7 +243,7 @@ This document implements <add "need" link>
 |    - component, then the below table shall match the above, adding the reasoning for tailoring of work products according to the OSS component classification.
 |    - sub-component, then no workproducts additional to the component’s will be planned and activities below are part of the component’s issues.
 
-.. list-table:: OSS (sub-)omponent <name> Workproducts
+.. list-table:: OSS (sub-)component <name> Workproducts
         :header-rows: 1
 
         * - Workproduct Id

diff --git a/docs/process/process_areas/safety_management/index.rst b/docs/process/process_areas/safety_management/index.rst
@@ -45,7 +45,8 @@ Stakeholders
 
 #. :need:`Safety Manager <RL__safety_manager>`
 
-   * he is the main responsible for the safety management work products. See his role definition.
+   * he is the main responsible for the safety management work products (as in :doc:`workproducts`).
+     See also his role definition in :doc:`roles`.
 
 #. :need:`External Auditor <RL__external_auditor>`
 
@@ -77,7 +78,7 @@ Apart from the safety plans the main work products of safety management are (see
 Safety Management Tooling
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-For the safety planning and safety manual, spinx-needs will be used for referencing.
+For the safety planning and safety manual, sphinx-needs will be used for referencing.
 
 For the activities planning (who, when) we use github issues and monitor these in github projects.
 

diff --git a/docs/process/process_areas/safety_management/roles.rst b/docs/process/process_areas/safety_management/roles.rst
@@ -50,6 +50,20 @@ Roles
    * Verify, that the preconditions for the "release for production", which are  part of the release notes, are fulfilled, and the correctness, completeness and consistency of the release notes
    * Coaching the project team w.r.t all questions related to functional safety
    * Planning of safety audit
+   * Approval of OSS component classification and safety analyses (incl. DFA)
+   * Creating the safety manuals on platform and module level
+   * Checking that every person in his team has sufficient safety skills for his role
+
+   Authority
+
+   * Escalation of planning topics
+   * Initiate the publication of a safety anomaly
+   * Recommend the Release of a SW platform or a module
+   * Refusing the approval of work products as defined in the workflows
+   * Refusing the approval of his team's role nomination (i.e. requesting that the role will be withdrawn)
+
+
+
 
 
 .. role:: External Auditor
@@ -64,4 +78,8 @@ Roles
    Responsibility
 
    * Performing and reporting of safety audit
-   * Performing of confirmation reviews on safety plans and safety analysis (incl. DFA)
+   * Performing of confirmation reviews on safety plans, safety case and safety analysis (incl. DFA)
+
+   Authority
+
+   * Decision on the passing or failing of an audit
diff --git a/docs/process/process_areas/safety_management/workflows.rst b/docs/process/process_areas/safety_management/workflows.rst
@@ -68,7 +68,7 @@ Workflows
    :has: DOC_CONCEPT__safety_management
 
    | The external auditor is reponsible to perform a safety audit.
-   | The Safety Team shall support the external auditor during this.
+   | The Safety Manager shall support the external auditor during this.
    | The Project Manager and and the Safety Manager shall approve the audit report.
 
 .. workflow:: Perform Confirmation Reviews

diff --git a/docs/process/process_areas/safety_management/workproducts.rst b/docs/process/process_areas/safety_management/workproducts.rst
@@ -68,7 +68,8 @@ Work products
 
    Confirmation that a work product provides sufficient and convincing evidence of their contribution to the achievement of functional safety considering the corresponding objectives and requirements of ISO 26262.
 
-   Will contain confirmation review report for Safety Plan, Safety Analyses and Dependent Failure Analyses (DFA)
+   Will contain confirmation review report for Safety Plan, Safety Case, Safety Analyses and Dependent Failure Analyses (DFA)
+   Note that the Safety Case confirmation review will always be incomplete because the safety argument is planned to be missing in the safety case.
 
 .. workproduct:: Functional Safety Audit Report
    :id: WP__audit_report

diff --git a/docs/process/standards/iso26262.rst b/docs/process/standards/iso26262.rst
@@ -1598,7 +1598,7 @@ Part 9: Automotive safety integrity level (ASIL)-oriented and safety-oriented an
 
 
     .. std_wp:: analysis_7
-       :id: STD_ẂP__ISO26262_analysis_7
+       :id: STD_WP_ISO26262__analysis_7
        :status: valid
 
 

diff --git a/docs/process/standards/isopas8926.rst b/docs/process/standards/isopas8926.rst
@@ -150,39 +150,39 @@ ISO PAS 8926
 
 * Workproducts:
     .. std_wp:: Pas1
-       :id: STD_ẂP_ISOPAS8926__1
+       :id: STD_WP_ISOPAS8926__1
        :status: valid
 
     .. std_wp:: Pas2
-       :id: STD_ẂP_ISOPAS8926__2
+       :id: STD_WP_ISOPAS8926__2
        :status: valid
 
     .. std_wp:: Pas3
-       :id: STD_ẂP_ISOPAS8926__3
+       :id: STD_WP_ISOPAS8926__3
        :status: valid
 
     .. std_wp:: Pas4
-       :id: STD_ẂP_ISOPAS8926__4
+       :id: STD_WP_ISOPAS8926__4
        :status: valid
 
     .. std_wp:: Pas5
-       :id: STD_ẂP_ISOPAS8926__5
+       :id: STD_WP_ISOPAS8926__5
        :status: valid
 
     .. std_wp:: Pas6
-       :id: STD_ẂP_ISOPAS8926__6
+       :id: STD_WP_ISOPAS8926__6
        :status: valid
 
     .. std_wp:: Pas7
-       :id: STD_ẂP_ISOPAS8926__7
+       :id: STD_WP_ISOPAS8926__7
        :status: valid
 
-    .. std_wp:: Ppas8
-       :id: STD_ẂP_ISOPAS8926__8
+    .. std_wp:: Pas8
+       :id: STD_WP_ISOPAS8926__8
        :status: valid
 
     .. std_wp:: Pas9
-       :id: STD_ẂP_ISOPAS8926__9
+       :id: STD_WP_ISOPAS8926__9
        :status: valid