Final answer:
Whittaker's guidelines for defect testing involve establishing methods to find and fix software bugs, using strategies like random sampling and analyzing past defects to enhance software quality.
Step-by-step explanation:
Whittaker's guidelines for defect testing focus on establishing a process to identify and fix defects in a software product. The objective is to enhance the quality of the software by finding bugs that might not be apparent during initial testing phases. To do this effectively, Whittaker suggests devising targeted testing strategies that are likely to uncover the most significant and impactful defects.
One example of a guideline might be the use of random sampling, as mentioned with the survey results presented in Table 11.6. This technique involves randomly selecting a portion of the software to test, which can sometimes reveal defects that are less obvious or occur less frequently. Another common approach is to analyze past defects to identify patterns and potentially vulnerable areas within the application that require more focused testing.
Overall, Whittaker's approach encourages a thorough and systematic effort to uncover as many defects as possible before the software reaches the end user, thus saving time, resources, and enhancing user satisfaction with the final product.