Safety Compliance Report
- Safety Compliance Report
- the safety work product
that reports the results of the analysis and assessment of the success of the
endeavor’s
safety program
As illustrated in the preceding figure, Safety Compliance Report is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Document
- Subclasses:
The typical responsibilities of a Safety Compliance Report are to:
- Report the results of the
safety compliance assessment.
- Provide evidence of the success of the safety program.
- Justify certifying the safety of the application.
- Provide justification for starting the
safety certification task.
- Document the results of the
safety compliance assessment task.
The typical contents of a safety compliance report are:
- Evidence of Safety
- Compliance with the safety program plan.
- Compliance with safety risk analysis categories.
- Adequacy of accident investigations.
- Adequacy of safety requirements.
- Adequacy of safety mechanisms.
- Adequacy of safety reviews and safety audits.
- Adequacy of staffing, training, and tools.
- Appendices:
- Applicable Regulations, Laws, Certifications and
Standards
- Major Issues
- TBDs
- Assumptions
The typical stakeholders of a safety compliance report
are:
- Producer:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
A safety compliance report typically can be started if the
following preconditions hold:
A safety compliance report typically has the following
inputs:
- Work Products:
- Stakeholders:
- Scope.
The scope of a safety compliance report can be:
- A business unit
- A data or contact center
- An application
- A reusable component
- Any other system.
The safety compliance report is typically constrained by the following conventions:
-
Content and Format Standard
-
MS Word Template
-
XML DTD
-
Evaluation Checklist
-
Example Safety Compliance
Report
