Safety Plan#

Note

Document header

[Your Module Name] Safety Plan		status: draft security: NO safety: ASIL_B
tags: template realizes: wp__module_safety_plan

doc__module_name_safety_plan		Generic Document

Attention

The above directive must be updated according to your Module.

Modify Your Module Name to be your Module Name
Modify id to be your Module Name in upper snake case preceded by doc_ and succeeded by safety_plan
Adjust status to be valid
Adjust safety and tags according to your needs

note:: The module safety plan shall be continuously maintained during the project. Deviations to the module safety plan should be documented here

Functional Safety Management Context#

This Safety Plan adds to the project’s Platform Safety Plan all the module development relevant work products needed for ISO 26262 conformity.

Functional Safety Management Scope#

This Safety Plan’s scope is a SW module of the SW platform <link to module documentation in platform/modules/<modulename>/index.rst>. The module consists of one or more SW components and will be qualified as a SEooC.

Functional Safety Management Roles#

Table 59 Module roles#
Role	Assignee
Safety Manager	<link to Module’s Safety Manager assignment or name>
Module Project Manager	<link to Module’s Project Manager assignment or name>

Tailoring#

Additional to the tailoring in the SW platform project as defined in the project’s Platform Safety Plan we define here the additional tailoring on module level.

Excluded for this module are additionally the following work products (and their related requirements):
- <work product/requirement> - <Argumentation why it is not needed or replaced by another work product or activity.>

Functional Safety Module Work products#

One set of work products for the module and one set for each component of the module:

Module Work products List#

Table 60 Module Work products#
Work product Id	Link to process	Process status	Link to WP
Module Safety Plan	Safety plan definitions	valid	this document
Module Safety Package	Safety package automated ge...	valid	this document (including the linked documentation)
Formal Document Review Reports (module Safety Plan)	Safety Plan Formal Review C...	valid	[Your Module Name] Safety P...
Formal Document Review Reports (module Safety Package)	Safety Package Formal Revie...	valid	[Your Module Name] Safety P...
Formal Document Review Reports (module’s Safety Analyses & DFA)	Safety Analysis Checklist T...	valid	<Link to WP>
Process Safety Audit Report	performed by external experts	n/a	<Link to WP>
Module Safety Manual	Safety Manual Template	valid	[Your Module Name] Safety M...
Module Verification Report	Module Verification Report ...	valid	[Your Module Name] Verifica...
Module Release Notes	Module Release Note Template	valid	[Your Module Name] Release ...

Component <name> Work products List#

Table 61 Component <name> Work products#
Work product Id	Link to process	Process status	Link to WP
Component Requirements	Component Requirements Temp...	valid	[Your Component Name] Requi...
Component Assumptions of Use	AoU Requirement Template	valid	[Your Component Name] Requi...
Requirements Inspection	Requirements Inspection Che...	valid	[Your Component Name] Requi...
Component Architecture	Component Architecture Temp...	valid	[Your Component Name] Archi...
Architecture Verification	Architecture Inspection Che...	valid	[Your Component Name] Archi...
Component FMEA	Component FMEA Template	valid	[Your Component Name] FMEA
Component DFA	Component DFA Templates	valid	[Your Component Name] DFA
Implementation	Implementation Guideline	valid	[Your Component Name] Detai... & <Link to code>
Unit test	Verification Guideline	valid	<Link to WP>
Implementation Inspection	Implementation Inspection C...	valid	[Your Component Name] Imple...
Component Integration test	Verification Guideline	valid	<Link to WP>
Software component classifi...	Classification of a component	valid	[Your Component Name] Compo...

Note: In case the component is a new development, Software component classifi... 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.

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

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.

Table 62 OSS (sub-)component <name> Work products#
Work product Id	Link to process	Reasoning for tailoring
Component Requirements	Component Requirements Temp...	Always needed (for Q and QR classification) and also improves process Id 2
Component Assumptions of Use	AoU Requirement Template	Always needed (for Q and QR classification) and also improves process Id 5
Requirements Inspection	Requirements Inspection Che...	<Reasoning for tailoring>
Create/Maintain Components ...	Component Architecture Temp...	<Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4>
Component FMEA	Component FMEA Template	<Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms>
Architecture Verification	Architecture Inspection Che...	<Reasoning for tailoring, needed if also wf__cr_mt_comparch is required>
Implementation	n/a	Tailored - If source code is modified, this is not a OSS qualification any more.
Unit test	Verification Guideline	<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3>
Implementation Inspection	Implementation Inspection C...	<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2>
Component Integration test	Verification Guideline	Always needed (for Q and QR classification)
Software component classifi...	Classification of a component	Always needed as basis for tailoring.

Module Safety Package#

To create the safety package (according to Safety package automated ge...) 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 <add here the section reference to the documentation management plan>

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 <add here the section reference to the documentation management plan>

Component Requirements Status#

ID	Status	Tags
comp_req__component_name__some_title	invalid	component_name

Component AoU Status#

ID	Status	Tags
aou_req__component_name__another_title	invalid	environment; component_name
aou_req__component_name__next_title	invalid	component_name

Component Architecture Status#

ID	Status	Tags
comp_arc_sta__component_name__static_view	invalid	component_name
comp_arc_sta__component_name__2	invalid	component_name
comp_arc_dyn__component_name__dynamic_view	invalid	component_name

Deviations from Module Safety Plan#

The following deviations from the module safety plan are present in the module safety package. These are deviations from planned processes execution and/or workproduct results, safety anomalies in the sense of known bugs in the software are reported in the release notes.