This preview shows page 1. Sign up to view the full content.
Unformatted text preview: uot;build-to" baseline sufficiently traceable to
assure that no orphan requirements exist?
Do the design qualification results from software
prototyping and engineering item testing,
simulation, and analysis support the conclusion
that the system will meet requirements?
Are all internal interfaces completely defined
and compatible? Are external interfaces
Are integrated safety analyses complete? Do
they show that identified hazards have been
controlled, or have those remaining risks which
cannot be controlled been waived by the
Are production plans in place and reasonable?
Are there adequate quality checks in the
Are the logistics support analyses adequate to
identify integrated logistics support resource
Are comprehensive system integration and
verifica tion plans complete? Results of Review — As a result of successful
completion of the CDR, the "build-to" baseline, production, and verification plans are approved. Approved
drawings are released and authorized for fabrication. It
also authorizes coding of deliverable software
(according to the "build-to" baseline and coding
standards presented in the review), and system
qualification testing and integration. All open issues
should be resolved with closure actions and schedules.
System Acceptance Review.
Purpose— The System Acceptance Review
(SAR) examines the system, its end items and
documentation, and test data and analyses that support
verification. It also ensures that the system has
sufficient technical maturity to authorize its shipment to
and installation at the launch site or the intended
Timing —Near the completion of the system
fabrication and integration stage.
Objectives—The objectives of the SAR are to:
• Establish that the system is ready to be
delivered and accepted under DD-250
Ensure that the system meets acceptance
criteria that were established at SDR
Establish that the system meets requirements
and will function properly in the expected • operational environments as reflected in the test
data, demonstrations, and analyses
Establish an understanding of the capabilities
and operational constraints of the ''as-built''
system, and that the documentation delivered
with the system is complete...
View Full Document