Safety Certificate
- Safety Certificate
- the safety work product that certifies:
(1) that the system is acceptably safe to begin operation in its intended environment
(2) the success of the
endeavor’s
safety program
As illustrated in the preceding figure, Safety Certificate is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Document
- Subclasses:
The typical responsibilities of a Safety Certificate is to:
- Certify compliance with relevant driving documents.
- Reference evidence of compliance.
- Specify suitability for use.
- Provide a binding certification of compliance with safety program and related contractual standards.
- Document the results of the
safety certification task.
The typical contents of a safety certificate are:
- Front Matter:
- Certificate number
- Identification of the system being certified
- Configuration version
- Contract identifier
- Certification Criteria:
- Compliance with:
- Safety Program Plan
- Quality Plan
- Contractual Standards (e.g., military
standards)
- Requirements Specifications
- Evidence of Compliance:
- Safety Compliance Report
- Safety Log
- Suitability for Use:
- User Manuals
- List of Restrictions or Limitations
- Signatures (including name, position, and
date):
The typical stakeholders of the safety certificate are:
- Producer:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
The safety certificate typically can be started if the
following preconditions hold:
A safety certificate typically has the following inputs:
- Work Products:
- Stakeholders:
Guidelines
- Scope.
The scope of a safety certificate can be:
- A business unit
- A data or contact center
- An application
- A reusable component
- Any other system.
The safety certificate is typically constrained by the
following conventions:
-
Content and Format Standard
-
MS Word Template
-
XML DTD
-
Evaluation Checklist
-
Example Safety Certificate
