Today when I was going through some testing web sites I came across "how to promote phase containment and defect prevention".
Frankly speaking i didn't understand what is it all about.
Can you please explain ?
Re: defect prevention
http://www.allpm.com/print.php?sid=985 says Phase containment's thesis is that project teams should diligently strive
to identify and fix problems at the earliest possible point in the development
life cycle. It is well established that the longer a problem persists, the more
costly it will be to eventually correct. (For example, it is far less costly
to correct an error in the architect�s drawing, than in the finished building).
As the probability of downstream faults grow, so does the likelihood that the
project will suffer substantial costs and delays. As applied to software projects,
phase containment measures the quantity of problems escaping the earliest possible
review (containment) points. The higher the number of escapes, the more likely
the project will experience delays, quality problems and/or cost overruns.
http://software.isixsigma.com/librar...t/c030910a.asp says "PCE tracks the ability of each phase to find defects before they escape that phase."
both links from a search on www.yahoo.com . A summary would be "Don't let your defects escape out of the phase they were generated in." If there is a requirement error, ensure that you find it during the requirements generation phase.
[ 06-29-2005, 03:50 PM: Message edited by: cyblue ]