Safety Plan Formal Review Report#
Note
Document header
Baselibs Safety Plan Formal Review
|
status: draft
safety: ASIL_B
|
||||
1. Purpose
The purpose of this safety plan formal review checklist is to report status of the review for the safety plan.
2. Checklist
Id |
Safety plan activity |
Compliant to ISO 26262? |
Comment |
|---|---|---|---|
1 |
Is the rationale for the safety work products tailoring included? |
[YES | NO ] |
<Rationale for result> |
2 |
Is impact analysis planned in case of re-use of SW (needed for every release following the first formal release)? |
[YES | NO ] |
<Rationale for result> |
3 |
Does the safety plan define all needed activities for safety management (incl. Confirmation review and Safety Audit)? |
[YES | NO ] |
<Rationale for result> |
4 |
Does the safety plan define all needed activities for System and SW development, integration and verification? |
[YES | NO ] |
<Rationale for result> |
5 |
Does the safety plan define all needed activities for safety analysis and DFA? |
[YES | NO ] |
<Rationale for result> |
6 |
Does the safety plan define all needed activities for supporting processes (incl. tool mgt)? |
[YES | NO ] |
<Rationale for result> |
7 |
Does the safety plan document a responsible for all activities? |
[YES | NO ] |
<Rationale for result> |
8 |
If OSS software components is used, is it planned to be qualified? |
[YES | NO ] |
<Rationale for result> |
9 |
Is a safety manager and a project manager appointed for the project? |
[YES | NO ] |
<Rationale for result> |
10 |
Is safety plan sufficiently linked to the project plan? |
[YES | NO ] |
<Rationale for result> |
11 |
Is safety plan updated iteratively to show the progress? |
[YES | NO ] |
<Rationale for result> |