FEO Module Safety Plan
status: valid
security: NO
safety: ASIL_B
tags: module_feo

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#

Table 34 Module 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#

FEO Component Work Products List#

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.

Table 37 OSS (sub-)component score-crates Work products#

Work product Id

Reasoning for tailoring

wp__requirements_comp

Always needed (for Q and QR classification) and also improves process Id 2

wp__requirements_comp_aou

Always needed (for Q and QR classification) and also improves process Id 5

wp__requirements_inspect

<Reasoning for tailoring>

wf__cr_mt_comparch

<Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4>

wp__sw_component_fmea

<Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms>

wp__sw_arch_verification

<Reasoning for tailoring, needed if also wf__cr_mt_comparch is required>

wp__sw_implementation

Tailored - If source code is modified, this is not a OSS qualification any more.

wp__verification_sw_unit_test

<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3>

wp__sw_implementation_inspection

<Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2>

wp__verification_comp_int_test

Always needed (for Q and QR classification)

wp__sw_component_class

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.

See docs/modules/feo/docs

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 docs/modules/feo/components

Component Requirements Status#

ID

Status

Tags

comp_req__feo__activity

valid

component_feo

comp_req__feo__act_map_cfg

valid

component_feo

comp_req__feo__act_alloc_error

valid

component_feo

comp_req__feo__act_shutdown_error

valid

component_feo

comp_req__feo__act_startup_error

valid

component_feo

comp_req__feo__act_stepping_error

valid

component_feo

comp_req__feo__act_timeout

valid

component_feo

comp_req__feo__agent

valid

component_feo

comp_req__feo__alive_supervision

valid

component_feo

comp_req__feo__application_lifecycle

valid

component_feo

comp_req__feo__application

valid

component_feo

comp_req__feo__comp_cfg

valid

component_feo

comp_req__feo__comp_cfg_file

valid

component_feo

comp_req__feo__activity_init

valid

component_feo

comp_req__feo__activitiy_thread

valid

component_feo

comp_req__feo__response_term_request

valid

component_feo

comp_req__feo__scheduler

valid

component_feo

comp_req__feo__secondary_conn_timeout

valid

component_feo

comp_req__feo__service_activity

valid

component_feo

comp_req__feo__activity_shutdown

valid

component_feo

comp_req__feo__startup_timeout

valid

component_feo

comp_req__feo__activitiy_step

valid

component_feo

comp_req__feo__deadline_supervision

valid

component_feo

comp_req__feo__logical_supervision

valid

component_feo

comp_req__feo__task_chain

valid

component_feo

comp_req__feo__trustable_computation

valid

component_feo

Component AoU Status#

ID

Status

Tags

aou_req__component_feo__anything

invalid

component_feo

Component Architecture Status#

ID

Status

Tags

comp_arc_dyn__feo__main

valid

component_feo

comp_arc_sta__feo__main

valid

component_feo