Safety Plan#
Logging Module Safety Plan
|
status: draft
security: NO
safety: ASIL_B
|
||||
Functional Safety Management Context#
This Safety Plan adds to the project’s wp__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 <link to module documentation in platform/modules/<modulename>/index.rst>. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management Roles#
Role |
Assignee |
|---|---|
Safety Manager |
<link to Module’s Safety Manager assignment or name> |
Module Project Manager |
<link to Module’s Project Manager assignment or name> |
Tailoring#
Additional to the tailoring in the SW platform project as defined in the project’s wp__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):
<work product/requirement> - <Argumentation why it is not needed or replaced by another work product or activity.>
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 |
<Link to WP> |
|
wp__fdr_reports (module Safety Package) |
valid |
<Link to WP> |
|
wp__fdr_reports (module’s Safety Analyses & DFA) |
valid |
Logging Safety Analysis Che... (doc__logging_safety_analysis_fdr) |
|
performed by external experts |
n/a |
<Link to WP> |
|
valid |
|||
valid |
Logging Verification Report (doc__logging_verification_report) |
||
valid |
Component Logging Backend Work products List#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
Logging Backend Component R... (doc__logging_backend_requirements) |
||
valid |
Logging Backend Component AoU (doc__logging_backend_comp_aou) |
||
valid |
Logging Backend Requirement... (doc__logging_backend_req_inspection) |
||
valid |
Logging Backend Architecture (doc__logging_backend_architecture) |
||
valid |
tailored as no sub-components are defined |
||
valid |
|||
valid |
|||
valid |
|||
valid |
<Link to WP> |
||
valid |
Logging Backend Implementat... (doc__logging_backend_impl_inspection) |
||
valid |
<Link to WP> |
Note: the Data Router component is rated QM and therefore it is not planned here.
Link to project planning#
<add here a link to your module’s planning for the above work products, e.g. a link to a ticket.>
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 <add here the section reference to the 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.
See <add here the section reference to the documentation management plan>
Component Requirements Status#
No needs passed the filters
Component AoU Status#
No needs passed the filters
Component Architecture Status#
No needs passed the filters
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 workproduct 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.>