Module Safety Plan#
Communication Safety Plan
|
status: draft
security: NO
safety: ASIL_B
|
||||
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#
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#
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 |
Communication Safety Plan F... (doc__communication_safety_plan_fdr) |
|
wp__fdr_reports (module Safety Package) |
valid |
Communication Safety Packag... (doc__communication_safety_package_fdr) |
|
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
Communication Safety Analys... (doc__communication_safety_analysis_fdr) |
|
performed by external experts |
n/a |
see platform safety plan |
|
valid |
Communication Safety Manual (doc__communication_safety_manual) |
||
valid |
|||
valid |
Component LoLa Work products List#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
|||
valid |
same as for feature level |
||
valid |
partly tailored as several checks are automated, gap analysis tbd |
||
valid |
<https://github.com/eclipse-score/communication/tree/main/score/mw/com/dependability/software_architectural_design> |
||
valid |
partly tailored as several checks are automated, gap analysis tbd |
||
valid |
same as for feature level |
||
valid |
same as for feature level |
||
valid |
|||
valid |
|||
valid |
partly tailored as several checks are automated, gap analysis tbd |
||
valid |
|||
valid |
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.
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#
not documented as needs, lola trlc shows no status attribute
Component AoU Status#
ID |
Status |
Tags |
|---|---|---|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
valid |
communication |
|
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.>