Module Safety Plan#
Persistency Safety Plan
|
status: valid
security: NO
safety: ASIL_B
|
||||
Functional Safety Management Context#
This Safety Plan adds to the gd_guidl__saf_plan_definitions 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 Module Documents Persistency. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management Roles#
Role |
Assignee |
|---|---|
Safety Manager |
tbd |
Module Project Manager (= Feature team lead) |
Lars Bauhofer |
Tailoring#
Additional to the tailoring in the SW platform project as defined in the gd_guidl__saf_plan_definitions we define here the additional tailoring on module level.
Functional Safety Module Workproducts#
One set of workproducts for the module and one set for each component of the module:
Module Workproducts List#
Workproduct Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP status |
|---|---|---|---|---|---|
valid |
this document |
valid |
|||
valid |
this document (including the linked documentation) |
valid |
|||
wp__fdr_reports (module Safety Plan) |
valid |
Persistency Safety Plan For... (doc__persistency_safety_plan_fdr) |
valid |
||
wp__fdr_reports (module Safety Package) |
valid |
Persistency Safety Package ... (doc__persistency_safety_package_fdr) |
valid |
||
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
valid |
|||
performed by external experts |
n/a |
<Link to issue> |
<Link to WP> |
<WP status (manual)> |
|
gd_temp__software_development_plan |
copy(‘status’, need_id=’doc__software_development_plan’) |
<Link to issue> |
<Link to WP> |
<automated> |
|
valid |
valid |
||||
valid |
Persistency Verification Re... (doc__persistency_verification_report) |
valid |
|||
valid |
<Link to issue> |
valid |
Component <name> Workproducts List#
Workproduct Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
Persistency KVS Module Requ... (doc__persistency_kvs_requirements) |
valid & WP below |
|||
valid |
Persistency KVS Module Requ... (doc__persistency_kvs_requirements) |
valid & WP below |
|||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
Persistency KVS Module Arch... (doc__persistency_kvs_architecture) |
valid & WP below |
|||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
valid & WP below |
||||
valid |
valid & WP below |
||||
valid |
<Link to WP> |
<automated> |
|||
valid |
<Link to WP> |
<automated> |
|||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
<Link to WP> |
<automated> |
|||
valid |
Persistency Component Class... (doc__persistency_component_classification) |
valid |
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 workproducts will be implemented (and why):
- If the OSS element is classified as a
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.
Workproduct Id |
Link to issue |
Reasoning for tailoring |
|---|---|---|
Always needed (for Q and QR classification) and also improves process Id 2 |
||
Always needed (for Q and QR classification) and also improves process Id 5 |
||
n/a |
Checklist used in Pull Request Review |
|
<Link to issue> |
<Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4> |
|
<Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms> |
||
<Reasoning for tailoring, needed if also wf__cr_mt_comparch is required> |
||
n/a |
If source code is modified, this is not a OSS qualification any more. |
|
<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3> |
||
<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2> |
||
Always needed (for Q and QR classification) |
||
Always needed as basis for tailoring. |
Work Product Status (for Safety Package)#
Component Requirements Status#
No needs passed the filters
Component AoU Status#
ID |
Status |
Tags |
|---|---|---|
valid |
environment; persistencykvs; persistency |
|
valid |
environment; persistencykvs; persistency |
|
valid |
environment; persistencykvs; persistency |
Component Architecture Status#
No needs passed the filters