Module Safety Plan#

Persistency Safety Plan
status: valid
security: NO
safety: ASIL_B
tags: persistency
version: 2
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#

Table 5 Module 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.

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#

Component KVS Work products List#

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.

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

comp_req__kvs__async_api

valid

comp_req__kvs__atomic_store

valid

comp_req__kvs__cached_access

valid

comp_req__kvs__callback_support

valid

comp_req__kvs__concurrency

valid

comp_req__kvs__constraints

valid

comp_req__kvs__constraints_priority

valid

comp_req__kvs__corruption_detect_open

valid

comp_req__kvs__default_storage_permissions

valid

comp_req__kvs__default_val_chksum

valid

comp_req__kvs__default_value_cfg

valid

comp_req__kvs__default_value_cfg_tool

valid

comp_req__kvs__default_value_types

valid

comp_req__kvs__default_value_query

valid

comp_req__kvs__default_value_is_default_api

valid

comp_req__kvs__discard_pending_changes_api

valid

comp_req__kvs__explicit_flush

valid

comp_req__kvs__explicit_snapshot_operations

valid

comp_req__kvs__key_encoding

valid

comp_req__kvs__key_exists_api

valid

comp_req__kvs__key_length

valid

comp_req__kvs__key_list_api

valid

comp_req__kvs__key_naming

valid

comp_req__kvs__key_remove_api

valid

comp_req__kvs__key_uniqueness

valid

comp_req__kvs__key_value_overwrite

valid

comp_req__kvs__language_bindings

valid

comp_req__kvs__snapshot_max_num_cfg

valid

comp_req__kvs__multi_instance

valid

comp_req__kvs__no_dynamic_memory

valid

comp_req__kvs__open_need_kvs_behavior

valid

comp_req__kvs__os_abstraction

valid

comp_req__kvs__permission_control

valid

comp_req__kvs__permission_err_hndl

valid

comp_req__kvs__pers_data_migration

valid

comp_req__kvs__pers_data_schema

valid

comp_req__kvs__pers_data_store_bnd

valid

comp_req__kvs__pers_data_csum_vrfy

valid

comp_req__kvs__pers_data_csum

valid

comp_req__kvs__pers_data_store_fmt

valid

comp_req__kvs__pers_data_version

valid

comp_req__kvs__random_access_complexity

valid

comp_req__kvs__recovery_snapshot_restore

valid

comp_req__kvs__reset_resistant_write

valid

comp_req__kvs__single_process_access

valid

comp_req__kvs__snapshot_create

valid

comp_req__kvs__snapshot_create_api

valid

comp_req__kvs__snapshot_source

valid

comp_req__kvs__snapshot_overwrite

valid

comp_req__kvs__snapshot_remove_api

valid

comp_req__kvs__snapshot_restore_api

valid

comp_req__kvs__snapshot_slot_free_api

valid

comp_req__kvs__snapshot_slot_index_vali

valid

comp_req__kvs__snapshot_id_api

valid

comp_req__kvs__storage_backend_select

valid

comp_req__kvs__storage_file_permissions

valid

comp_req__kvs__storage_tool

valid

comp_req__kvs__store_reset_api

valid

comp_req__kvs__value_data_types

valid

comp_req__kvs__value_default

valid

comp_req__kvs__value_reset

valid

comp_req__kvs__value_get_api

valid

comp_req__kvs__value_serialize

valid

comp_req__kvs__value_set_api

valid

comp_req__kvs__write_amplification

valid

Component AoU Status#

No needs passed the filters

Component Architecture Status#

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.

Table 8 Deviations from the module safety plan#

Work product

Deviation

Planned resolution

wp__sw_component_class

The OSS crates tinyjson and adler32 used by the Rust implementation are not classified. The previous classification of Tiny JSON was removed with the change of the architecture to the baselibs JSON interface.

Classify the crates or replace them by the baselibs interfaces in the Rust implementation.