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__score_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 |
Markus Schu |
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__score_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 WP |
|---|---|---|---|
valid |
this document |
||
valid |
this document (including the linked documentation) |
||
wp__fdr_reports (module Safety Plan) |
valid |
||
wp__fdr_reports (module Safety Package) |
valid |
FEO Module Safety Package F... (doc__feo_safety_package_fdr) |
|
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
FEO Safety Analysis Inspect... (doc__safety_analysis_inspection_component_feo) |
|
performed by external experts |
n/a |
<Link to WP> |
|
valid |
|||
valid |
FEO Module Verification Report (doc__feo_verification_report) |
||
valid |
FEO Component Work Products List#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
FEO Component Requirements (doc__component_feo_requirements) |
||
valid |
FEO Component Assumptions o... (doc__component_feo_aou_reqs) |
||
valid |
FEO Component Requirements ... (doc__req_inspection_component_feo) |
||
valid |
FEO Component Architecture (doc__component_feo_architecture) |
||
valid |
FEO Component Architecture ... (doc__arch_inspection_component_feo) |
||
valid |
|||
valid |
|||
valid |
<Link to WP> |
||
valid |
<Link to WP> |
||
valid |
FEO Implementation Inspecti... (doc__impl_inspection_component_feo) |
||
valid |
<Link to WP> |
As feo is using score-crates as OSS component, the following section should be filled out accordingly. This section is currently only a placeholder and needs to be adapted based on the progress of the OSS qualification.
OSS score-crates 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 |
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> |
|
<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 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.
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.
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 |
|---|---|---|
invalid |
component_feo |
Component Architecture Status#
ID |
Status |
Tags |
|---|---|---|
valid |
component_feo |
|
valid |
component_feo |