Safety Plan#

score-crates Safety Plan		status: draft security: NO safety: ASIL_B
version: 0 realizes: wp__module_safety_plan

doc__score_crates_safety_plan		Generic Document

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 wp__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 - this moddule is a container for Rust libraries (crates). The module consists of one or more SW components and will be qualified as a SEooC.

Functional Safety Management Roles#

Table 1 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#

No addition to the tailoring in the SW platform project as defined in the project’s wp__platform_safety_plan.

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 2 Module Work products#
Work product 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	<Link to WP>
wp__fdr_reports (module Safety Package)	gd_chklst__safety_package	valid	<Link to WP>
wp__fdr_reports (module’s Safety Analyses & DFA)	gd_chklst__safety_analysis	valid	<Link to WP>
wp__audit_report	performed by external experts	n/a	<Link to WP>
wp__module_safety_manual	gd_temp__safety_manual	valid	<Link to WP>
wp__verification_module_ver_report	gd_temp__mod_ver_report	valid	score-crates Verification R... (doc__score_crates_verification_report)
wp__module_sw_release_note	gd_temp__rel_mod_rel_note	valid	<Link to WP>

Component Pastey Work products List#

Table 3 Component Pastey Work products#
Work product Id	Link to process	Process status	Link to WP
wp__requirements_comp	gd_temp__req_comp_req	valid	component_requirements.trlc
wp__requirements_comp_aou	gd_temp__req_aou_req	valid	aou.trlc
wp__requirements_inspect	gd_chklst__req_inspection	valid	<link to wp>
wp__component_arch	gd_temp__arch_comp	valid	Pastey Architecture (doc__mod_pastey_architecture)
wp__sw_arch_verification	gd_chklst__arch_inspection_checklist	valid	n/a (tailored)
wp__sw_component_fmea	gd_temp__comp_saf_fmea	valid	failure_modes.trlc
wp__sw_component_dfa	gd_temp__comp_saf_dfa	valid	n/a (tailored)
wp__sw_implementation	gd_guidl__implementation	valid	n/a (tailored)
wp__verification_sw_unit_test	gd_guidl__verification_guide	valid	n/a (tailored)
wp__sw_implementation_inspection	gd_chklst__impl_inspection_checklist	valid	n/a (tailored)
wp__verification_comp_int_test	gd_guidl__verification_guide	valid	pastey_test.rs
wp__sw_component_class	gd_guidl__component_classification	valid	Pastey Crate Component Clas... (doc__pastey_crate_comp_class)

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

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 4 OSS (sub-)component Pastey Work products#
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	needed
wf__cr_mt_comparch	gd_temp__arch_comp	It is small crate structure with one public interface, architecture view showing this shall be provided.
wp__sw_component_fmea	gd_temp__comp_saf_fmea	Safety analysis will be performed.
wp__sw_arch_verification	gd_chklst__arch_inspection_checklist	Tailored - Not needed due to simplicity.
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	Tailored - already provided by OSS component, see https://github.com/AS1100K/pastey/tree/master/pastey-test-suite
wp__sw_implementation_inspection	gd_chklst__impl_inspection_checklist	Tailored - OSS (design) documentation already exists, see https://docs.rs/pastey/0.2.3/pastey/
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 workproduct results, safety anomalies in the sense of known bugs in the software are reported in the release notes.