Barb

• Oct 11th, 2011

 

A Quality gate is usually an activity that must be completed prior to acceptance of a deliverable or movement to the next step in the life cycle. Often they are set as milestones. For example a requirement document may have a peer review, a requirements traceability matrix, and a user review and sign off as part of the quality gate. A program or module specification may have a code review or code inspection as its quality gate.

mfsi_satyakamm

 Profile Answers by mfsi_satyakamm 

• Feb 7th, 2012

 

Hi,

Quality gates are situated inbetween two phases of a software project where the later phase depends on the outcome of its previous phase.
If the previous phase is a success, then only it can pass the quality gate and move to next phase.
Eg: Embedded software when transferred to hardware.

Thanks