1. Purpose of the gate
Software validation sign-off is the engineering decision that the release candidate is good enough to become production software. It is separate from the production release itself on purpose: this gate asks whether the software works and meets its requirements, while Production software release asks whether everything needed to ship it to customers is in place. Keeping the two apart stops packaging and signing pressure from softening the quality judgement.
The criteria are a validation report in which every requirement is verified or waived, open defects within the release criteria in the quality plan, compliance test results passed for the claimed standards, and a release candidate frozen and tagged. Firmware, drivers and the board support package reach their final maturity here. The errata list and the software workarounds list become final too, because customers will design against them.
Hardware gates depend on this review in both directions. In the FPGA lifecycle, System validated waits for it, since system validation runs with the validated software release. In the automotive lifecycle, the review waits for Silicon validated, because software safety mechanisms must be validated on silicon whose own safety mechanisms have been tested; and Functional safety assessment complete waits for this gate, because software verification and process evidence go into the safety case the assessment reviews.
10 more sections for registered members.