Module Safety Plan#

Communication Safety Plan
status: draft
security: NO
safety: ASIL_B
version: 2

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 of the SW platform: Communication Module. The module consists of one or more SW components and will be developed as a SEooC in S-CORE repository but with tooling and process different from S-CORE. It shall be used as a part of the S-CORE platform based on component classification.

Functional Safety Management Roles#

Table 87 Module roles#

Role

Assignee

Safety Manager

Alexander Schemmel

Module Project Manager (= Feature team lead)

Committers of feature team see Communication FT

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.

  • tailoring is as described in the work products lists based on the component classification.

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#

Component LoLa Work products List#

Table 89 Component mw_com Work products#

Work product Id

Link to process

Process status

Link to WP

wp__requirements_comp

gd_temp__req_comp_req

valid

eclipse-score/communication

wp__requirements_comp_aou

gd_temp__req_aou_req

valid

same as for feature level

wp__requirements_inspect

gd_chklst__req_inspection

valid

partly tailored as several checks are automated, gap analysis tbd

wp__component_arch

gd_temp__arch_comp

valid

<https://github.com/eclipse-score/communication/tree/main/score/mw/com/dependability/software_architectural_design>

wp__sw_arch_verification

gd_chklst__arch_inspection_checklist

valid

partly tailored as several checks are automated, gap analysis tbd

wp__sw_component_fmea

gd_temp__comp_saf_fmea

valid

same as for feature level

wp__sw_component_dfa

gd_temp__comp_saf_dfa

valid

same as for feature level

wp__sw_implementation

gd_guidl__implementation

valid

LoLa/.h/.cpp, LoLa/design

wp__verification_sw_unit_test

gd_guidl__verification_guide

valid

LoLa/test.cpp

wp__sw_implementation_inspection

gd_chklst__impl_inspection_checklist

valid

partly tailored as several checks are automated, gap analysis tbd

wp__verification_comp_int_test

gd_guidl__verification_guide

valid

LoLa/test

wp__sw_component_class

gd_guidl__component_classification

valid

LoLa Component Classification (doc__lola_comp_class)

Note: Name of the external component taken from Readme where it is stated as LoLa/mw::com but we abbreviate it to LoLa (as mw::com is mainly the namespace/api name).

Note2: Above links to communication repository are to the version as defined in reference integration.

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 Feature, module and component documentation

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 Feature, module and component documentation

Component Requirements Status#

not documented as needs, lola trlc shows no status attribute

Component AoU Status#

ID

Status

Tags

aou_req__communication__27

valid

communication

aou_req__communication__14

valid

communication

aou_req__communication__8

valid

communication

aou_req__communication__10

valid

communication

aou_req__communication__4

valid

communication

aou_req__communication__34

valid

communication

aou_req__communication__3

valid

communication

aou_req__communication__2

valid

communication

aou_req__communication__9

valid

communication

aou_req__communication__32

valid

communication

aou_req__communication__19

valid

communication

aou_req__communication__24

valid

communication

aou_req__communication__26

valid

communication

aou_req__communication__1

valid

communication

aou_req__communication__6

valid

communication

aou_req__communication__16

valid

communication

aou_req__communication__12

valid

communication

aou_req__communication__29

valid

communication

aou_req__communication__7

valid

communication

aou_req__communication__13

valid

communication

aou_req__communication__25

valid

communication

aou_req__communication__11

valid

communication

aou_req__communication__20

valid

communication

aou_req__communication__17

valid

communication

aou_req__communication__15

valid

communication

aou_req__communication__5

valid

communication

aou_req__communication__22

valid

communication

aou_req__communication__31

valid

communication

aou_req__communication__18

valid

communication

aou_req__communication__28

valid

communication

aou_req__communication__30

valid

communication

aou_req__communication__21

valid

communication

aou_req__communication__23

valid

communication

Deviations from Module Safety Plan#

The following deviations from the module safety plan are present in the module safety package. These are deviations from planned processes execution and/or work product results, safety anomalies in the sense of known bugs in the software are reported in the release notes.

<Describe here the deviations, whether they have an impact on module’s safety functions, how these can be mitigated or argued and if and when a resolution is planned.>