Module Safety Plan#
Persistency Safety Plan
|
status: valid
security: NO
safety: ASIL_B
|
||||
- note:
The module safety plan shall be continuously maintained during the project. Deviations to the module safety plan are documented here.
Functional Safety Management Context#
This Safety Plan adds to the 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 Persistency Documentation. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management Roles#
Role |
Assignee |
|---|---|
Safety Manager |
Volker Häussler |
Module Project Manager (= Feature team lead) |
Uwe Maucher |
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 work products (and their related requirements):
none
Notes on the execution of the planned work products:
The component safety analyses (KVS FMEA (doc__kvs_fmea), KVS DFA (doc__kvs_dfa)) refer to the feature safety analyses, because the KVS component has no internal components (KVS Component Architecture (doc__kvs_component_architecture)).
The detailed design is captured in the source code (public API headers and traits, source code comments) according to gd_guidl__implementation. KVS Detailed Design (doc__kvs_detailed_design) documents the decomposition into units.
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#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
this document |
||
valid |
this document (including the linked documentation) |
||
wp__fdr_reports (module Safety Plan) |
valid |
Persistency Safety Plan For... (doc__persistency_safety_plan_fdr) |
|
wp__fdr_reports (module Safety Package) |
valid |
Persistency Safety Package ... (doc__persistency_safety_package_fdr) |
|
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
Persistency Safety Analysis... (doc__module_safety_analysis_fdr) |
|
performed by external experts |
n/a |
n/a |
|
valid |
|||
valid |
Persistency Module Verifica... (mod_vrep__persistency__report) |
||
valid |
|||
valid |
Component KVS Work products List#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
|||
valid |
|||
valid |
|||
valid |
KVS Component Architecture (doc__kvs_component_architecture) |
||
valid |
|||
valid |
|||
valid |
|||
valid |
KVS Detailed Design (doc__kvs_detailed_design) & source code |
||
valid |
Bazel test suites |
||
valid |
|||
valid |
Bazel test suites |
The KVS component is a new development, so no wp__sw_component_class is planned for it.
OSS (sub-)component qualification plan#
The Rust implementation of the KVS component uses the OSS crates tinyjson (JSON parsing and generation) and
adler32 (checksum). The C++ implementation uses the S-CORE baselibs only.
The classification of these OSS crates (wp__sw_component_class) and the resulting qualification plan are open, see Deviations from Module Safety Plan.
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” and in Persistency Documentation.
Component Documents Status#
For all the work product documents the status can be seen by following the “Link to WP” and in Component documentation.
Component Requirements Status#
ID |
Status |
|---|---|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
|
valid |
Component AoU Status#
No needs passed the filters
Component Architecture Status#
ID |
Status |
|---|---|
invalid |
|
invalid |
|
invalid |
|
valid |
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.
Work product |
Deviation |
Planned resolution |
|---|---|---|
The OSS crates |
Classify the crates or replace them by the baselibs interfaces in the Rust implementation. |