Safety management process for changes

process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst

@@ -207,7 +207,7 @@ Note: In case the component is a new development, :need:`wp__sw_component_class`
 In case an OSS element is used in the module, part 6 has to be filled out.
 
 OSS (sub-)component qualification plan
-======================================
+--------------------------------------
 
 For the selected OSS component the following work products will be implemented (and why):
 
@@ -266,6 +266,11 @@ If the OSS element is classified as
           - :need:`gd_guidl__component_classification`
           - Always needed as basis for tailoring.
 
+Link to project planning
+------------------------
+
+<add here a link to your module's planning for the above work products, e.g. a link to a ticket.>
+
 Module Safety Package
 =====================
 

process/folder_templates/platform/docs/safety_mgt/platform_safety_plan.rst

@@ -163,6 +163,8 @@ Functional Safety Specific SW Platform Work Products
 List of all relevant work products for the platform project relevant for Functional Safety.
 Including their status (which makes it cover also the "safety package").
 
+Link to project planning: <add here a link to your project's planning for these work products, e.g. a link to a ticket.>
+
 Platform Safety Plan - Feature Work Product Lists
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

process/process_areas/safety_management/guidance/guideline_safety_management.rst

@@ -82,8 +82,8 @@ Safety Management Guideline
    **Planning safety activities:**
 
    In the safety plan the nomination of the safety manager and the project manager is documented.
-   The planning of safety activities is done using issues in the :need:`wp__issue_track_system` as specified in the :need:`wp__platform_mgmt`
-   It contains for each issue:
+   The planning of safety activities is done as for the project defined in the :need:`wp__project_mgt` by using issues in the :need:`wp__issue_track_system`.
+   It should contain for each issue:
 
    * objective - as part of the issue description
    * dependencies on other activities or information - by links to the respective issues
@@ -97,7 +97,21 @@ Safety Management Guideline
    * platform SEooC planning, dealing with all work products needed only once for the platform. This is included in :need:`wp__platform_safety_plan`
    * module SEooC planning, dealing with all work products needed for each module development (initiated by a change request), included in :need:`wp__module_safety_plan`. This module safety planning also includes the planning of OSS component qualification based on :need:`gd_guidl__component_classification`.
 
-   A template exists to guide this: :need:`gd_temp__module_safety_plan`.
+   Templates exists to guide this: :need:`gd_temp__platform_safety_plan`, :need:`gd_temp__module_safety_plan`.
+   These include linkage to the project planning according to the defined issue structuring schema.
+
+   **Reporting safety activities:**
+
+   Reporting is based on work products and documents status and supported by the safety plan templates and document management.
+   A safety plan is completed and the safety package can be released when all planned work products and documents are in status "valid".
+
+   **Planning safety activities for subsequent releases**
+
+   After the first release of the platform or a module with full safety coverage (i.e. all work products are in "valid" state) there will be further development.
+   This further development is initiated by creating a feature/component change request including a change impact analysis (see :need:`doc_concept__change_process`).
+   As part of the "implementation and monitoring of the change request", the documents affected by the change will be set back to "draft"
+   and the implementation (change of work products) planned by issues, as appropriate to the size of the change. At least the change request issue will be linked
+   to the updated safety plan. Note that there may be more than one change request for a module per release cycle.
 
    **Planning supporting processes:**