Skip to content

Classification planning in Safety Mgt Concept #594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
masc2023 merged 1 commit into from
Feb 27, 2026
Merged

Classification planning in Safety Mgt Concept #594

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions process/process_areas/safety_management/guidance/guideline_safety_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,9 @@ Safety Management Guideline
Based on the component classification as described in :need:`gd_guidl__component_classification`,
the qualification of the component is planned as part of the :need:`gd_temp__module_safety_plan`.
The template contains guidance how to do this and to document in the "OSS (sub-)component <name> Workproducts" list.
As an alternative the module safety manager can also decide to use the :ref:`external_tsf`
to reach enough trust in an externally provided (OSS) to use it for safety related functionality
in the scope of the SW platform. This approach is also documented in the module safety plan.


.. gd_guidl:: Safety manual generation
Expand Down
5 changes: 3 additions & 2 deletions process/process_areas/safety_management/safety_management_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,10 @@ Safety Management Work Products

Apart from the safety plans the main work products of Safety Management are:

* :need:`Safety Manual <wp__platform_safety_manual>` - the safety manual defines the requirements for safe usage or integration of the SW platform (or its individual modules)
* :need:`Safety Manual <wp__platform_safety_manual>` - defines the requirements for safe usage or integration of the SW platform (or its individual modules)
* :need:`Formal Document Review Reports <wp__fdr_reports>` - on safety plan, safety package and safety analyses, according to ISO 26262 requirements
* :need:`Safety Package <wp__platform_safety_package>` - the safety package contains the released work products planned in the safety plan, it does not contain the safety argumentation. By this the project ensures it does not take over liability for the SW platform (or its individual modules). But it enables the user to integrate the SW platform (or its individual modules) in their safety case.
* :need:`Safety Package <wp__platform_safety_package>` - contains the released work products planned in the safety plan, it does not contain the safety argumentation. By this the project ensures it does not take over liability for the SW platform (or its individual modules). But it enables the user to integrate the SW platform (or its individual modules) in their safety case.
* :need:`SW Component Classification <wp__sw_component_class>` - used for pre-existing software components, to determine their usability for safety funtionalities and the activities needed for its qualification in context of the SW platform. Is used as an input for the planning of SW component qualification documented in :need:`Module Safety Plan <wp__module_safety_plan>`.

Safety Management Tooling
^^^^^^^^^^^^^^^^^^^^^^^^^
Expand Down