Module Safety Plan#
Note
Document header
[Your Module Name] Safety Plan
|
status: draft
security: NO
safety: ASIL_B
|
||||
Attention
The above directive must be updated according to your Module.
Modify
Your Module Nameto be your Module NameModify
idto be your Module Name in upper snake case preceded bydoc_and succeeded bysafety_planAdjust
statusto bevalidAdjust
safetyandtagsaccording to your needs
Functional Safety Management Context#
This Safety Plan adds to the project’s Platform Safety Plan (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 <link to module documentation in platform/modules/<modulename>/index.rst>. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management 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#
Additional to the tailoring in the SW platform project as defined in the project’s Platform Safety Plan (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):
<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 WP |
|---|---|---|---|
valid |
this document |
||
valid |
this document (including the linked documentation) |
||
Formal Document Review Reports (wp__fdr_reports) (module Safety Plan) |
valid |
[Your Module Name] Safety P... (doc__module_name_safety_plan_fdr) |
|
Formal Document Review Reports (wp__fdr_reports) (module Safety Package) |
valid |
[Your Module Name] Safety P... (doc__module_name_safety_package_fdr) |
|
Formal Document Review Reports (wp__fdr_reports) (module’s Safety Analyses & DFA) |
valid |
<Link to WP> |
|
performed by external experts |
n/a |
<Link to WP> |
|
valid |
[Your Module Name] Safety M... (doc__module_name_safety_manual) |
||
Module Verification Report (wp__verification_module_ver_report) |
valid |
[Your Module Name] Verifica... (doc__module_name_verification_report) |
|
valid |
[Your Module Name] Release ... (doc__module_name_release_note) |
Component <name> Work products List#
Note: In case the component is a new development, Software component classifi... (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.
Work product Id |
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 |
|
<Reasoning for tailoring> |
|
<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> |
|
Tailored - 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> |
|
Implementation Inspection (wp__sw_implementation_inspection) |
<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. |
Module Safety Package#
To create the safety package (according to Safety package automated ge... (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#
ID |
Status |
Tags |
|---|---|---|
invalid |
component_name |
Component AoU Status#
ID |
Status |
Tags |
|---|---|---|
invalid |
environment; component_name |
|
invalid |
component_name |
Component Architecture Status#
ID |
Status |
Tags |
|---|---|---|
invalid |
component_name |
|
invalid |
component_name |
|
invalid |
component_name |