Safety Status Report
- Safety Status Report
- the document
documenting the current status of the
safety program
As illustrated in the preceding figure, Safety Status Report is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Document
- Subclasses:
The typical responsibilities of a Safety Status Report is to:
- Document the current status of the safety program.
The typical contents of a safety status report are:
- TBD
- Appendices:
- Applicable Regulations, Laws, Certifications and
Standards
- Major Issues
- TBDs
- Assumptions
The typical stakeholders of the safety status report
are:
- Producer:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
- Management
- Legal Department
The safety status report typically can be started if the
following preconditions hold:
A safety status report typically has the following
inputs:
- Work Products:
- Stakeholders:
- Scope.
The scope of a safety status report can be:
- A business unit
- A data or contact center
- An application
- A reusable component
- Any other system.
The safety status report is typically constrained by the following conventions:
-
Content and Format Standard
-
MS Word Template
-
XML DTD
-
Evaluation Checklist
- Example Safety Status Report
