The main objectives the senior management team wants to achieve are: - to reduce the costs associated with dynamic testing - to use reviews to ensure…

The senior management objectives require a multi-faceted approach. A "formal" review process aligns with the need for well-defined roles and effective, documented bug removal. This addresses the cost reduction objective by finding defects earlier than dynamic testing. The most critical objectives are to determine and improve "phase containment effectiveness." This metric specifically measures the percentage of defects found in the same phase they were introduced. To calculate this, it is essential to perform an analysis of defects found throughout the lifecycle (including dynamic testing) to determine their phase of origin. Option D is the only choice that correctly combines formal reviews with this specific type of analysis.

A. "Lightweight" reviews contradict the stated objective for a formal process with well-defined roles and documentation.
B. Analyzing for defect clusters is a valid activity, but it does not directly address the specific objective of measuring phase containment effectiveness.
C. Using defect analysis to determine the people responsible is a counter-productive practice that focuses on blame rather than process improvement.

1. ISTQB® Certified Tester Advanced Level Test Manager Syllabus v3.1.1 (2023).

Section 5.6, "Using Defect Report Information for Process Improvement," p. 53: This section explicitly supports the correct answer by stating, "The analysis may also be used to identify the root causes of defects and the phase in which the defect was introduced." This is the core of measuring phase containment.

Section 5.6, p. 53: This section directly refutes option C: "The goal of defect report analysis is to gain a better understanding of the product and the process, not to blame individuals for the defects they have caused."

Section 3.3, "Managing the Review Process," pp. 28-29: This section details the formal review process, including roles and responsibilities, which aligns with the objectives and refutes the "lightweight" approach in option A.

2. Jones, C. (2012). Software Defect Removal Efficiency. Crosstalk, The Journal of Defense Software Engineering, 25(3), pp. 20-24.

This foundational article explains that calculating phase-based Defect Removal Efficiency (a concept synonymous with Phase Containment Effectiveness) requires tracking the total number of defects originating in each phase and the number of those defects found within that same phase. This necessitates the analysis described in option D.

3. Radice, R. A. (2002). High-quality, low-cost software inspections. Paradoxicon Publishing.

Chapter 2, "The Inspection Process," pp. 15-34: This chapter details the formal, role-based nature of inspections, which are a type of formal review. It emphasizes their effectiveness in early defect removal to reduce downstream costs, directly supporting the management objectives outlined in the question.