Abstract
It is clear that the critical success factor to lead the software development project is the quality of the specifications delivered from requirement specification phase. We often meet a fatal defect in the later phase though strict controls, validations or inspections for the specifications. Practically, many real projects tend to decide the end time when they should close their work through their experience. Those experiences frequently contain the substantial missing values. The purpose of this paper is to discuss the lack of viewpoint for exit criteria in requirement definition phase. I'd like to examine the quantitative verification of validity about phase exit criteria. What need to be emphasized in this approach is applying the classic quality engineering techniques such as "Reliability curve model" or "Defect prevention model" in programming or test phase to requirement engineering activities in project early phase. I found that defect visualization, quantification technique is so useful not only for programming or test debug phase but also requirement definition phase.
