Module Safety Plan#
Note
Document header
Baselibs Safety Plan
|
status: draft
safety: ASIL_B
|
||||
Functional Safety Management Context#
This Safety Plan adds to the Platform Safety Plan (doc__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 Module Documents. The module consists of one or more SW components and will be qualified as a SEooC.
Functional Safety Management Roles#
Role |
Assignee |
|---|---|
Safety Manager |
tbd |
Module Project Manager (= Feature team lead) |
Andrey Babanin |
Tailoring#
Additional to the tailoring in the SW platform project as defined in the Platform Safety Plan (doc__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): - wp__module_sw_build_config - Baselibs is a collection of libraries, so this work product is specific for every component.
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 issue |
Link to WP |
WP status |
|---|---|---|---|---|---|
valid |
this document |
see above |
|||
valid |
this document (including the linked documentation) |
see above (and below) |
|||
wp__fdr_reports (module Safety Plan) |
valid |
Baselibs Safety Plan Formal... (doc__baselibs_safety_plan_fdr) |
draft |
||
wp__fdr_reports (module Safety Package) |
valid |
Baselibs Safety Package For... (doc__baselibs_safety_package_fdr) |
draft |
||
wp__fdr_reports (module’s Safety Analyses & DFA) |
Safety Analysis FDR tbd |
<automated> |
<Link to issue> |
<Link to WP> |
<automated> |
performed by external experts |
n/a |
<Link to WP> |
<WP status (manual)> |
||
valid |
draft |
||||
valid |
Baselibs Verification Report (doc__baselibs_verification_report) |
draft |
|||
valid |
valid |
Component bitmanipulation Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
Bit Manipulation Requirements (doc__bitmanipulation_requirements) |
draft |
|||
valid |
<Link to issue> |
Bit Manipulation Requirements (doc__bitmanipulation_requirements) |
draft |
||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
bitmanipulation Architecture (doc__bitmanipulation_architecture) |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
n/a |
valid |
|||
valid |
n/a |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<manual> |
||
valid |
n/a |
component integration not needed (no sub-components and units are independent) |
n/a |
||
draft |
n/a |
valid |
Component containers Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
Containers Library Requirem... (doc__containers_lib_requirements) |
draft |
|||
valid |
<Link to issue> |
Containers Library Requirem... (doc__containers_lib_requirements) |
draft |
||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
valid |
||||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
n/a |
draft |
|||
valid |
n/a |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<manual> |
||
valid |
n/a |
component integration not needed (no sub-components and units are independent) |
n/a |
||
draft |
n/a |
valid |
Component filesystem Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
Filesystem Library Requirem... (doc__filesystem_lib_requirements) |
draft |
|||
valid |
<Link to issue> |
Filesystem Library Requirem... (doc__filesystem_lib_requirements) |
draft |
||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
draft |
||||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
n/a |
valid |
|||
valid |
n/a |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<manual> |
||
valid |
n/a |
component integration not needed (no sub-components and units are independent) |
n/a |
||
draft |
n/a |
valid |
Component result Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
n/a |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
valid |
||||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
n/a |
draft |
|||
valid |
n/a |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<manual> |
||
valid |
n/a |
component integration not needed (no sub-components and units are independent) |
n/a |
||
draft |
n/a |
valid |
Component json Work products List#
Work product Id |
Link to process |
Process status |
Link to issue |
Link to WP |
WP/doc status |
|---|---|---|---|---|---|
valid |
draft |
||||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
n/a |
draft |
|||
valid |
<Link to issue> |
<Link to WP> |
<automated> |
||
valid |
<Link to issue> |
draft |
|||
valid |
<Link to issue> |
draft |
|||
valid |
n/a |
valid |
|||
valid |
n/a |
valid |
|||
valid |
<Link to issue> |
<Link to WP> |
<manual> |
||
valid |
<Link to issue> |
<Link to WP> |
<automatic> |
||
draft |
n/a |
valid |
|||
valid |
draft |
All other components of the baselibs module as released in the Baselibs Release Note (doc__baselibs_release_note) are not planned to be qualifiable stand alone (as SEooC), but only in context, for example as they are used in other S-CORE modules (e.g. communication). To be qualifiable in context those come with unit tests, are implemented according to defined coding and detailed design guidelines, achieve the required structural coverage and fulfill the AoUs of the reference OS (e.g. don’t use banned functions).