Module Safety Plan#

Persistency Safety Plan		status: valid security: NO safety: ASIL_B
tags: persistency realizes: wp__module_safety_plan

doc__persistency_safety_plan		Generic Document

Functional Safety Management Context#

This Safety Plan adds to the wp__platform_safety_plan all the module development relevant workproducts needed for ISO 26262 conformity.

Functional Safety Management Scope#

This Safety Plan’s scope is a SW module of the SW platform Persistency Documentation. The module consists of one or more SW components and will be qualified as a SEooC.

Functional Safety Management Roles#

Table 2 Module roles#
Role	Assignee
Safety Manager	Volker Häussler
Module Project Manager (= Feature team lead)	Lars Bauhofer

Tailoring#

Additional to the tailoring in the SW platform project as defined in the wp__platform_safety_plan we define here the additional tailoring on module level.

- Excluded for this module are additionally the following workproducts (and their related requirements):

- Safety Analysis will not be performed on module level, because they are identical to the feature level.

Functional Safety Module Workproducts#

One set of workproducts for the module and one set for each component of the module:

Module Workproducts List#

Table 3 Module Workproducts#
Workproduct Id	Link to process	Process status	Link to WP
wp__module_safety_plan	gd_guidl__saf_plan_definitions	valid	this document
wp__module_safety_package	gd_guidl__saf_package	valid	this document (including the linked documentation)
wp__fdr_reports (module Safety Plan)	gd_chklst__safety_plan	valid	Persistency Safety Plan For... (doc__persistency_safety_plan_fdr)
wp__fdr_reports (module Safety Package)	gd_chklst__safety_package	valid	Persistency Safety Package ... (doc__persistency_safety_package_fdr)
wp__fdr_reports (module’s Safety Analyses & DFA)	gd_guidl__safety_analysis	valid	n/a because no safety analysis performed for the components. They will be overtaken from the feature.
wp__audit_report	performed by external experts	n/a	<Link to WP>
wp__module_safety_manual	gd_temp__safety_manual	valid	Persistency Safety Manual (doc__persistency_safety_manual)
wp__verification_module_ver_report	gd_temp__mod_ver_report	valid	Persistency Verification Re... (doc__persistency_verification_report)
wp__module_sw_release_note	gd_temp__rel_mod_rel_note	valid	Persistency Release Note (doc__persistency_release_note)

Component KVS Workproducts List#

Table 4 Component KVS Workproducts#
Workproduct Id	Link to process	Process status	Link to WP
wp__requirements_comp	gd_temp__req_comp_req	valid	KVS Requirements (doc__kvs_requirements)
wp__requirements_comp_aou	gd_temp__req_aou_req	valid	KVS Requirements (doc__kvs_requirements)
wp__requirements_inspect	gd_chklst__req_inspection	valid	Checklist used in Pull Request Review
wp__component_arch	gd_temp__arch_comp	valid	KVS Module Architecture (doc__kvs_architecture)
wp__sw_arch_verification	gd_chklst__arch_inspection_checklist	valid	Checklist used in Pull Request Review
wp__sw_component_fmea	wp__sw_component_fmea	valid	KVS FMEA (doc__kvs_fmea)
wp__sw_component_dfa	wp__sw_component_dfa	valid	KVS DFA (doc__kvs_dfa)
wp__sw_implementation	gd_guidl__implementation	valid	<Link to WP>
wp__verification_sw_unit_test	gd_guidl__verification_guide	valid	<Link to WP>
wp__sw_implementation_inspection	gd_chklst__impl_inspection_checklist	valid	Checklist used in Pull Request Review
wp__verification_comp_int_test	gd_guidl__verification_guide	valid	<Link to WP>
wp__sw_component_class	gd_guidl__component_classification	valid	JSON Component Classification (doc__json_comp_class)

OSS (sub-)component qualification plan#

For the selected OSS component the following workproducts 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 workproducts additional to the component’s will be planned and activities below are part of the component’s issues.

Table 5 OSS (sub-)component Tiny JSON Workproducts#
Work product Id	Link to process	Reasoning for tailoring
wp__requirements_comp	gd_temp__req_comp_req	Always needed (for Q and QR classification) and also improves process Id 2
wp__requirements_comp_aou	gd_temp__req_aou_req	Always needed (for Q and QR classification) and also improves process Id 5
wp__requirements_inspect	gd_chklst__req_inspection	<Reasoning for tailoring>
wf__cr_mt_comparch	gd_temp__arch_comp	<Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4>
wp__sw_component_fmea	gd_temp__comp_saf_fmea	<Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms>
wp__sw_arch_verification	gd_chklst__arch_inspection_checklist	<Reasoning for tailoring, needed if also wf__cr_mt_comparch is required>
wp__sw_implementation	n/a	Tailored - If source code is modified, this is not a OSS qualification any more.
wp__verification_sw_unit_test	gd_guidl__verification_guide	<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3>
wp__sw_implementation_inspection	gd_chklst__impl_inspection_checklist	<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2>
wp__verification_comp_int_test	gd_guidl__verification_guide	Always needed (for Q and QR classification)
wp__sw_component_class	gd_guidl__component_classification	Always needed as basis for tailoring.

Link to project planning#

Module Safety Package#

To create the safety package (according to 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 <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#

No needs passed the filters

Component AoU Status#

No needs passed the filters

Component Architecture Status#

No needs passed the filters

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 work product results, safety anomalies in the sense of known bugs in the software are reported in the release notes.