diff --git a/process/folder_templates/modules/module_name/component_name/docs/detailed_design/chklst_impl_inspection.rst b/process/folder_templates/modules/module_name/component_name/docs/detailed_design/chklst_impl_inspection.rst new file mode 100644 index 0000000000..2253721141 --- /dev/null +++ b/process/folder_templates/modules/module_name/component_name/docs/detailed_design/chklst_impl_inspection.rst @@ -0,0 +1,101 @@ +.. + # ******************************************************************************* + # 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 + # ******************************************************************************* + +.. document:: [Your Component Name] Implementation Inspection Checklist + :id: doc__component_name_impl_inspection + :status: draft + :safety: ASIL_B + :security: YES + :realizes: wp__sw_implementation_inspection + :tags: template + +.. attention:: + The above directive must be updated according to your Component. + + - Modify ``Your Component Name`` to be your Component Name + - Modify ``id`` to be your Component Name in lower snake case preceded by ``doc__`` and followed by ``_impl_inspection`` + - Adjust ``status`` to be ``valid`` + - Adjust ``safety``, ``security`` and ``tags`` according to your needs + +Implementation Inspection Checklist +=================================== + +Purpose +------- + +The purpose of this checklist is to collect the topics to be checked during implementation, +i.e. in the detailed design and the source code of the units. + +The checklist shall be agnostic to which programming language is used. Differences shall be treated +by linking to C++ or Rust specific documentation. + +Checklist +--------- + +.. list-table:: Implementation Checklist + :header-rows: 1 + :widths: 10,30,50,6,6,8 + + * - Review ID + - Acceptance Criteria + - Guidance + - Passed + - Remarks + - Issue link + * - IMPL_01_01 + - Is the design according to guidelines? + - see :need:`gd_temp__detailed_design` and :need:`doc_concept__imp_concept` + (e.g. are the views done with the proposed UML diagrams) + - + - + - + * - IMPL_01_02 + - Is the implementation according to specification? + - Check if the linked component requirements are fulfilled + and detailed design also matches architecture description. + - + - + - + * - IMPL_01_03 + - Are the design decisions and constraints documented? + - Check also for plausibility of these. + - + - + - + * - IMPL_01_04 + - Are all external libraries used by the component specified in the detailed design? + - Check the automated dependency analysis. + Also make sure ASIL rated units also only use ASIL rated libraries. + - + - + - + * - IMPL_02_01 + - Are the static and dynamic code analysis reports verified for violations? + - All violations in ASIL related code must be justified. This includes the checks of coding guidelines. + - + - + - + * - IMPL_02_02 + - Do manual checks, that are derived from the coding guideline, find no safety critical error? + - Check this for the programming language used (e.g. C++ , Rust ) + - + - + - + * - IMPL_02_03 + - Are detailed design and source code consistent? + - Check if the static and dynamic design descriptions match the code (e.g. naming of elements) + and that the respective traceability is established + - + - + - diff --git a/process/folder_templates/modules/module_name/component_name/docs/index.rst b/process/folder_templates/modules/module_name/component_name/docs/index.rst index c9e350be16..65c0da2137 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/index.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/index.rst @@ -178,6 +178,7 @@ Footnotes architecture/chklst_arc_inspection.rst component_classification.rst detailed_design/index.rst + detailed_design/chklst_impl_inspection.rst requirements/index.rst requirements/chklst_req_inspection.rst safety_analysis/fmea.rst diff --git a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst index 862c1cedde..e37d71a224 100644 --- a/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst +++ b/process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst @@ -83,79 +83,52 @@ Module Work products List * - Work product Id - Link to process - Process status - - Link to issue - Link to WP - - WP status * - :need:`wp__module_safety_plan` - :need:`gd_guidl__saf_plan_definitions` - :ndf:`copy('status', need_id='gd_guidl__saf_plan_definitions')` - - - this document - - see above * - :need:`wp__module_safety_package` - :need:`gd_guidl__saf_package` - :ndf:`copy('status', need_id='gd_guidl__saf_package')` - - - this document (including the linked documentation) - - see above (and below) * - :need:`wp__fdr_reports` (module Safety Plan) - :need:`gd_chklst__safety_plan` - :ndf:`copy('status', need_id='gd_chklst__safety_plan')` - - - :need:`doc__module_name_safety_plan_fdr` - - :ndf:`copy('status', need_id='doc__module_name_safety_plan_fdr')` * - :need:`wp__fdr_reports` (module Safety Package) - :need:`gd_chklst__safety_package` - :ndf:`copy('status', need_id='gd_chklst__safety_package')` - - - :need:`doc__module_name_safety_package_fdr` - - :ndf:`copy('status', need_id='doc__module_name_safety_package_fdr')` * - :need:`wp__fdr_reports` (module's Safety Analyses & DFA) - - Safety Analysis FDR tbd - - - - + - :need:`gd_chklst__safety_analysis` + - :ndf:`copy('status', need_id='gd_chklst__safety_analysis')` - - - * - :need:`wp__audit_report` - performed by external experts - n/a - - - - - - - * - :need:`wp__module_sw_release_note` - - :need:`gd_temp__software_development_plan` - - `copy('status', need_id='gd_temp__software_development_plan')` - - - - - - * - :need:`wp__module_safety_manual` - :need:`gd_temp__safety_manual` - :ndf:`copy('status', need_id='gd_temp__safety_manual')` - - - :need:`doc__module_name_safety_manual` - - :ndf:`copy('status', need_id='doc__module_name_safety_manual')` * - :need:`wp__verification_module_ver_report` - :need:`gd_temp__mod_ver_report` - :ndf:`copy('status', need_id='gd_temp__mod_ver_report')` - - - :need:`doc__module_name_verification_report` - - :ndf:`copy('status', need_id='doc__module_name_verification_report')` * - :need:`wp__module_sw_release_note` - :need:`gd_temp__rel_mod_rel_note` - :ndf:`copy('status', need_id='gd_temp__rel_mod_rel_note')` - - - :need:`doc__module_name_release_note` - - :ndf:`copy('status', need_id='doc__module_name_release_note')` Component Work products List ----------------------------------- @@ -166,93 +139,67 @@ Component Work products List * - Work product Id - Link to process - Process status - - Link to issue - Link to WP - - WP/doc status * - :need:`wp__requirements_comp` - :need:`gd_temp__req_comp_req` - :ndf:`copy('status', need_id='gd_temp__req_comp_req')` - - - :need:`doc__component_name_requirements` - - doc :ndf:`copy('status', need_id='doc__component_name_requirements')` & WP below * - :need:`wp__requirements_comp_aou` - :need:`gd_temp__req_aou_req` - :ndf:`copy('status', need_id='gd_temp__req_aou_req')` - - - :need:`doc__component_name_requirements` - - doc :ndf:`copy('status', need_id='doc__component_name_requirements')` & WP below * - :need:`wp__requirements_inspect` - :need:`gd_chklst__req_inspection` - :ndf:`copy('status', need_id='gd_chklst__req_inspection')` - - - :need:`doc__component_name_req_inspection` - - :ndf:`copy('status', need_id='doc__component_name_req_inspection')` * - :need:`wp__component_arch` - :need:`gd_temp__arch_comp` - :ndf:`copy('status', need_id='gd_temp__arch_comp')` - - - :need:`doc__component_name_architecture` - - doc :ndf:`copy('status', need_id='doc__component_name_architecture')` & WP below * - :need:`wp__sw_arch_verification` - :need:`gd_chklst__arch_inspection_checklist` - :ndf:`copy('status', need_id='gd_chklst__arch_inspection_checklist')` - - - :need:`doc__component_name_arc_inspection` - - :ndf:`copy('status', need_id='doc__component_name_arc_inspection')` * - :need:`wp__sw_component_fmea` - :need:`gd_temp__comp_saf_fmea` - :ndf:`copy('status', need_id='gd_temp__comp_saf_fmea')` - - - :need:`doc__component_name_fmea` - - doc :ndf:`copy('status', need_id='doc__component_name_fmea')` & WP below * - :need:`wp__sw_component_dfa` - :need:`gd_temp__comp_saf_dfa` - :ndf:`copy('status', need_id='gd_temp__comp_saf_dfa')` - - - :need:`doc__component_name_dfa` - - doc :ndf:`copy('status', need_id='doc__component_name_dfa')` & WP below * - :need:`wp__sw_implementation` - :need:`gd_guidl__implementation` - :ndf:`copy('status', need_id='gd_guidl__implementation')` - - - - - - + - :need:`doc__component_name_detailed_design` & * - :need:`wp__verification_sw_unit_test` - :need:`gd_guidl__verification_guide` - :ndf:`copy('status', need_id='gd_guidl__verification_guide')` - - - - - * - :need:`wp__sw_implementation_inspection` - :need:`gd_chklst__impl_inspection_checklist` - :ndf:`copy('status', need_id='gd_chklst__impl_inspection_checklist')` - - - - - - + - :need:`doc__component_name_impl_inspection` * - :need:`wp__verification_comp_int_test` - :need:`gd_guidl__verification_guide` - :ndf:`copy('status', need_id='gd_guidl__verification_guide')` - - - - - * - :need:`wp__sw_component_class` - :need:`gd_guidl__component_classification` - :ndf:`copy('status', need_id='gd_guidl__component_classification')` - - - :need:`doc__component_name_comp_class` - - :ndf:`copy('status', need_id='doc__component_name_comp_class')` Note: In case the component is a new development, :need:`wp__sw_component_class` shall be removed from the above list (and also from the folders). In case an OSS element is used in the module, part 6 has to be filled out. @@ -262,7 +209,7 @@ OSS (sub-)component qualification plan For the selected OSS component the following work products will be implemented (and why): -If the OSS element is classified as a +If the OSS element is classified as - component, then the below table shall match the above, adding the reasoning for tailoring of work products according to the OSS component classification. - lower level component, then no work products additional to the component’s will be planned and activities below are part of the component’s issues. @@ -270,55 +217,62 @@ If the OSS element is classified as a :header-rows: 1 * - Work product Id - - Link to issue - Reasoning for tailoring * - :need:`wp__requirements_comp` - - - Always needed (for Q and QR classification) and also improves process Id 2 * - :need:`wp__requirements_comp_aou` - - - Always needed (for Q and QR classification) and also improves process Id 5 * - :need:`wp__requirements_inspect` - - n/a - - Checklist used in Pull Request Review + - * - :need:`wf__cr_mt_comparch` - - - * - :need:`wp__sw_component_fmea` - - - * - :need:`wp__sw_arch_verification` - - - * - :need:`wp__sw_implementation` - - n/a - - If source code is modified, this is not a OSS qualification any more. + - Tailored - If source code is modified, this is not a OSS qualification any more. * - :need:`wp__verification_sw_unit_test` - - - * - :need:`wp__sw_implementation_inspection` - - - * - :need:`wp__verification_comp_int_test` - - - Always needed (for Q and QR classification) * - :need:`wp__sw_component_class` - - - Always needed as basis for tailoring. -Work Product Status (for Safety Package) -======================================== +Module Safety Package +===================== + +To create the safety package (according to :need:`gd_guidl__saf_package`) the following +documents and work products status have to go to "valid" (after the relevant verification were performed). + +Module Documents Status +----------------------- + +For all the work product documents the status can be seen by following the "Link to WP". +A summary of the status is also documented in the project's documentation management plan. + +See + +Component Documents Status +-------------------------- + +For all the work product documents the status can be seen by following the "Link to WP". +A summary of the status is also documented in the project's documentation management plan. + +See Component Requirements Status ----------------------------- diff --git a/process/process_areas/implementation/guidance/implementation_checklist.rst b/process/process_areas/implementation/guidance/implementation_checklist.rst index 333126aaca..9043851ae3 100644 --- a/process/process_areas/implementation/guidance/implementation_checklist.rst +++ b/process/process_areas/implementation/guidance/implementation_checklist.rst @@ -22,71 +22,6 @@ Implementation Inspection Checklist :tags: implementation :complies: std_req__iso26262__software_942 -Purpose -------- + For the content see here: -The purpose of this checklist is to collect the topics to be checked during implementation, -i.e. in the detailed design and the source code of the units. - -The checklist shall be agnostic to which programming language is used. Differences shall be treated -by linking to C++ or Rust specific documentation. - -Checklist ---------- - -.. list-table:: Implementation Checklist - :header-rows: 1 - :widths: 10,30,50,6,6,8 - - * - Review ID - - Acceptance Criteria - - Guidance - - Passed - - Remarks - - Issue link - * - IMPL_01_01 - - Is the design according to guidelines? - - see :need:`gd_temp__detailed_design` and :need:`doc_concept__imp_concept` - (e.g. are the views done with the proposed UML diagrams) - - - - - - - * - IMPL_01_02 - - Is the implementation according to specification? - - Check if the linked component requirements are fulfilled - and detailed design also matches architecture description. - - - - - - - * - IMPL_01_03 - - Are the design decisions and constraints documented? - - Check also for plausibility of these. - - - - - - - * - IMPL_01_04 - - Are all external libraries used by the component specified in the detailed design? - - Check the automated dependency analysis. - Also make sure ASIL rated units also only use ASIL or FFI rated libraries. - - - - - - - * - IMPL_02_01 - - Are the static and dynamic code analysis reports verified for violations? - - All violations in ASIL related code must be justified. This includes the checks of coding guidelines. - - - - - - - * - IMPL_02_02 - - Do manual checks, that are derived from the coding guideline, find no safety critical error? - - Check this list for C++ and this list for Rust - - - - - - - * - IMPL_02_03 - - Are detailed design and source code consistent? - - Check if the static and dynamic design descriptions match the code (e..g. naming of elements) - and that the respective traceability is established (doxygen style comments) - - - - - - + - :need:`doc__component_name_impl_inspection` diff --git a/process/process_areas/platform_management/platform_management_workflow.rst b/process/process_areas/platform_management/platform_management_workflow.rst index d2d9a8ea75..59a5ad25f4 100644 --- a/process/process_areas/platform_management/platform_management_workflow.rst +++ b/process/process_areas/platform_management/platform_management_workflow.rst @@ -27,7 +27,7 @@ For a detailed explanation of workflows and their role within the process model, :approved_by: rl__process_community :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager :input: wp__policies, wp__issue_track_system - :output: wp__platform_mgmt, wp__project_mgt, wp__document_mgt_plan, wp__config_mgt_plan, wp__prm_plan, wp__tlm_plan + :output: wp__platform_mgmt, wp__project_mgt, wp__document_mgt_plan, wp__config_mgt_plan, wp__prm_plan, wp__tlm_plan, wp__chm_plan :contains: gd_temp__platform_mgmt_plan, gd_guidl__platform_mgmt_plan, gd_guidl__documentation, gd_chklst__documentation_review, gd_temp__documentation :has: doc_concept__platform_process, doc_getstrt__platform_process diff --git a/process/process_areas/process_management/process_management_workflow.rst b/process/process_areas/process_management/process_management_workflow.rst index 355dead75c..f0e9cbb4ff 100644 --- a/process/process_areas/process_management/process_management_workflow.rst +++ b/process/process_areas/process_management/process_management_workflow.rst @@ -39,7 +39,7 @@ For a detailed explanation of workflows and their role within the process model, :approved_by: rl__process_community :supported_by: rl__external_auditor, rl__project_lead :input: wp__process_strategy, wp__issue_track_system - :output: wp__process_description + :output: wp__process_description, wp__tailoring_work_products :contains: gd_guidl__process_management, gd_temp__process_workflow :has: doc_concept__process_management, doc_getstrt__process_management diff --git a/process/process_areas/process_management/process_management_workproducts.rst b/process/process_areas/process_management/process_management_workproducts.rst index 24ae56f3e8..2586a785dd 100644 --- a/process/process_areas/process_management/process_management_workproducts.rst +++ b/process/process_areas/process_management/process_management_workproducts.rst @@ -38,5 +38,16 @@ Process Management Work Products :ref:`process_areas` as part of that representing the process definitions. +.. workproduct:: Tailoring Document Work Products + :id: wp__tailoring_work_products + :status: valid + :complies: std_wp__iso26262__management_651, std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522 + + This work product "definition" links to all the work products which are not covered by the + processes work products documented. Make sure these are tailored out in the safety, security and quality plans + for your project (documented in the PMP), to be able to demonstrate completeness. + It is not really a work product definition, + but this is the best way to link to the tailored out standard work products. + .. needextend:: docname is not None and "process_areas/process_management" in docname :+tags: process_management 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 d648cf12fb..3bcfbff16e 100644 --- a/process/process_areas/safety_management/guidance/guideline_safety_management.rst +++ b/process/process_areas/safety_management/guidance/guideline_safety_management.rst @@ -35,7 +35,7 @@ Safety Management Guideline ASPICE standard is selected for quality management. Processes will always link to the :ref:`standard_iso26262` standard and to the :ref:`ASPICE PAM4 ` standard. **Competence management:** - + The :need:`rl__project_lead` on SW platform level is responsible to define a competence management for the whole platform. Expectation is that the safety competence of the persons nominated for the roles is already given and only has to be checked. The exception from this are the committers, for these no safety competence needs to be enforced. @@ -115,14 +115,14 @@ Safety Management Guideline Verification planning is documented in :need:`wp__verification_plan` Any unspecified functions, such as code for debugging or instrumentation, must either be deactivated or removed prior to release, unless their presence does not affect safety compliance. - **Scheduling of formal document reviews, audit and assessment:** + **Scheduling of formal document reviews and safety audit:** Scheduling is done in the same way as for all work products definition by issues. The respective work products are :need:`wp__fdr_reports` and :need:`wp__audit_report` A person responsible for carrying out the functional safety audit shall be appointed as part of the scheduling process. This person has to have the required skillset and knowledge. The functional safety auditor may appoint one or more assistants to support the audit. These assistants may not be fully independent from the developers of the relevant item, elements, or work products, but must possess at least a basic level of independence. - The assessor is responsible for appraising the input from any assistants to ensure that the assessment remains objective and that an unbiased opinion is provided. - The planning and follow-up of the audit or assessment shall also take into account the type of report to be issued—whether it is an acceptance, conditional acceptance (with required corrective actions and conditions for acceptance), or a rejection. + The auditor is responsible for appraising the input from any assistants to ensure that the audit remains objective and that an unbiased opinion is provided. + The planning and follow-up of the audit shall also take into account the type of report to be issued—whether it is an acceptance, conditional acceptance (with required corrective actions and conditions for acceptance), or a rejection. Any conditions or corrective actions identified in the report must be addressed and tracked to completion as part of the Safety Management process. **Planning of dependent failures and safety analyses:** diff --git a/process/process_areas/safety_management/guidance/templates_safety_plan.rst b/process/process_areas/safety_management/guidance/templates_safety_plan.rst index 8c90c1a397..b58a099994 100644 --- a/process/process_areas/safety_management/guidance/templates_safety_plan.rst +++ b/process/process_areas/safety_management/guidance/templates_safety_plan.rst @@ -12,8 +12,8 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* -Safety Plan Templates -===================== +Safety Planning Templates +========================= .. gd_temp:: Feature Safety Work Products Template :id: gd_temp__feature_safety_wp diff --git a/process/process_areas/safety_management/safety_management_concept.rst b/process/process_areas/safety_management/safety_management_concept.rst index 5497e558d3..6de327cf19 100644 --- a/process/process_areas/safety_management/safety_management_concept.rst +++ b/process/process_areas/safety_management/safety_management_concept.rst @@ -43,10 +43,11 @@ Stakeholders * Main responsible to ensure ISO 26262 compliance in the project * Create/Maintain Safety Plan + * Perform Formal Reviews (for safety work products not in his resposibility area) * Approve Component Classification * Approve Safety Package * Approve Safety Audit - * Approve Formal Reviews + * Approve Formal Reviews (for safety work products in his resposibility area) * Approve Safety Manual * Monitor/Verify Safety * Impact Analysis of Change Request @@ -74,7 +75,6 @@ Stakeholders #. :need:`External Auditor ` * Perform Safety Audit as independent safety audits - * Perform Formal Reviews (e.g., safety plans, safety packages, safety analyses). * Verifies compliance with defined safety processes and standards. * Reports audit results and decides on pass/fail status. diff --git a/process/process_areas/safety_management/safety_management_roles.rst b/process/process_areas/safety_management/safety_management_roles.rst index bb8a8a5164..c8768d6d5a 100644 --- a/process/process_areas/safety_management/safety_management_roles.rst +++ b/process/process_areas/safety_management/safety_management_roles.rst @@ -42,7 +42,7 @@ Roles Experience - * 2 years of experience in the management of safety topics + * 3 years of experience in the management of safety topics * Experience in managing projects * Experience in managing safety anomalies @@ -56,7 +56,9 @@ Roles * Coaching the project team w.r.t all questions related to functional safety * Planning of safety audit * Approval of OSS component classification and safety analyses (incl. DFA) + * Approval of the Safety Package * Creating the safety manuals on platform and module level + * Performing/approval of formal document reviews on safety plans, safety package and safety analysis (incl. DFA) * Checking that every person in his team has sufficient safety skills for his role Authority @@ -80,7 +82,6 @@ Roles Responsibility * Performing and reporting of safety audit - * Performing of formal document reviews on safety plans, safety package and safety analysis (incl. DFA) Authority diff --git a/process/process_areas/safety_management/safety_management_workflow.rst b/process/process_areas/safety_management/safety_management_workflow.rst index 0ce923dd62..a5c0aab79a 100644 --- a/process/process_areas/safety_management/safety_management_workflow.rst +++ b/process/process_areas/safety_management/safety_management_workflow.rst @@ -22,8 +22,8 @@ Safety Management Workflows :status: valid :responsible: rl__safety_manager :approved_by: rl__project_lead - :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring - :output: wp__module_safety_plan, wp__platform_safety_plan + :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring_work_products + :output: wp__module_safety_plan, wp__platform_safety_plan, wp__safety_tailoring :contains: gd_guidl__saf_plan_definitions, gd_temp__feature_safety_wp, gd_temp__module_safety_plan :has: doc_concept__safety_management_process, doc_getstrt__safety_management_process @@ -48,7 +48,7 @@ Safety Management Workflows :status: valid :responsible: rl__safety_engineer :approved_by: rl__safety_manager - :input: wp__module_safety_plan, wp__platform_safety_plan, wp__issue_track_system + :input: wp__module_safety_plan, wp__platform_safety_plan, wp__issue_track_system, wp__safety_tailoring :output: wp__module_safety_package, wp__platform_safety_package :contains: gd_guidl__saf_package, gd_temp__feature_safety_wp, gd_temp__module_safety_plan :has: doc_concept__safety_management_process, doc_getstrt__safety_management_process @@ -76,17 +76,18 @@ Safety Management Workflows .. workflow:: Perform Formal Reviews :id: wf__p_formal_rv :status: valid - :responsible: rl__external_auditor + :responsible: rl__safety_manager :approved_by: rl__safety_manager :input: wp__module_safety_plan, wp__platform_safety_plan, wp__module_safety_package, wp__platform_safety_package :output: wp__fdr_reports :contains: gd_guidl__saf_plan_definitions, gd_chklst__safety_plan, gd_chklst__safety_package :has: doc_concept__safety_management_process, doc_getstrt__safety_management_process - | The external auditor is responsible to perform the formal reviews on safety plan, safety package and safety analysis. - | The Safety Manager shall support the external auditor during the reviews. - | The Project Manager and and the Safety Manager shall approve the formal reviews. - | Therefore a checklists exist to guide the creator of the relevant safety documents. + | A "external" safety manager is responsible the formal reviews on safety plan, safety package and safety analysis. + | "External" means here that the person is not the Safety Manager of the platform/module (i.e. created or approved the respective work product). + | The Safety Manager (of the platform/module) shall support the "external" safety manager during the reviews. + | The Safety Manager (of the platform/module) shall approve the formal reviews. + | A checklists exist to guide the creator of the relevant safety documents. .. workflow:: Create/Maintain Safety Manual :id: wf__cr_mt_safety_manual @@ -121,7 +122,7 @@ Safety Management Workflows :status: valid :responsible: rl__safety_manager :approved_by: rl__project_lead - :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring + :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__safety_tailoring :output: wp__issue_track_system :contains: gd_temp__change_component_request, gd_temp__change_decision_record, gd_temp__change_impact_analysis :has: doc_concept__safety_management_process diff --git a/process/process_areas/safety_management/safety_management_workproducts.rst b/process/process_areas/safety_management/safety_management_workproducts.rst index 782fffd41a..df1b75dc4a 100644 --- a/process/process_areas/safety_management/safety_management_workproducts.rst +++ b/process/process_areas/safety_management/safety_management_workproducts.rst @@ -123,11 +123,11 @@ Safety Management Work Products * finally a SW component classification as input for the safety planning (which is to cover the determined gaps, if any, by additional verification measures). .. workproduct:: Tailoring Documents - :id: wp__tailoring + :id: wp__safety_tailoring :status: valid :complies: std_wp__iso26262__management_653 - This work product argues why some work products are not needed in the project. + This work product argues why some safety work products are not needed in the project. It may have several levels: @@ -136,13 +136,6 @@ Safety Management Work Products It belongs to the Safety Plan. -.. workproduct:: Tailoring Document Work Products - :id: wp__tailoring_work_products - :status: valid - :complies: std_wp__iso26262__management_651, std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522 - This work product "definition" links to all the work products which are not covered by the - processes work products documented. Make sure these are tailored out in the safety plan - for your project (documented in the PMP), to be able to demonstrate completeness as described in :need:`gd_guidl__saf_package`. - It is not really a work product definition, - but this is the best way to link to the tailored out standard work products. +.. needextend:: docname is not None and "process_areas/safety_management" in docname + :+tags: safety_management diff --git a/process/process_areas/security_management/security_management_workflow.rst b/process/process_areas/security_management/security_management_workflow.rst index c8841e000e..8f08926cf7 100644 --- a/process/process_areas/security_management/security_management_workflow.rst +++ b/process/process_areas/security_management/security_management_workflow.rst @@ -24,7 +24,7 @@ For a detailed explanation of workflows and their role within the process model, :responsible: rl__security_manager :approved_by: rl__project_lead :supported_by: rl__safety_manager - :input: wp__platform_mgmt, wp__issue_track_system, wp__tailoring + :input: wp__platform_mgmt, wp__issue_track_system, wp__tailoring_work_products :output: wp__module_security_plan, wp__platform_security_plan :contains: gd_guidl__security_plan_definitions, gd_temp__feature_security_wp, gd_temp__module_security_plan :has: doc_concept__security_management_process, doc_getstrt__security_management_process