Safety Checklist
How well can your organization answer these questions?
- For each safety-critical project undertaken by your organization, there is a coordinating committee or working group for managing the safety efforts.
0 - never 1 - occasionally 2 - frequently 3 - always
- Direct channels of communication exist between those responsible for safety and the rest of the project team.
0 - never 1 - occasionally 2 - frequently 3 - always
- There is a mechanism for all stakeholders to report safety-related concerns.
0 - never 1 - occasionally 2 - frequently 3 - always
- A safety plan exists that establishes the safety objectives and how they are to be achieved.
0 - never 1 - occasionally 2 - frequently 3 - always
- Safety activities are documented in an auditable form.
0 - never 1 - occasionally 2 - frequently 3 - always
- On completion of the project, a safety report summarizes the safety activities and provides a final risk assessment.
0 - never 1 - occasionally 2 - frequently 3 - always
- Potential hazards are identified.
0 - never 1 - occasionally 2 - frequently 3 - always
- Assessments are made of hazard severity and likelihood of occurrence.
0 - never 1 - occasionally 2 - frequently 3 - always
- Techniques such as fault—tree analysis and failure modes and effects analysis are used to analyze hazards.
0 - never 1 - occasionally 2 - frequently 3 - always
- Specific safety-related requirements are identified.
0 - never 1 - occasionally 2 - frequently 3 - always
- The requirements specification is analyzed for safety-related functionality.
0 - never 1 - occasionally 2 - frequently 3 - always
- The requirements specification is analyzed for missing, incomplete, inconsistent, ambiguous or conflicting requirements.
0 - never 1 - occasionally 2 - frequently 3 - always
- Safety design criteria and constraints are established.
0 - never 1 - occasionally 2 - frequently 3 - always
- The critical system components are identified and analyzed for potential hazard causes.
0 - never 1 - occasionally 2 - frequently 3 - always
- The critical software components are isolated, minimized and protected as much as possible.
0 - never 1 - occasionally 2 - frequently 3 - always
- Changes to the requirements, design or source code are evaluated for safety impact.
0 - never 1 - occasionally 2 - frequently 3 - always
- Static code analysis techniques, such as code inspections, are used to analyze the critical source code.
0 - never 1 - occasionally 2 - frequently 3 - always
- Safety-related testing is performed.
0 - never 1 - occasionally 2 - frequently 3 - always
- The user interface is evaluated for potential contributions to hazards.
0 - never 1 - occasionally 2 - frequently 3 - always
- Safe operational procedures are established.
0 - never 1 - occasionally 2 - frequently 3 - always |
阅读(1690) | 评论(0) | 转发(0) |
