FEO Module Safety Plan
|
status: valid
security: NO
safety: ASIL_B
|
||||
FEO Module Safety Plan#
Functional Safety Management Context#
This Safety Plan adds to the Platform Safety Plan (doc__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 FEO Module Documents of the SW platform. 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) |
Johannes Glamsch |
Tailoring#
Additional to the tailoring in the SW platform project as defined in the Platform Safety Plan (doc__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): - No work products excluded
Functional Safety Module Work Products#
One set of work products for the module and one set for each component of the module:
FEO Module Work Products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP status |
|---|---|---|---|---|---|
valid |
this document |
see above |
|||
valid |
this document (including the linked documentation) |
see above (and below), safety manual |
|||
wp__fdr_reports (module Safety Plan) |
valid |
draft |
|||
wp__fdr_reports (module Safety Package) |
valid |
FEO Module Safety Package F... (doc__feo_safety_package_fdr) |
draft |
||
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
FEO Safety Analysis Inspect... (doc__safety_analysis_inspection_component_feo) |
draft |
||
performed by external experts |
n/a |
<Link to WP> |
<WP status (manual)> |
||
draft |
<Link to WP> |
<automated> |
|||
valid |
draft |
||||
valid |
FEO Module Verification Report (doc__feo_verification_report) |
draft |
|||
valid |
draft |
FEO Component Work Products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
FEO Component Requirements (doc__component_feo_requirements) |
doc draft & WP below |
|||
valid |
FEO Component Assumptions o... (doc__component_feo_aou_reqs) |
doc valid & WP below |
|||
valid |
FEO Component Requirements ... (doc__req_inspection_component_feo) |
doc draft |
|||
valid |
FEO Component Architecture (doc__component_feo_architecture) |
doc draft & WP below |
|||
valid |
FEO Component Architecture ... (doc__arch_inspection_component_feo) |
doc draft |
|||
valid |
doc draft & WP below |
||||
valid |
doc draft & WP below |
||||
valid |
<Link to WP> |
<automated> |
|||
valid |
<Link to WP> |
<automated> |
|||
valid |
FEO Implementation Inspecti... (doc__impl_inspection_component_feo) |
draft |
|||
valid |
<Link to WP> |
<automated> |
|||
valid |
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, depending on the component classification results.
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 |
|---|---|---|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
|
valid |
component_feo |
Component AoU Status#
ID |
Status |
Tags |
|---|---|---|
valid |
component_feo |
Component Architecture Status#
ID |
Status |
Tags |
|---|---|---|
valid |
component_feo |
|
valid |
component_feo |