Final answer:
In an iterative lifecycle model, the most accurate statement is that for every development activity, there should be a corresponding testing activity. This ensures continual evaluation and refinement, which is essential to maintain high-quality standards. Testing in this context goes hand-in-hand with development, enabling the discovery and correction of issues through prototyping, testing, and refinement.
Step-by-step explanation:
In an iterative lifecycle model, testing activities are a crucial part of the development process. The most accurate statement about these activities is A: For every development activity, there should be a corresponding testing activity. This ensures that as new features or functionalities are developed, they are adequately tested to find and fix bugs or issues early in the development cycle. This approach leads to a high-quality product and reduces the risk of major defects being discovered after deployment. The iterative model emphasizes the need for continual evaluation and refinement, which is achieved by repeatedly cycling through development and testing phases.
The other options are supportive practices but are not as universally accurate. While B: For every testing activity, appropriate documentation should be produced, versioned and stored is an important practice for maintaining records and ensuring reproducibility, it is not a rule that applies specifically to the iterative lifecycle model. Similarly, C and D involve documentation and metrics, which are also good practices but are not definitive statements about the relationship between development and testing in an iterative model.
Testing reveals previously unknown characteristics of a design, requiring prototyping, testing, and refinement through many iterations. Thus, development and testing activities are intimately linked within this lifecycle model, reflecting the continuous evolution of both design and the corresponding validation efforts.