Module Safety Plan#
Rust Base Libraries Safety Plan
|
status: draft
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 work products needed for ISO 26262 conformity.
Functional Safety Management Scope#
This Safety Plan’s scope is a SW module of the SW platform Module Documents. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management Roles#
Safety Manager |
<link to Module’s Safety Manager assignment or name> |
Project Manager |
<link to Module’s Project Manager assignment or name> |
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.
Excluded for this module are additionally the following work products (and their related requirements): - <ISO 26262 reference>: <work product/requirement> - <Argumentation why it is not needed or replaced by another work product or activity.>
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 issue |
Link to WP |
WP status |
|---|---|---|---|---|---|
valid |
<Link to issue> |
this document |
see above |
||
valid |
<Link to issue> |
this document (including the linked documentation) |
see above (and below) |
||
wp__fdr_reports (module Safety Plan) |
valid |
<Link to issue> |
Rust Base Libraries Safety ... (doc__baselibs_rust_safety_plan_fdr) |
draft |
|
wp__fdr_reports (module Safety Package) |
valid |
<Link to issue> |
Rust Base Libraries Safety ... (doc__baselibs_rust_safety_package_fdr) |
draft |
|
wp__fdr_reports (module’s Safety Analyses & DFA) |
Safety Analysis FDR tbd |
<automated> |
<Link to issue> |
<Link to WP> |
<automated> |
performed by external experts |
n/a |
<Link to issue> |
<Link to WP> |
<WP status (manual)> |
|
copy(‘status’, need_id=’gd_temp__software_development_plan’) |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
Rust Base Libraries Safety ... (doc__baselibs_rust_safety_manual) |
draft |
||
valid |
<Link to issue> |
Rust Base Libraries Verific... (doc__baselibs_rust_verification_report) |
draft |
||
valid |
<Link to issue> |
Rust Base Libraries Release... (doc__baselibs_rust_release_note) |
draft |
Component <name> Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
<Link to issue> |
doc draft & WP below |
|||
valid |
<Link to issue> |
doc draft & WP below |
|||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
<Link to issue> |
doc draft & WP below |
|||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
<Link to issue> |
doc draft & WP below |
|||
valid |
<Link to issue> |
doc draft & WP below |
|||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
n/a |
Checklist used in Pull Request Review |
n/a |
||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
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 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 work products additional to the component’s will be planned and activities below are part of the component’s issues.
Work product Id |
Link to issue |
Reasoning for tailoring |
|---|---|---|
<Link to issue> |
Always needed (for Q and QR classification) and also improves process Id 2 |
|
<Link to issue> |
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> |
|
<Link to issue> |
<Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms> |
|
<Link to issue> |
<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. |
|
<Link to issue> |
<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3> |
|
<Link to issue> |
<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2> |
|
<Link to issue> |
Always needed (for Q and QR classification) |
|
<Link to issue> |
Always needed as basis for tailoring. |
Work Product Status (for Safety Package)#
Component Requirements Status#
ID |
Status |
Tags |
|---|---|---|
invalid |
log |
Component AoU Status#
No needs passed the filters
Component Architecture Status#
No needs passed the filters