This preview shows page 1. Sign up to view the full content.
Unformatted text preview: risks and hazards
Ensure that mitigation/elimination methods can
be verified. Criteria for Successful Completion —The following items comprise a checklist to aid in determining
readiness of SSR product preparation: • Criteria for Successful Completion —The following items compose a checklist to aid in determining
readiness of SRR project preparation: Are cost estimates established and realistic?
Has a system verification concept been
Are appropriate plans being initiated to support
projected system development milestones?
Have the technology development issues been
identified along with approaches to their
solution? Have the risks been identified, characterized,
and quantified if needed?
Have design/procedural options been analyzed,
and quantified if needed to mitigate significant
Have verification methods been identified for
candidate options? Result of Review —A successful SSR results in
the identification of hazards and their causes in the proposed design and operational modes, and specific
means of eliminating, reducing, or controlling the
hazards. The methods of safety verification will also be
identified prior to PDR. At CDR, a safety baseline is
Software Specification Review.
Purpose — The Software Specification Review
(SoSR) ensures that the software specification set is
sufficiently mature to support preliminary design efforts. NASA Systems Engineering Handbook
Management Issues in Systems Engineering
Timing—Occurs shortly after the start of
Objectives—The review objectives are to:
• • • Verify that all software requirements from the
system specification have been allocated to
CSCls and documented in the appropriate
Verify that a complete set of functional,
requirements for each CSCI has been
Ensure that the software requirement set is both
complete and understandable. Criteria for Successful Completion —The following items comprise a checklist to aid in determining
View Full Document