From 4e27895f2c887d245cec7d0cf2ce638391d0d1fd Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel Date: Fri, 13 Feb 2026 12:14:14 +0100 Subject: [PATCH 01/25] issue_2501_createx_missing_drafts --- docs/index.rst | 3 +- docs/platform_management_plan/index.rst | 6 + .../safety_management.rst | 24 ++-- .../platform_ver_report.rst | 83 ++++++++++++++ .../fdr_reports_safety_analyses_DFA.rst | 91 ++++++++++++++++ docs/safety/fdr_reports_safety_package.rst | 74 +++++++++++++ ...dr_reports_safety_platform_safety_plan.rst | 103 ++++++++++++++++++ docs/safety/index.rst | 28 +++++ docs/safety/platform_dfa.rst | 47 ++++++++ docs/safety/platform_safety_manual.rst | 92 ++++++++++++++++ 10 files changed, 538 insertions(+), 13 deletions(-) create mode 100644 docs/platform_management_plan/verification_report/platform_ver_report.rst create mode 100644 docs/safety/fdr_reports_safety_analyses_DFA.rst create mode 100644 docs/safety/fdr_reports_safety_package.rst create mode 100644 docs/safety/fdr_reports_safety_platform_safety_plan.rst create mode 100644 docs/safety/index.rst create mode 100644 docs/safety/platform_dfa.rst create mode 100644 docs/safety/platform_safety_manual.rst diff --git a/docs/index.rst b/docs/index.rst index 8417fd620e..392d1a35a9 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -89,7 +89,7 @@ Project structure and processes .. grid-item-card:: Platform Management Plan (PMP) - ^^^ + ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Read about our project and organization structure in the :ref:`Project Handbook `. And learn how we deal with :ref:`Platform Safety Plan ` or care about :ref:`Software Verification Plan `. @@ -105,6 +105,7 @@ Project structure and processes requirements/index modules/index contribute/index + safety/index Releases Tools diff --git a/docs/platform_management_plan/index.rst b/docs/platform_management_plan/index.rst index b75d3fdbc9..59282ca831 100644 --- a/docs/platform_management_plan/index.rst +++ b/docs/platform_management_plan/index.rst @@ -50,3 +50,9 @@ Platform Management Plan role_assignment/platform_safety_manager role_assignment/platform_security_manager role_assignment/platform_quality_manager + +.. toctree:: + :titlesonly: + :caption: Verification Report + + verification_report/platform_ver_report diff --git a/docs/platform_management_plan/safety_management.rst b/docs/platform_management_plan/safety_management.rst index 9b5c35ecdc..f775ba68eb 100644 --- a/docs/platform_management_plan/safety_management.rst +++ b/docs/platform_management_plan/safety_management.rst @@ -377,8 +377,8 @@ Functional Safety/Security Management SW Platform Work Products * - :need:`wp__verification_platform_ver_report` - :ndf:`copy('status', need_id='wf__verification_platform_ver_report')` - - - - + - :need:`doc__platform_verification_report` + - draft * - :need:`wp__requirements_stkh` - :ndf:`copy('status', need_id='wf__req_stkh_req')` @@ -429,18 +429,18 @@ Functional Safety Specific SW Platform Work Products * - :need:`wp__fdr_reports` (platform Safety Plan) - :ndf:`copy('status', need_id='wf__p_formal_rv')` - - - - + - :need:`doc__platform_safety_plan_fdr` + - draft * - :need:`wp__fdr_reports` (platform Safety Package) - :ndf:`copy('status', need_id='wf__p_formal_rv')` - - - - + - :need:`doc__Platform_safety_package_fdr` + - draft * - :need:`wp__fdr_reports` (feature's Safety Analyses & DFA) - :ndf:`copy('status', need_id='wf__p_formal_rv')` - - - - + - :need:`doc__Platform_safety_analysis_fdr` + - draft * - :need:`wp__audit_report` - performed by external experts @@ -449,13 +449,13 @@ Functional Safety Specific SW Platform Work Products * - :need:`wp__platform_dfa` - :ndf:`copy('status', need_id='wf__analyse_platform_featarch')` - - - - + - :need:`doc__platform_dfa` + - draft * - :need:`wp__platform_safety_manual` - :ndf:`copy('status', need_id='wf__cr_mt_safety_manual')` - - - - + - :need:`doc__platform_safety_manual` + - draft * - :need:`wp__safety_tailoring` (generic) - :ndf:`copy('status', need_id='wf__def_app_process_description')` diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst new file mode 100644 index 0000000000..1a8ceb67fc --- /dev/null +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -0,0 +1,83 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Verification Report +=================== + +.. note:: Document header + +.. document:: Platform Verification Report + :id: doc__platform_verification_report + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__verification_module_ver_report + :tags: template + + +This verification report is based on the :need:`gd_temp__verification_plan`. +It covers all the components of the above stated module. + +Verification Report contains: + +**1. Verification Coverage** + +**1.1. on Requirements** + - Lists of component requirements (incl. AoU satisfied by the component) tested by which test case, passed/failed and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - For external component Assumptions of Use: coverage by platform safety manual or feature/components incl. test case, passed/failed and completeness verdict + - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. + - List of component requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + +**1.2. on Architecture** + - List of component architecture tags tested by which test case, passed/failed and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - This is split in a list of QM components tested and a separate list of tests for ASIL rated components. + - List of component architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + +**1.3. on Detailed Design** + - List of detailed design tags tested by which test case, passed/failed and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - This is split in a list of QM components tested and a separate list of tests for ASIL rated components. + - List of detailed design tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + + - The lists may also contain other verification methods like "Analysis" - process tbd + +**2. DFA Report** + - List of the performed component DFA, pass/fail with open mitigations + +**3. Safety Analysis Report** + - List of the performed component Safety Analysis, pass/fail with open mitigations + +**4. Unit Verification Coverage** + +**4.1. Structural Coverage** + - List of the units with C0(line) and C1(branch) coverage absolute and percentage + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - List includes a column for the safety rating of each unit. + +**4.2. Static Code Analysis** + - List of the units with compiler warning numbers and coding rule violation numbers + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - List includes a column for the safety rating of each unit. + +**4.3. Manual Code Inspection** + - List of components (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + +**5. Software component qualification verification report** + - Contains the needed verification results if for some components a qualification of pre-developed SW is performed. + +**Note1:** The verification report is valid for the module version tagged together with the report + +**Note2:** All the above lists are generated automatically diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst new file mode 100644 index 0000000000..d2c7488e01 --- /dev/null +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -0,0 +1,91 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + + +Safety Analysis Checklist +========================= + +.. document:: Platform Safety Analyses Checklist + :id: doc__platform_safety_analysis_fdr + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__fdr_reports + :tags: template + + +**Purpose** +The purpose of this Safety Analysis (DFA and FMEA) checklist template is to collect the topics to be checked during verification of the Platform Safety Analysis & DFA. + +**Conduct** +As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager: + +- reviewer: + +**Checklist** + +Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular. + +.. list-table:: Safety Analysis Checklist + :header-rows: 1 + :widths: 10,30,30,15,8,8 + + * - Review ID + - Acceptance Criteria + - Guidance + - Passed + - Remarks + - Issue link + * - REQ_01_01 + - Is / are the attribute sufficient set correctly? + - The mitigations shall have a direct influence ont the violation by prevention, detection or mitigation to reduce the risk to an acceptable level. + - The mitigations are sufficient. + - + - + * - REQ_01_02 + - Are the templates for DFA and/or FMEA used? + - See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis` + - Templates are used to generate the DFA or / and FMEA. + - + - + * - REQ_01_03 + - Were the failure initiators / fault models applied? + - See :need:`gd_guidl__dfa_failure_initiators` / :need:`gd_guidl__fault_models` + - The applicable items of the failure initiators / fault models are used to ensure a structured analysis. For all not applicable items an argument shall be given in the content of the document. + - + - + * - REQ_01_04 + - Are the failure effects clearly and completely described? + - Use the generic failure effect descriptions and enlarge the description if it's applicable to the considered element. + - The effects of the failure is described completely. The effect can be recognized easily. + - + - + * - REQ_01_06 + - Is the attribute "mitigated by" linked correct? + - Check if the correct failure effect is linked via "mitigated by". + - The "mitigated by" link is correct. + - + - + * - REQ_01_07 + - Is the sufficiency of the "mitigated by" (prevention, detection or mitigation) described or can it be recognized easily? + - The sufficiency of the "mitigated by" is described in the content of the document. It can be recognized easily. + - The "mitigated by" shows clearly that a fault / failure can be mitigated by the linked requirement by prevention, detection or mitigation. It shall be described in the contend. + - + - + * - REQ_01_08 + - Is the overall result of the Safety Analysis described in the report? + - It shall be shown in the report if the Safety Analysis are finished and if all artifacts are "valid" and "sufficient". + - The results of the Safety Analysis are described in the report. The report is available :need:`wp__verification_platform_ver_report`. + - + - diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst new file mode 100644 index 0000000000..bc87e5d846 --- /dev/null +++ b/docs/safety/fdr_reports_safety_package.rst @@ -0,0 +1,74 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Safety Package Formal Review Report +=================================== + +.. note:: Document header + +.. document:: Platform Safety Package Formal Review + :id: doc__platform_safety_package_fdr + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__fdr_reports + :tags: template + + + +**Purpose** + +The purpose of this review checklist is to report status of the formal review for the Platform safety package. + +**Conduct** +As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager: + +- reviewer: + +**Checklist** + +See also :ref:`review_concept` for further information about reviews in general and inspection in particular. + +.. list-table:: Safety Package Checklist + :header-rows: 1 + + * - Id + - Safety package activity + - Compliant to ISO 26262? + - Comment + + * - 1 + - Is a safety package provided which matches the safety plan (i.e. all planned work products referenced)? + - [YES | NO ] + - + + * - 2 + - Is the argument how functional safety is achieved, provided in the safety package, plausible and sufficient? + - NO + - The argument is intentionally not provided by the project. + + * - 3 + - Are the referenced work products available? + - [YES | NO ] + - + + * - 4 + - Are the referenced work products in released state, including the process safety audit? + - [YES | NO ] + - + + * - 5 + - If safety related deviations from the process or safety concept are documented, are these argued understandably? + - [YES | NO ] + - diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst new file mode 100644 index 0000000000..236f97ff39 --- /dev/null +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -0,0 +1,103 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Safety Plan Formal Review Report +================================ + +.. note:: Document header + +.. document:: S-CORE Platform Safety Plan Formal Review + :id: doc__platform_safety_plan_fdr + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__fdr_reports + :tags: template + + +**Purpose** + +The purpose of this safety plan formal review checklist is to report status of the review for the Platform safety plan. + +**Conduct** +As described in :need:`wf__p_formal_rv`, the formal document review is performed by an "external" safety manager: + +- reviewer: + +**Checklist** + +See also :ref:`review_concept` for further information about reviews in general and inspection in particular. + +.. list-table:: Safety Plan Checklist + :header-rows: 1 + + * - Id + - Safety plan activity + - Compliant to ISO 26262? + - Comment + + * - 1 + - Is the rationale for the safety work products tailoring included? + - [YES | NO ] + - + + * - 2 + - Is impact analysis planned in case of re-use of SW (needed for every release following the first formal release)? + - [YES | NO ] + - + + * - 3 + - Does the safety plan define all needed activities for safety management (incl. formal document review and Safety Audit)? + - [YES | NO ] + - + + * - 4 + - Does the safety plan define all needed activities for System and SW development, integration and verification? + - [YES | NO ] + - + + * - 5 + - Does the safety plan define all needed activities for safety analysis and DFA? + - [YES | NO ] + - + + * - 6 + - Does the safety plan define all needed activities for supporting processes (incl. tool mgt)? + - [YES | NO ] + - + + * - 7 + - Does the safety plan document a responsible for all activities? + - [YES | NO ] + - + + * - 8 + - If OSS software components is used, is it planned to be qualified? + - [YES | NO ] + - + + * - 9 + - Is a safety manager and a project manager appointed for the project? + - [YES | NO ] + - + + * - 10 + - Is safety plan sufficiently linked to the project plan? + - [YES | NO ] + - + + * - 11 + - Is safety plan updated iteratively to show the progress? + - [YES | NO ] + - diff --git a/docs/safety/index.rst b/docs/safety/index.rst new file mode 100644 index 0000000000..90f340c2b7 --- /dev/null +++ b/docs/safety/index.rst @@ -0,0 +1,28 @@ +.. + # ******************************************************************************* + # Copyright (c) 2024 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +.. + +Safety documentation +==================== + +Safety specific documentation for Platform is listed here + +.. toctree:: + + fdr_reports_safety_analyses_DFA + fdr_reports_safety_package + fdr_reports_safety_platform_safety_plan + platform_dfa + platform_safety_manual diff --git a/docs/safety/platform_dfa.rst b/docs/safety/platform_dfa.rst new file mode 100644 index 0000000000..99c21c2c2b --- /dev/null +++ b/docs/safety/platform_dfa.rst @@ -0,0 +1,47 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + + +Platform DFA (Dependent Failure Analysis) +========================================= + +.. document:: Platform DFA + :id: doc__platform_dfa + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__platform_dfa + :tags: template + +.. note:: The platform DFA is only performed once at platform level to analyse the dependencies between the features of the platform. + The results shall be used as an input for the safety analysis so that general safety mechanisms are only defined once and not in every single safety analysis. + +.. note:: Use the content of the document to describe e.g. why a fault model is not applicable for the diagram. + + +Dependent Failure Initiators +---------------------------- + +.. code-block:: rst + + .. plat_saf_dfa:: + :violates: <Feature architecture> + :id: plat_saf_DFA__<Feature>__<Element descriptor> + :failure_id: <ID from DFA failure initiators :need:`gd_guidl__dfa_failure_initiators`> + :failure_effect: "description of failure effect of the failure initiator on the element" + :mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement> + :mitigation_issue: <ID from Issue Tracker> + :sufficient: <yes|no> + :status: <valid|invalid> +.. note:: Argument is inside the 'content'. Therefore content is mandatory. diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst new file mode 100644 index 0000000000..24ab704c30 --- /dev/null +++ b/docs/safety/platform_safety_manual.rst @@ -0,0 +1,92 @@ +.. + # ******************************************************************************* + # Copyright (c) 2025 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Safety Manual +============= + +.. note:: Document header + +.. document:: Platform Safety Manual + :id: doc__platform_safety_manual + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__module_safety_manual + :tags: template + + +Introduction/Scope +------------------ +| This Safety Manual applies to the S-CORE Platform + +Assumed Platform Safety Requirements +------------------------------------ +| For the S-CORE Platformhe following safety related stakeholder requirements are assumed to define the top level functionality (purpose) of the S-CORE Platform. I.e. from these all the feature and component requirements implemented are derived. +| <List here all the stakeholder requirements, with safety not equal to QM, the module's components requirements are derived from.> + +Assumptions of Use +------------------ + +Assumptions on the Environment +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +| Generally the assumption of the project platform SEooC is that it is integrated in a safe system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module's safety concept. +| <List here all the OS calls the project platform expects to be safe.> + +List of AoUs expected from the environment the platform / module runs on: + +.. needtable:: + :style: table + :columns: title;id;status + :colwidths: 25,25,25 + :sort: title + + results = [] + + for need in needs.filter_types(["aou_req"]): + if need and "environment" in need["tags"]: + results.append(need) + +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 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. + +List of AoUs on the user of the platform features or the module of this safety manual: + +.. needtable:: + :style: table + :columns: title;id;status + :colwidths: 25,25,25 + :sort: title + + results = [] + + for need in needs.filter_types(["aou_req"]): + if need and "environment" not in need["tags"]: + results.append(need) + +Safety concept of the SEooC +--------------------------- +| <Describe here the safety concept incl. which faults are taken care of, reactions of the implemented functions under anomalous operating conditions ... if this is not already documented sufficiently in the feature documentation "safety impact" section of all the features the module is used in.> + +Safety Anomalies +---------------- +| Anomalies (bugs in ASIL SW, detected by testing or by users, which could not be fixed) known before release are documented in the platform/module release notes <add link to release note>. + +References +---------- +| <link to the user manual> +| <other links> From 1a30be4bc5da3d24e59b4199edd387399d796b04 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Mon, 16 Feb 2026 10:39:56 +0100 Subject: [PATCH 02/25] issue2501_fixed wrong links --- docs/platform_management_plan/safety_management.rst | 6 +++--- docs/safety/fdr_reports_safety_analyses_DFA.rst | 2 +- docs/safety/fdr_reports_safety_package.rst | 4 ++-- docs/safety/fdr_reports_safety_platform_safety_plan.rst | 4 ++-- docs/safety/platform_dfa.rst | 6 +++--- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/platform_management_plan/safety_management.rst b/docs/platform_management_plan/safety_management.rst index f775ba68eb..41979d26b8 100644 --- a/docs/platform_management_plan/safety_management.rst +++ b/docs/platform_management_plan/safety_management.rst @@ -378,7 +378,7 @@ Functional Safety/Security Management SW Platform Work Products * - :need:`wp__verification_platform_ver_report` - :ndf:`copy('status', need_id='wf__verification_platform_ver_report')` - :need:`doc__platform_verification_report` - - draft + - draft * - :need:`wp__requirements_stkh` - :ndf:`copy('status', need_id='wf__req_stkh_req')` @@ -434,12 +434,12 @@ Functional Safety Specific SW Platform Work Products * - :need:`wp__fdr_reports` (platform Safety Package) - :ndf:`copy('status', need_id='wf__p_formal_rv')` - - :need:`doc__Platform_safety_package_fdr` + - :need:`doc__platform_safety_package_fdr` - draft * - :need:`wp__fdr_reports` (feature's Safety Analyses & DFA) - :ndf:`copy('status', need_id='wf__p_formal_rv')` - - :need:`doc__Platform_safety_analysis_fdr` + - :need:`doc__platform_safety_analysis_fdr` - draft * - :need:`wp__audit_report` diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index d2c7488e01..1f7a8d8b9e 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -55,7 +55,7 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - * - REQ_01_02 - Are the templates for DFA and/or FMEA used? - - See :ref:`dfa_templates` / :ref:`FMEA_templates` and also :ref:`process_requirements_safety_analysis` + - See :ref:`doc__platform_dfa` - Templates are used to generate the DFA or / and FMEA. - <yes|no> - diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index bc87e5d846..d004463216 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -23,7 +23,7 @@ Safety Package Formal Review Report :safety: ASIL_B :security: NO :realizes: wp__fdr_reports - :tags: template + :tags: @@ -38,7 +38,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :ref:`review_concept` for further information about reviews in general and inspection in particular. +See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Package Checklist :header-rows: 1 diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 236f97ff39..46f58cce3b 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -23,7 +23,7 @@ Safety Plan Formal Review Report :safety: ASIL_B :security: NO :realizes: wp__fdr_reports - :tags: template + :tags: **Purpose** @@ -37,7 +37,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :ref:`review_concept` for further information about reviews in general and inspection in particular. +See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Plan Checklist :header-rows: 1 diff --git a/docs/safety/platform_dfa.rst b/docs/safety/platform_dfa.rst index 99c21c2c2b..922d8da876 100644 --- a/docs/safety/platform_dfa.rst +++ b/docs/safety/platform_dfa.rst @@ -17,18 +17,18 @@ Platform DFA (Dependent Failure Analysis) ========================================= .. document:: Platform DFA - :id: doc__platform_dfa + :id: doc__score_platform_dfa :status: draft :safety: ASIL_B :security: NO :realizes: wp__platform_dfa - :tags: template + :tags: .. note:: The platform DFA is only performed once at platform level to analyse the dependencies between the features of the platform. The results shall be used as an input for the safety analysis so that general safety mechanisms are only defined once and not in every single safety analysis. .. note:: Use the content of the document to describe e.g. why a fault model is not applicable for the diagram. - + Dependent Failure Initiators ---------------------------- From e8eb38a32bce53bbda557d368b32866a7c5435dc Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 17 Feb 2026 14:13:11 +0100 Subject: [PATCH 03/25] issue2501 fixed link errors as per suggestions --- docs/safety/fdr_reports_safety_analyses_DFA.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index 1f7a8d8b9e..0e26cee118 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -35,7 +35,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular. +Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Analysis Checklist :header-rows: 1 @@ -55,7 +55,7 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - * - REQ_01_02 - Are the templates for DFA and/or FMEA used? - - See :ref:`doc__platform_dfa` + - See :need:`doc__platform_dfa` - Templates are used to generate the DFA or / and FMEA. - <yes|no> - From e3a91744a6f58b049fa826e5b63e258a84615dae Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 17 Feb 2026 14:45:37 +0100 Subject: [PATCH 04/25] issue 2501: fixed last residual link errors --- docs/safety/fdr_reports_safety_analyses_DFA.rst | 2 +- docs/safety/fdr_reports_safety_package.rst | 2 +- docs/safety/fdr_reports_safety_platform_safety_plan.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index 0e26cee118..5fa2920e7e 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -35,7 +35,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. +Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular. .. list-table:: Safety Analysis Checklist :header-rows: 1 diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index d004463216..6e0b8d324e 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -38,7 +38,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. +See also :need:`review_concept` for further information about reviews in general and inspection in particular. .. list-table:: Safety Package Checklist :header-rows: 1 diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 46f58cce3b..b28c98ed12 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -37,7 +37,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :ref:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. +See also :need:`review_concept` for further information about reviews in general and inspection in particular. .. list-table:: Safety Plan Checklist :header-rows: 1 From e30633bba19dd964ad73c3e0244a92e09aa4e407 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 17 Feb 2026 15:08:33 +0100 Subject: [PATCH 05/25] issue 2501 trying fixing errors link --- docs/safety/fdr_reports_safety_analyses_DFA.rst | 2 +- docs/safety/fdr_reports_safety_package.rst | 2 +- docs/safety/fdr_reports_safety_platform_safety_plan.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index 5fa2920e7e..f2168e6c78 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -35,7 +35,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :ref:`review_concept` for further information about reviews in general and inspection in particular. +Please note that it is mandatory to fill in the "passed" column with "yes" or "no" for each checklist item and additional to add in the remarks why it is passed or not passed. In case of "no" an issue link to the issue tracking system has to be added in the last column. See also :need:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Analysis Checklist :header-rows: 1 diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index 6e0b8d324e..39512c2ea9 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -38,7 +38,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :need:`review_concept` for further information about reviews in general and inspection in particular. +See also :need:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Package Checklist :header-rows: 1 diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index b28c98ed12..4cff1b9d3a 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -37,7 +37,7 @@ As described in :need:`wf__p_formal_rv`, the formal document review is performed **Checklist** -See also :need:`review_concept` for further information about reviews in general and inspection in particular. +See also :need:`doc_concept__wp_inspections` for further information about reviews in general and inspection in particular. .. list-table:: Safety Plan Checklist :header-rows: 1 From 0fbb3d1499f41de960975cd87f11c0bd9e63e96e Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Wed, 18 Feb 2026 09:21:29 +0100 Subject: [PATCH 06/25] 2501 attifunel fixed wrong req. link --- .../verification_report/platform_ver_report.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 1a8ceb67fc..78ba4c37c4 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -22,7 +22,7 @@ Verification Report :status: draft :safety: ASIL_B :security: NO - :realizes: wp__verification_module_ver_report + :realizes: wp__verification_platform_ver_report :tags: template From 850bf14b39034db45cc9fa0c23f1b55509561cad Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Wed, 18 Feb 2026 09:22:42 +0100 Subject: [PATCH 07/25] 2501 attifunel fixed wrong tag --- .../verification_report/platform_ver_report.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 78ba4c37c4..4ad426c2f5 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -23,7 +23,7 @@ Verification Report :safety: ASIL_B :security: NO :realizes: wp__verification_platform_ver_report - :tags: template + :tags: draft This verification report is based on the :need:`gd_temp__verification_plan`. From f0658f676ff7ff6b9644928a512971b48a7a1140 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Wed, 18 Feb 2026 09:29:04 +0100 Subject: [PATCH 08/25] 2501 attifunel fixed wrroenous template flags --- .../verification_report/platform_ver_report.rst | 2 +- docs/safety/fdr_reports_safety_analyses_DFA.rst | 2 +- docs/safety/fdr_reports_safety_package.rst | 2 +- docs/safety/platform_safety_manual.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 4ad426c2f5..19ec3343ba 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -23,7 +23,7 @@ Verification Report :safety: ASIL_B :security: NO :realizes: wp__verification_platform_ver_report - :tags: draft + :tags: This verification report is based on the :need:`gd_temp__verification_plan`. diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index f2168e6c78..2f3e3950fe 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -22,7 +22,7 @@ Safety Analysis Checklist :safety: ASIL_B :security: YES :realizes: wp__fdr_reports - :tags: template + :tags: **Purpose** diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index 39512c2ea9..a39be8a2c2 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -23,7 +23,7 @@ Safety Package Formal Review Report :safety: ASIL_B :security: NO :realizes: wp__fdr_reports - :tags: + :tags: draft diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst index 24ab704c30..2e6fc01ebc 100644 --- a/docs/safety/platform_safety_manual.rst +++ b/docs/safety/platform_safety_manual.rst @@ -23,7 +23,7 @@ Safety Manual :safety: ASIL_B :security: NO :realizes: wp__module_safety_manual - :tags: template + :tags: Introduction/Scope From 664879bc0dac699c190e0c8f4ad2361ef95b494f Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Wed, 18 Feb 2026 09:41:50 +0100 Subject: [PATCH 09/25] 2501 attifunel corrected platform ver. report template --- .../platform_ver_report.rst | 68 ++++--------------- 1 file changed, 14 insertions(+), 54 deletions(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 19ec3343ba..4bea2ec42f 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -23,61 +23,21 @@ Verification Report :safety: ASIL_B :security: NO :realizes: wp__verification_platform_ver_report - :tags: + :tags: -This verification report is based on the :need:`gd_temp__verification_plan`. -It covers all the components of the above stated module. -Verification Report contains: +In its final form, Platform Verification Report must contain: -**1. Verification Coverage** - -**1.1. on Requirements** - - Lists of component requirements (incl. AoU satisfied by the component) tested by which test case, passed/failed and completeness verdict - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - For external component Assumptions of Use: coverage by platform safety manual or feature/components incl. test case, passed/failed and completeness verdict - - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. - - List of component requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - -**1.2. on Architecture** - - List of component architecture tags tested by which test case, passed/failed and completeness verdict - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - This is split in a list of QM components tested and a separate list of tests for ASIL rated components. - - List of component architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - -**1.3. on Detailed Design** - - List of detailed design tags tested by which test case, passed/failed and completeness verdict - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - This is split in a list of QM components tested and a separate list of tests for ASIL rated components. - - List of detailed design tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - - - The lists may also contain other verification methods like "Analysis" - process tbd - -**2. DFA Report** - - List of the performed component DFA, pass/fail with open mitigations - -**3. Safety Analysis Report** - - List of the performed component Safety Analysis, pass/fail with open mitigations - -**4. Unit Verification Coverage** - -**4.1. Structural Coverage** - - List of the units with C0(line) and C1(branch) coverage absolute and percentage - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - List includes a column for the safety rating of each unit. - -**4.2. Static Code Analysis** - - List of the units with compiler warning numbers and coding rule violation numbers - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - List includes a column for the safety rating of each unit. - -**4.3. Manual Code Inspection** - - List of components (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - -**5. Software component qualification verification report** - - Contains the needed verification results if for some components a qualification of pre-developed SW is performed. - -**Note1:** The verification report is valid for the module version tagged together with the report - -**Note2:** All the above lists are generated automatically + - List of requirements (stakeholder and feature) and architecture tested by which test + (can be several levels), passed/failed and completeness verdict, including normal + operation and failure reactions + - The list of requirements may also contain other verification methods like "Analysis" + - Formal evidence about the performed DFA + - Formal evidence about the performed Safety Analyses + - Test result per test case from + :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run + - Test log per test case from + :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run From 94db119027c585c769728020c734485138378e46 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Wed, 18 Feb 2026 15:10:25 +0100 Subject: [PATCH 10/25] issue 2501 attifunel somex fixes --- .../verification_report/platform_ver_report.rst | 5 +++-- docs/safety/platform_dfa.rst | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 4bea2ec42f..3418bb4a1b 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -27,14 +27,15 @@ Verification Report -In its final form, Platform Verification Report must contain: +In its final form (status = valid), Platform Verification Report must contain: - List of requirements (stakeholder and feature) and architecture tested by which test (can be several levels), passed/failed and completeness verdict, including normal operation and failure reactions - The list of requirements may also contain other verification methods like "Analysis" - Formal evidence about the performed DFA - - Formal evidence about the performed Safety Analyses + - Formal evidence about the performed Safety Analyses (if planned) + - Summary reports ("all passed" or OPs, justifications, planned actions etc.) for the above safety analyses - Test result per test case from :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` with status passed/failed/not_run diff --git a/docs/safety/platform_dfa.rst b/docs/safety/platform_dfa.rst index 922d8da876..ddcca70195 100644 --- a/docs/safety/platform_dfa.rst +++ b/docs/safety/platform_dfa.rst @@ -40,7 +40,7 @@ Dependent Failure Initiators :id: plat_saf_DFA__<Feature>__<Element descriptor> :failure_id: <ID from DFA failure initiators :need:`gd_guidl__dfa_failure_initiators`> :failure_effect: "description of failure effect of the failure initiator on the element" - :mitigated_by: <ID from Feature Requirement | ID from AoU Feature Requirement> + :mitigated_by: <ID from Stakeholder Requirement | ID from AoU Feature Requirement> :mitigation_issue: <ID from Issue Tracker> :sufficient: <yes|no> :status: <valid|invalid> From 7cc7537f4e70240647c136de3b63cae797bb830b Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 16:58:02 +0100 Subject: [PATCH 11/25] issue 2501 fixed review comments --- .../verification_report/platform_ver_report.rst | 3 +-- docs/safety/fdr_reports_safety_analyses_DFA.rst | 6 +++--- docs/safety/fdr_reports_safety_package.rst | 1 - docs/safety/fdr_reports_safety_platform_safety_plan.rst | 1 - docs/safety/index.rst | 2 +- docs/safety/platform_safety_manual.rst | 7 +++---- 6 files changed, 8 insertions(+), 12 deletions(-) diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst index 3418bb4a1b..c8f44d5678 100644 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ b/docs/platform_management_plan/verification_report/platform_ver_report.rst @@ -15,7 +15,6 @@ Verification Report =================== -.. note:: Document header .. document:: Platform Verification Report :id: doc__platform_verification_report @@ -33,7 +32,7 @@ In its final form (status = valid), Platform Verification Report must contain: (can be several levels), passed/failed and completeness verdict, including normal operation and failure reactions - The list of requirements may also contain other verification methods like "Analysis" - - Formal evidence about the performed DFA + - Formal evidence about the Platform DFA - Formal evidence about the performed Safety Analyses (if planned) - Summary reports ("all passed" or OPs, justifications, planned actions etc.) for the above safety analyses - Test result per test case from diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index 2f3e3950fe..f5fe7e673e 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -13,16 +13,16 @@ # ******************************************************************************* -Safety Analysis Checklist + Safety Analysis Formal Review Report ========================= -.. document:: Platform Safety Analyses Checklist +.. document:: Safety Analysis Formal Review Report :id: doc__platform_safety_analysis_fdr :status: draft :safety: ASIL_B :security: YES :realizes: wp__fdr_reports - :tags: + :tags: **Purpose** diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index a39be8a2c2..32672a8cf4 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -15,7 +15,6 @@ Safety Package Formal Review Report =================================== -.. note:: Document header .. document:: Platform Safety Package Formal Review :id: doc__platform_safety_package_fdr diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 4cff1b9d3a..d063a67f34 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -15,7 +15,6 @@ Safety Plan Formal Review Report ================================ -.. note:: Document header .. document:: S-CORE Platform Safety Plan Formal Review :id: doc__platform_safety_plan_fdr diff --git a/docs/safety/index.rst b/docs/safety/index.rst index 90f340c2b7..11b580dba3 100644 --- a/docs/safety/index.rst +++ b/docs/safety/index.rst @@ -20,7 +20,7 @@ Safety documentation Safety specific documentation for Platform is listed here .. toctree:: - + :maxdepth: 1 fdr_reports_safety_analyses_DFA fdr_reports_safety_package fdr_reports_safety_platform_safety_plan diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst index 2e6fc01ebc..fb4d8f8421 100644 --- a/docs/safety/platform_safety_manual.rst +++ b/docs/safety/platform_safety_manual.rst @@ -15,7 +15,6 @@ Safety Manual ============= -.. note:: Document header .. document:: Platform Safety Manual :id: doc__platform_safety_manual @@ -23,7 +22,7 @@ Safety Manual :safety: ASIL_B :security: NO :realizes: wp__module_safety_manual - :tags: + :tags: Introduction/Scope @@ -33,7 +32,7 @@ Introduction/Scope Assumed Platform Safety Requirements ------------------------------------ | For the S-CORE Platformhe following safety related stakeholder requirements are assumed to define the top level functionality (purpose) of the S-CORE Platform. I.e. from these all the feature and component requirements implemented are derived. -| <List here all the stakeholder requirements, with safety not equal to QM, the module's components requirements are derived from.> +| **<List here all the stakeholder requirements, with safety level not equal to QM, the module's components requirements are derived from.>** Assumptions of Use ------------------ @@ -41,7 +40,7 @@ Assumptions of Use Assumptions on the Environment ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | Generally the assumption of the project platform SEooC is that it is integrated in a safe system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module's safety concept. -| <List here all the OS calls the project platform expects to be safe.> +| **<List here all the OS calls the project platform expects to be safe.>** List of AoUs expected from the environment the platform / module runs on: From f2663ee883c61b418e47e6daab9292bee6485adb Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:07:25 +0100 Subject: [PATCH 12/25] issue 5201 attifunel changes from review --- docs/platform_management_plan/index.rst | 7 +---- docs/safety/platform_ver_report.rst | 42 +++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 6 deletions(-) create mode 100644 docs/safety/platform_ver_report.rst diff --git a/docs/platform_management_plan/index.rst b/docs/platform_management_plan/index.rst index 59282ca831..1f3e0aa00b 100644 --- a/docs/platform_management_plan/index.rst +++ b/docs/platform_management_plan/index.rst @@ -50,9 +50,4 @@ Platform Management Plan role_assignment/platform_safety_manager role_assignment/platform_security_manager role_assignment/platform_quality_manager - -.. toctree:: - :titlesonly: - :caption: Verification Report - - verification_report/platform_ver_report + diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst new file mode 100644 index 0000000000..9892c71c63 --- /dev/null +++ b/docs/safety/platform_ver_report.rst @@ -0,0 +1,42 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Verification Report +=================== + +.. document:: Platform Verification Report + :id: doc__platform_verification_report + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__verification_platform_ver_report + :tags: + + + +In its final form (status = valid), Platform Verification Report must contain: + + - List of requirements (stakeholder and feature) and architecture tested by which test + (can be several levels), passed/failed and completeness verdict, including normal + operation and failure reactions + - The list of requirements may also contain other verification methods like "Analysis" + - Formal evidence about the performed DFA + - Formal evidence about the performed Safety Analyses (if planned) + - Summary reports ("all passed" or OPs, justifications, planned actions etc.) for the above safety analyses + - Test result per test case from + :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run + - Test log per test case from + :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run From cc5a1190a7d49fa787d0071b1125c6cfde31579e Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:07:47 +0100 Subject: [PATCH 13/25] issue 2501 fixed further review comments --- docs/safety/fdr_reports_safety_package.rst | 1 - docs/safety/fdr_reports_safety_platform_safety_plan.rst | 1 - docs/safety/index.rst | 2 ++ docs/safety/platform_safety_manual.rst | 1 - 4 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index 32672a8cf4..fe675bb3a1 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -15,7 +15,6 @@ Safety Package Formal Review Report =================================== - .. document:: Platform Safety Package Formal Review :id: doc__platform_safety_package_fdr :status: draft diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index d063a67f34..2daf0ed700 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -15,7 +15,6 @@ Safety Plan Formal Review Report ================================ - .. document:: S-CORE Platform Safety Plan Formal Review :id: doc__platform_safety_plan_fdr :status: draft diff --git a/docs/safety/index.rst b/docs/safety/index.rst index 11b580dba3..5c8be7ed84 100644 --- a/docs/safety/index.rst +++ b/docs/safety/index.rst @@ -26,3 +26,5 @@ Safety specific documentation for Platform is listed here fdr_reports_safety_platform_safety_plan platform_dfa platform_safety_manual + platform_ver_report.rst + diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst index fb4d8f8421..419c376f37 100644 --- a/docs/safety/platform_safety_manual.rst +++ b/docs/safety/platform_safety_manual.rst @@ -15,7 +15,6 @@ Safety Manual ============= - .. document:: Platform Safety Manual :id: doc__platform_safety_manual :status: draft From 1aa48be732c7f94189efb279dd8fa805f654faac Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:16:24 +0100 Subject: [PATCH 14/25] issue 2501 attifunel fixing build errors --- docs/safety/fdr_reports_safety_analyses_DFA.rst | 2 +- docs/safety/index.rst | 2 +- docs/safety/platform_ver_report.rst | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index f5fe7e673e..8edab15001 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -14,7 +14,7 @@ Safety Analysis Formal Review Report -========================= +===================================== .. document:: Safety Analysis Formal Review Report :id: doc__platform_safety_analysis_fdr diff --git a/docs/safety/index.rst b/docs/safety/index.rst index 5c8be7ed84..47efe5accf 100644 --- a/docs/safety/index.rst +++ b/docs/safety/index.rst @@ -21,10 +21,10 @@ Safety specific documentation for Platform is listed here .. toctree:: :maxdepth: 1 + fdr_reports_safety_analyses_DFA fdr_reports_safety_package fdr_reports_safety_platform_safety_plan platform_dfa platform_safety_manual platform_ver_report.rst - diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst index 9892c71c63..c2d56fdb53 100644 --- a/docs/safety/platform_ver_report.rst +++ b/docs/safety/platform_ver_report.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Verification Report -=================== +Platform Verification Report +============================ .. document:: Platform Verification Report :id: doc__platform_verification_report From 413b19d6cf85373c7c2f7e828bc24ede5480a990 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:26:12 +0100 Subject: [PATCH 15/25] issue 2501 trying again to solve conflicts... --- .../platform_ver_report.rst | 43 ------------------- .../fdr_reports_safety_analyses_DFA.rst | 4 +- docs/safety/fdr_reports_safety_package.rst | 4 +- ...dr_reports_safety_platform_safety_plan.rst | 4 +- docs/safety/platform_dfa.rst | 4 +- 5 files changed, 8 insertions(+), 51 deletions(-) delete mode 100644 docs/platform_management_plan/verification_report/platform_ver_report.rst diff --git a/docs/platform_management_plan/verification_report/platform_ver_report.rst b/docs/platform_management_plan/verification_report/platform_ver_report.rst deleted file mode 100644 index c8f44d5678..0000000000 --- a/docs/platform_management_plan/verification_report/platform_ver_report.rst +++ /dev/null @@ -1,43 +0,0 @@ -.. - # ******************************************************************************* - # Copyright (c) 2026 Contributors to the Eclipse Foundation - # - # See the NOTICE file(s) distributed with this work for additional - # information regarding copyright ownership. - # - # This program and the accompanying materials are made available under the - # terms of the Apache License Version 2.0 which is available at - # https://www.apache.org/licenses/LICENSE-2.0 - # - # SPDX-License-Identifier: Apache-2.0 - # ******************************************************************************* - -Verification Report -=================== - - -.. document:: Platform Verification Report - :id: doc__platform_verification_report - :status: draft - :safety: ASIL_B - :security: NO - :realizes: wp__verification_platform_ver_report - :tags: - - - -In its final form (status = valid), Platform Verification Report must contain: - - - List of requirements (stakeholder and feature) and architecture tested by which test - (can be several levels), passed/failed and completeness verdict, including normal - operation and failure reactions - - The list of requirements may also contain other verification methods like "Analysis" - - Formal evidence about the Platform DFA - - Formal evidence about the performed Safety Analyses (if planned) - - Summary reports ("all passed" or OPs, justifications, planned actions etc.) for the above safety analyses - - Test result per test case from - :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - with status passed/failed/not_run - - Test log per test case from - :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - with status passed/failed/not_run diff --git a/docs/safety/fdr_reports_safety_analyses_DFA.rst b/docs/safety/fdr_reports_safety_analyses_DFA.rst index 8edab15001..4889206c42 100644 --- a/docs/safety/fdr_reports_safety_analyses_DFA.rst +++ b/docs/safety/fdr_reports_safety_analyses_DFA.rst @@ -13,8 +13,8 @@ # ******************************************************************************* - Safety Analysis Formal Review Report -===================================== +Safety Analysis Formal Review Report +==================================== .. document:: Safety Analysis Formal Review Report :id: doc__platform_safety_analysis_fdr diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index fe675bb3a1..8a3dd84d99 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Safety Package Formal Review Report -=================================== + Safety Package Formal Review Report + =================================== .. document:: Platform Safety Package Formal Review :id: doc__platform_safety_package_fdr diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 2daf0ed700..4c7197ab6e 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Safety Plan Formal Review Report -================================ + Safety Plan Formal Review Report + ================================ .. document:: S-CORE Platform Safety Plan Formal Review :id: doc__platform_safety_plan_fdr diff --git a/docs/safety/platform_dfa.rst b/docs/safety/platform_dfa.rst index ddcca70195..ccbd54e9bb 100644 --- a/docs/safety/platform_dfa.rst +++ b/docs/safety/platform_dfa.rst @@ -13,8 +13,8 @@ # ******************************************************************************* -Platform DFA (Dependent Failure Analysis) -========================================= + Platform DFA (Dependent Failure Analysis) + ========================================= .. document:: Platform DFA :id: doc__score_platform_dfa From 6003b4d211675458c6fa2e7d862af04a07a42f3a Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:29:29 +0100 Subject: [PATCH 16/25] issue 2501 fixed titles --- docs/safety/fdr_reports_safety_package.rst | 4 ++-- docs/safety/fdr_reports_safety_platform_safety_plan.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index 8a3dd84d99..fe675bb3a1 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* - Safety Package Formal Review Report - =================================== +Safety Package Formal Review Report +=================================== .. document:: Platform Safety Package Formal Review :id: doc__platform_safety_package_fdr diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 4c7197ab6e..2daf0ed700 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* - Safety Plan Formal Review Report - ================================ +Safety Plan Formal Review Report +================================ .. document:: S-CORE Platform Safety Plan Formal Review :id: doc__platform_safety_plan_fdr From 1a2b7fff6bda02a58e22c1a63896bdc39395b273 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Thu, 19 Feb 2026 17:33:05 +0100 Subject: [PATCH 17/25] issue 2501 titles fixes --- docs/safety/fdr_reports_safety_package.rst | 1 + docs/safety/fdr_reports_safety_platform_safety_plan.rst | 1 + docs/safety/platform_dfa.rst | 4 ++-- docs/safety/platform_safety_manual.rst | 5 +++-- 4 files changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/safety/fdr_reports_safety_package.rst b/docs/safety/fdr_reports_safety_package.rst index fe675bb3a1..fbd55b3db1 100644 --- a/docs/safety/fdr_reports_safety_package.rst +++ b/docs/safety/fdr_reports_safety_package.rst @@ -12,6 +12,7 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* + Safety Package Formal Review Report =================================== diff --git a/docs/safety/fdr_reports_safety_platform_safety_plan.rst b/docs/safety/fdr_reports_safety_platform_safety_plan.rst index 2daf0ed700..99961b8f46 100644 --- a/docs/safety/fdr_reports_safety_platform_safety_plan.rst +++ b/docs/safety/fdr_reports_safety_platform_safety_plan.rst @@ -12,6 +12,7 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* + Safety Plan Formal Review Report ================================ diff --git a/docs/safety/platform_dfa.rst b/docs/safety/platform_dfa.rst index ccbd54e9bb..ddcca70195 100644 --- a/docs/safety/platform_dfa.rst +++ b/docs/safety/platform_dfa.rst @@ -13,8 +13,8 @@ # ******************************************************************************* - Platform DFA (Dependent Failure Analysis) - ========================================= +Platform DFA (Dependent Failure Analysis) +========================================= .. document:: Platform DFA :id: doc__score_platform_dfa diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst index 419c376f37..4749025fa7 100644 --- a/docs/safety/platform_safety_manual.rst +++ b/docs/safety/platform_safety_manual.rst @@ -12,8 +12,9 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Safety Manual -============= + +Platform Safety Manual +====================== .. document:: Platform Safety Manual :id: doc__platform_safety_manual From 6aa267a83e8e3adac8f807a323bcd5b4e2471e0a Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 08:25:10 +0100 Subject: [PATCH 18/25] issue 2501 attifunel added further boldfaces for suggestions --- docs/safety/platform_safety_manual.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/safety/platform_safety_manual.rst b/docs/safety/platform_safety_manual.rst index 4749025fa7..2e9ed93edd 100644 --- a/docs/safety/platform_safety_manual.rst +++ b/docs/safety/platform_safety_manual.rst @@ -79,7 +79,7 @@ List of AoUs on the user of the platform features or the module of this safety m Safety concept of the SEooC --------------------------- -| <Describe here the safety concept incl. which faults are taken care of, reactions of the implemented functions under anomalous operating conditions ... if this is not already documented sufficiently in the feature documentation "safety impact" section of all the features the module is used in.> +| **<Describe here the safety concept incl. which faults are taken care of, reactions of the implemented functions under anomalous operating conditions ... if this is not already documented sufficiently in the feature documentation "safety impact" section of all the features the module is used in.>** Safety Anomalies ---------------- @@ -87,5 +87,5 @@ Safety Anomalies References ---------- -| <link to the user manual> -| <other links> +| **<link to the user manual>** +| **<other links>** From 54356442ca4a7916aa956d70d6b5302e8532ff87 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 08:31:13 +0100 Subject: [PATCH 19/25] 2501 fixed template request --- docs/safety/platform_ver_report.rst | 39 ++++++++++++++++++----------- 1 file changed, 24 insertions(+), 15 deletions(-) diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst index c2d56fdb53..6f43424d00 100644 --- a/docs/safety/platform_ver_report.rst +++ b/docs/safety/platform_ver_report.rst @@ -25,18 +25,27 @@ Platform Verification Report -In its final form (status = valid), Platform Verification Report must contain: - - - List of requirements (stakeholder and feature) and architecture tested by which test - (can be several levels), passed/failed and completeness verdict, including normal - operation and failure reactions - - The list of requirements may also contain other verification methods like "Analysis" - - Formal evidence about the performed DFA - - Formal evidence about the performed Safety Analyses (if planned) - - Summary reports ("all passed" or OPs, justifications, planned actions etc.) for the above safety analyses - - Test result per test case from - :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - with status passed/failed/not_run - - Test log per test case from - :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - with status passed/failed/not_run +**<In its final form (status = valid), Platform Verification Report must contain:>** + +**1. List of requirements and architecture tested** + + - List of requirements (stakeholder and feature) tested by which test + - List of architecture elements tested by which test (can be several levels) + - For all tests "passed/failed" shall be reported + - For all tests, completeness verdict shall be report, including normal operation and failure reactions + - The list of requirements may also contain other verification methods like “Analysis” + +**2. Safety analyses** + - Formal evidence about the performed DFA + - Formal evidence about the performed Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) + - Final statement resume (i.e. all passed, or are there open points, further actions needed, justifications etc.) + +**2. Integration test results** + - Test results per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) + - Test results per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) + - All test results shall include status ("passed/failed/not_run") + +**3. Integration test logs** + - Test log per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) + - Test log per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) + - All test results shall include status ("passed/failed/not_run") From e40eb452347c2617ecf61a2bb5f21bddbe578d55 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 08:39:30 +0100 Subject: [PATCH 20/25] 2501 attifunel added "Platform" --- docs/safety/platform_ver_report.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst index 6f43424d00..7c03695442 100644 --- a/docs/safety/platform_ver_report.rst +++ b/docs/safety/platform_ver_report.rst @@ -36,8 +36,8 @@ Platform Verification Report - The list of requirements may also contain other verification methods like “Analysis” **2. Safety analyses** - - Formal evidence about the performed DFA - - Formal evidence about the performed Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) + - Formal evidence about the performed Platform DFA + - Formal evidence about the performed Platform Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) - Final statement resume (i.e. all passed, or are there open points, further actions needed, justifications etc.) **2. Integration test results** From da8946d4d8f0891f7c0ad2dfb8481874e073204f Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 17:03:32 +0100 Subject: [PATCH 21/25] 2501 various fixes --- docs/index.rst | 1 + docs/release/index.rst | 25 ++++++++++++++ docs/release/platform_ver_report.rst | 51 ++++++++++++++++++++++++++++ docs/safety/index.rst | 3 +- 4 files changed, 78 insertions(+), 2 deletions(-) create mode 100644 docs/release/index.rst create mode 100644 docs/release/platform_ver_report.rst diff --git a/docs/index.rst b/docs/index.rst index 392d1a35a9..530fe441c6 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -106,6 +106,7 @@ Project structure and processes modules/index contribute/index safety/index + release/index Releases <score_releases/index.rst> Tools <score_tools/index.rst> diff --git a/docs/release/index.rst b/docs/release/index.rst new file mode 100644 index 0000000000..02f439c039 --- /dev/null +++ b/docs/release/index.rst @@ -0,0 +1,25 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +.. + +Release documentation +==================== + +Release specific documentation for Platform is listed here + +.. toctree:: + :maxdepth: 1 + + platform_ver_report.rst diff --git a/docs/release/platform_ver_report.rst b/docs/release/platform_ver_report.rst new file mode 100644 index 0000000000..7c03695442 --- /dev/null +++ b/docs/release/platform_ver_report.rst @@ -0,0 +1,51 @@ +.. + # ******************************************************************************* + # Copyright (c) 2026 Contributors to the Eclipse Foundation + # + # See the NOTICE file(s) distributed with this work for additional + # information regarding copyright ownership. + # + # This program and the accompanying materials are made available under the + # terms of the Apache License Version 2.0 which is available at + # https://www.apache.org/licenses/LICENSE-2.0 + # + # SPDX-License-Identifier: Apache-2.0 + # ******************************************************************************* + +Platform Verification Report +============================ + +.. document:: Platform Verification Report + :id: doc__platform_verification_report + :status: draft + :safety: ASIL_B + :security: NO + :realizes: wp__verification_platform_ver_report + :tags: + + + +**<In its final form (status = valid), Platform Verification Report must contain:>** + +**1. List of requirements and architecture tested** + + - List of requirements (stakeholder and feature) tested by which test + - List of architecture elements tested by which test (can be several levels) + - For all tests "passed/failed" shall be reported + - For all tests, completeness verdict shall be report, including normal operation and failure reactions + - The list of requirements may also contain other verification methods like “Analysis” + +**2. Safety analyses** + - Formal evidence about the performed Platform DFA + - Formal evidence about the performed Platform Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) + - Final statement resume (i.e. all passed, or are there open points, further actions needed, justifications etc.) + +**2. Integration test results** + - Test results per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) + - Test results per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) + - All test results shall include status ("passed/failed/not_run") + +**3. Integration test logs** + - Test log per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) + - Test log per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) + - All test results shall include status ("passed/failed/not_run") diff --git a/docs/safety/index.rst b/docs/safety/index.rst index 47efe5accf..4f4afbc0ee 100644 --- a/docs/safety/index.rst +++ b/docs/safety/index.rst @@ -21,10 +21,9 @@ Safety specific documentation for Platform is listed here .. toctree:: :maxdepth: 1 - + fdr_reports_safety_analyses_DFA fdr_reports_safety_package fdr_reports_safety_platform_safety_plan platform_dfa platform_safety_manual - platform_ver_report.rst From 8966cc87eae045c843a7d1f7139584d155cc739c Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 17:03:41 +0100 Subject: [PATCH 22/25] 2501 indent fix --- docs/safety/platform_ver_report.rst | 52 +++++++++++++++++------------ 1 file changed, 30 insertions(+), 22 deletions(-) diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst index 7c03695442..d226f7ee09 100644 --- a/docs/safety/platform_ver_report.rst +++ b/docs/safety/platform_ver_report.rst @@ -27,25 +27,33 @@ Platform Verification Report **<In its final form (status = valid), Platform Verification Report must contain:>** -**1. List of requirements and architecture tested** - - - List of requirements (stakeholder and feature) tested by which test - - List of architecture elements tested by which test (can be several levels) - - For all tests "passed/failed" shall be reported - - For all tests, completeness verdict shall be report, including normal operation and failure reactions - - The list of requirements may also contain other verification methods like “Analysis” - -**2. Safety analyses** - - Formal evidence about the performed Platform DFA - - Formal evidence about the performed Platform Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) - - Final statement resume (i.e. all passed, or are there open points, further actions needed, justifications etc.) - -**2. Integration test results** - - Test results per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) - - Test results per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) - - All test results shall include status ("passed/failed/not_run") - -**3. Integration test logs** - - Test log per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) - - Test log per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) - - All test results shall include status ("passed/failed/not_run") + **1. Verification Coverage** + + **1.1. on Requirements** + - Lists of stakeholder and feature requirements tested by which test case, passed/failed/not_run and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - For external component Assumptions of Use: coverage by platform safety manual + - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. + - List of stakeholder requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + + **1.2. on Architecture** + - List of feature architecture tags tested by which test case, passed/failed and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - This is split in a list of QM features tested and a separate list of tests for ASIL rated features. + - List of feature architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + + - The lists may also contain other verification methods + + **2. Safety Analyses Report** + - List of the performed Platform and Feature Safety Analyses, pass/fail with open mitigations + + **3. Test results** + - Test result per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + + **4. Test logs** + - Test log per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run + + **Note1: The verification report is valid for the platform version tagged together with the report** + + **Note2: All the above lists are generated automatically** From 817601a3d9f32b95e7631f6e2e29ec491239068a Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 17:08:53 +0100 Subject: [PATCH 23/25] 2501 fixed duplicate file --- docs/release/platform_ver_report.rst | 52 ++++++++++++++++------------ 1 file changed, 30 insertions(+), 22 deletions(-) diff --git a/docs/release/platform_ver_report.rst b/docs/release/platform_ver_report.rst index 7c03695442..d226f7ee09 100644 --- a/docs/release/platform_ver_report.rst +++ b/docs/release/platform_ver_report.rst @@ -27,25 +27,33 @@ Platform Verification Report **<In its final form (status = valid), Platform Verification Report must contain:>** -**1. List of requirements and architecture tested** - - - List of requirements (stakeholder and feature) tested by which test - - List of architecture elements tested by which test (can be several levels) - - For all tests "passed/failed" shall be reported - - For all tests, completeness verdict shall be report, including normal operation and failure reactions - - The list of requirements may also contain other verification methods like “Analysis” - -**2. Safety analyses** - - Formal evidence about the performed Platform DFA - - Formal evidence about the performed Platform Safety Analyses (this has to be compared against safety plan, i.e. needed only if FMEA actually planned on platform level) - - Final statement resume (i.e. all passed, or are there open points, further actions needed, justifications etc.) - -**2. Integration test results** - - Test results per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) - - Test results per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) - - All test results shall include status ("passed/failed/not_run") - -**3. Integration test logs** - - Test log per test case from Platform Integration Test (:need:`wp__verification_platform_int_test`) - - Test log per test case from Feature Integration test (:need:`wp__verification_feat_int_test`) - - All test results shall include status ("passed/failed/not_run") + **1. Verification Coverage** + + **1.1. on Requirements** + - Lists of stakeholder and feature requirements tested by which test case, passed/failed/not_run and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - For external component Assumptions of Use: coverage by platform safety manual + - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. + - List of stakeholder requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + + **1.2. on Architecture** + - List of feature architecture tags tested by which test case, passed/failed and completeness verdict + (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) + - This is split in a list of QM features tested and a separate list of tests for ASIL rated features. + - List of feature architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) + + - The lists may also contain other verification methods + + **2. Safety Analyses Report** + - List of the performed Platform and Feature Safety Analyses, pass/fail with open mitigations + + **3. Test results** + - Test result per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + + **4. Test logs** + - Test log per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` + with status passed/failed/not_run + + **Note1: The verification report is valid for the platform version tagged together with the report** + + **Note2: All the above lists are generated automatically** From beb1d89d090038b45dc548f91ec24f4bfaf38eb2 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 17:12:12 +0100 Subject: [PATCH 24/25] fixed further minor errors --- docs/release/index.rst | 2 +- docs/safety/platform_ver_report.rst | 59 ----------------------------- 2 files changed, 1 insertion(+), 60 deletions(-) delete mode 100644 docs/safety/platform_ver_report.rst diff --git a/docs/release/index.rst b/docs/release/index.rst index 02f439c039..4dfff31c60 100644 --- a/docs/release/index.rst +++ b/docs/release/index.rst @@ -15,7 +15,7 @@ .. Release documentation -==================== +===================== Release specific documentation for Platform is listed here diff --git a/docs/safety/platform_ver_report.rst b/docs/safety/platform_ver_report.rst deleted file mode 100644 index d226f7ee09..0000000000 --- a/docs/safety/platform_ver_report.rst +++ /dev/null @@ -1,59 +0,0 @@ -.. - # ******************************************************************************* - # Copyright (c) 2026 Contributors to the Eclipse Foundation - # - # See the NOTICE file(s) distributed with this work for additional - # information regarding copyright ownership. - # - # This program and the accompanying materials are made available under the - # terms of the Apache License Version 2.0 which is available at - # https://www.apache.org/licenses/LICENSE-2.0 - # - # SPDX-License-Identifier: Apache-2.0 - # ******************************************************************************* - -Platform Verification Report -============================ - -.. document:: Platform Verification Report - :id: doc__platform_verification_report - :status: draft - :safety: ASIL_B - :security: NO - :realizes: wp__verification_platform_ver_report - :tags: - - - -**<In its final form (status = valid), Platform Verification Report must contain:>** - - **1. Verification Coverage** - - **1.1. on Requirements** - - Lists of stakeholder and feature requirements tested by which test case, passed/failed/not_run and completeness verdict - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - For external component Assumptions of Use: coverage by platform safety manual - - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. - - List of stakeholder requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - - **1.2. on Architecture** - - List of feature architecture tags tested by which test case, passed/failed and completeness verdict - (this shall be generated by tools and accompanied by progress charts to be usable also for project steering) - - This is split in a list of QM features tested and a separate list of tests for ASIL rated features. - - List of feature architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export) - - - The lists may also contain other verification methods - - **2. Safety Analyses Report** - - List of the performed Platform and Feature Safety Analyses, pass/fail with open mitigations - - **3. Test results** - - Test result per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - - **4. Test logs** - - Test log per test case with status passed/failed/not_run for :need:`wp__verification_platform_int_test` and :need:`wp__verification_feat_int_test` - with status passed/failed/not_run - - **Note1: The verification report is valid for the platform version tagged together with the report** - - **Note2: All the above lists are generated automatically** From 5e786ca2deef792bcbc4ded6cc2c0cb9d3aff4b7 Mon Sep 17 00:00:00 2001 From: Attilio Stefano Funel <attiliostefano.funel@etas.com> Date: Tue, 24 Feb 2026 17:34:14 +0100 Subject: [PATCH 25/25] fix safety/index order --- docs/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.rst b/docs/index.rst index 530fe441c6..7949987b44 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -105,12 +105,12 @@ Project structure and processes requirements/index modules/index contribute/index - safety/index release/index Releases <score_releases/index.rst> Tools <score_tools/index.rst> PMP <platform_management_plan/index.rst> + safety/index Eclipse <https://projects.eclipse.org/projects/automotive.score> design_decisions/index