diff --git a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_package_fdr.rst b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_package_fdr.rst index 7afc66154b..744f45875f 100644 --- a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_package_fdr.rst +++ b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_package_fdr.rst @@ -53,29 +53,36 @@ See also :ref:`review_concept` for further information about reviews in general * - Id - Safety package activity - Compliant to ISO 26262? + - Reference - Comment * - 1 - Is a safety package provided which matches the safety plan (i.e. all planned work products referenced)? - [YES | NO ] + - :need:`[[title]] ` - * - 2 - Is the argument how functional safety is achieved, provided in the safety package, plausible and sufficient? - NO + - :need:`[[title]] ` - The argument is intentionally not provided by the project. * - 3 - Are the referenced work products available? - [YES | NO ] + - :need:`[[title]] ` - * - 4 - Are the referenced work products in released state, including the process safety audit? - [YES | NO ] + - :need:`[[title]] ` + :need:`[[title]] ` - * - 5 - If safety related deviations from the process or safety concept are documented, are these argued understandably? - [YES | NO ] + - :need:`[[title]] ` - diff --git a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan_fdr.rst b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan_fdr.rst index 674b11c5d4..5721604f55 100644 --- a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan_fdr.rst +++ b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan_fdr.rst @@ -52,59 +52,77 @@ See also :ref:`review_concept` for further information about reviews in general * - Id - Safety plan activity - Compliant to ISO 26262? + - Reference - Comment * - 1 - Is the rationale for the safety work products tailoring included? - [YES | NO ] + - :need:`[[title]] ` + :need:`[[title]] ` + :need:`[[title]] ` + :need:`[[title]] ` - * - 2 - Is impact analysis planned in case of re-use of SW (needed for every release following the first formal release)? - [YES | NO ] + - :need:`[[title]] ` - * - 3 - Does the safety plan define all needed activities for safety management (incl. formal document review and Safety Audit)? - [YES | NO ] + - :need:`[[title]] ` + :need:`[[title]] ` + :need:`[[title]] ` - * - 4 - Does the safety plan define all needed activities for System and SW development, integration and verification? - [YES | NO ] + - :need:`[[title]] ` - * - 5 - Does the safety plan define all needed activities for safety analysis and DFA? - [YES | NO ] + - :need:`[[title]] ` - * - 6 - Does the safety plan define all needed activities for supporting processes (incl. tool mgt)? - [YES | NO ] + - :need:`[[title]] ` - * - 7 - Does the safety plan document a responsible for all activities? - [YES | NO ] + - :need:`[[title]] ` - * - 8 - If OSS software components is used, is it planned to be qualified? - [YES | NO ] + - :need:`[[title]] ` - * - 9 - Is a safety manager and a project manager appointed for the project? - [YES | NO ] + - :need:`[[title]] ` + :need:`[[title]] ` - * - 10 - Is safety plan sufficiently linked to the project plan? - [YES | NO ] + - :need:`[[title]] ` - * - 11 - Is safety plan updated iteratively to show the progress? - [YES | NO ] + - :need:`[[title]] ` - diff --git a/process/process_areas/safety_management/guidance/checklist_safety_package.rst b/process/process_areas/safety_management/guidance/checklist_safety_package.rst index 59ace9a138..68a9df65f1 100644 --- a/process/process_areas/safety_management/guidance/checklist_safety_package.rst +++ b/process/process_areas/safety_management/guidance/checklist_safety_package.rst @@ -18,6 +18,6 @@ Safety Package Formal Review Checklist .. gd_chklst:: Safety Package Formal Review Checklist :id: gd_chklst__safety_package :status: valid - :complies: std_req__iso26262__management_5425, std_req__iso26262__management_6491, std_req__iso26262__management_6492, std_req__iso26262__management_6493, std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105 + :complies: std_req__iso26262__management_5425, std_req__iso26262__management_6469, std_req__iso26262__management_6481, std_req__iso26262__management_6482, std_req__iso26262__management_6491, std_req__iso26262__management_6492, std_req__iso26262__management_6493, std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105 For the content see here: :need:`doc__module_name_safety_package_fdr` diff --git a/process/process_areas/safety_management/guidance/checklist_safety_plan.rst b/process/process_areas/safety_management/guidance/checklist_safety_plan.rst index d9a183fdd0..39b8b7f35e 100644 --- a/process/process_areas/safety_management/guidance/checklist_safety_plan.rst +++ b/process/process_areas/safety_management/guidance/checklist_safety_plan.rst @@ -18,6 +18,6 @@ Safety Plan Formal Review Checklist .. gd_chklst:: Safety Plan Formal Review Checklist :id: gd_chklst__safety_plan :status: valid - :complies: std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105 + :complies: std_req__iso26262__management_6451, std_req__iso26262__management_6452, std_req__iso26262__management_6455, std_req__iso26262__management_6457, std_req__iso26262__management_6461, std_req__iso26262__management_6462, std_req__iso26262__management_6463, std_req__iso26262__management_6464, std_req__iso26262__management_6465, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6491, std_req__iso26262__management_64101, std_req__iso26262__management_64102, std_req__iso26262__management_64103, std_req__iso26262__management_64104, std_req__iso26262__management_64105, std_req__iso26262__management_64111 For the content see here: :need:`doc__module_name_safety_plan_fdr` diff --git a/process/process_areas/safety_management/guidance/guideline_safety_management.rst b/process/process_areas/safety_management/guidance/guideline_safety_management.rst index 92b3c9e9f0..2051f53571 100644 --- a/process/process_areas/safety_management/guidance/guideline_safety_management.rst +++ b/process/process_areas/safety_management/guidance/guideline_safety_management.rst @@ -20,7 +20,7 @@ Safety Management Guideline .. gd_guidl:: Safety plan definitions :id: gd_guidl__saf_plan_definitions :status: valid - :complies: std_req__iso26262__management_5426, std_req__iso26262__management_6465, std_req__iso26262__management_6466, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6469, std_req__iso26262__management_6422, std_req__iso26262__management_6423, std_req__iso26262__management_6424, std_req__iso26262__management_6451, std_req__iso26262__management_6452, std_req__iso26262__management_6453, std_req__iso26262__management_6454, std_req__iso26262__management_6455, std_req__iso26262__management_6456, std_req__iso26262__management_6457, std_req__iso26262__management_6461, std_req__iso26262__management_6462, std_req__iso26262__management_6463, std_req__iso26262__management_64610, std_req__iso26262__management_6472, std_req__iso26262__management_6471, std_req__iso26262__management_64111, std_req__iso26262__management_64112, std_req__iso26262__management_64113, std_req__iso26262__management_64114, std_req__iso26262__management_64121, std_req__iso26262__management_64122, std_req__iso26262__management_64123, std_req__iso26262__management_64124, std_req__iso26262__management_64125, std_req__iso26262__management_64126, std_req__iso26262__management_64127, std_req__iso26262__management_64128, std_req__iso26262__management_6431, std_req__iso26262__management_6432, std_req__iso26262__management_6433, std_req__iso26262__management_6454, std_req__iso26262__management_64129, std_req__iso26262__management_641210, std_req__iso26262__management_641211, std_req__iso26262__management_641212, std_req__iso26262__management_641213, std_req__iso26262__software_747, std_req__iso26262__support_8441, std_req__iso26262__management_5424, std_req__iso26262__management_5427, std_req__iso26262__management_5432, std_req__iso26262__management_5441, std_req__iso26262__management_5424, std_req__iso26262__management_5427, std_req__iso26262__management_5461, + :complies: std_req__iso26262__management_5426, std_req__iso26262__management_6465, std_req__iso26262__management_6466, std_req__iso26262__management_6467, std_req__iso26262__management_6468, std_req__iso26262__management_6469, std_req__iso26262__management_6422, std_req__iso26262__management_6423, std_req__iso26262__management_6424, std_req__iso26262__management_6451, std_req__iso26262__management_6452, std_req__iso26262__management_6455, std_req__iso26262__management_6457, std_req__iso26262__management_6461, std_req__iso26262__management_6462, std_req__iso26262__management_6463, std_req__iso26262__management_6472, std_req__iso26262__management_6471, std_req__iso26262__management_64111, std_req__iso26262__management_64112, std_req__iso26262__management_64113, std_req__iso26262__management_64114, std_req__iso26262__management_6431, std_req__iso26262__management_6432, std_req__iso26262__management_6433, std_req__iso26262__software_747, std_req__iso26262__support_8441, std_req__iso26262__management_5424, std_req__iso26262__management_5427, std_req__iso26262__management_5432, std_req__iso26262__management_5441, std_req__iso26262__management_5424, std_req__iso26262__management_5427, std_req__iso26262__management_5461, std_req__aspice_40__REU-2-BP1 **Safety culture:** @@ -172,7 +172,10 @@ Tailoring .. gd_guidl:: Safety Mgt Tailored :id: gd_guidl__saf_tailored :status: valid - :complies: std_req__iso26262__support_12423 + :complies: std_req__iso26262__support_12423, std_req__iso26262__management_6453, std_req__iso26262__management_6454, std_req__iso26262__management_6456, std_req__iso26262__management_64610, + std_req__iso26262__management_64121, std_req__iso26262__management_64122, std_req__iso26262__management_64123, std_req__iso26262__management_64124, std_req__iso26262__management_64125, + std_req__iso26262__management_64126, std_req__iso26262__management_64127, std_req__iso26262__management_64128, std_req__iso26262__management_64129, std_req__iso26262__management_641210, + std_req__iso26262__management_641211, std_req__iso26262__management_641212, std_req__iso26262__management_641213 This part of the guideline links to all the requirements which are not fulfilled by the safety management process. Make sure these are tailored out in the safety/security/quality plans @@ -180,4 +183,6 @@ Tailoring The reasoning is: - - The requirement is not applicable for an ASIL_B process + - for "support" standard requirements: The requirement is not applicable for an ASIL_B process + - for "management" standard requirements: 6453 - not proven in use argument, 6454 - no HW part of SW platform, 6456 - no confidence in use, 64610 - no distributed development + - for "management" standard requirements 6412*: No assessment planned, as also no finalized safety case is planned