You are the Test Manager on a project following an iterative life-cycle model. The project should consist of nine iterations of one month duration…

In an iterative life-cycle model, testing is an integral part of each iteration, not a phase at the end. The project plan focuses on developing a "stable core" with the "most important features" in the first three iterations. This core functionality represents the highest risk and is the foundation for all subsequent development. Therefore, allocating a significant system testing effort early on is critical to validate the core architecture and functionality, provide early feedback, and mitigate risks before building upon this foundation. This aligns with the iterative principle of building and testing the product incrementally.

A. Waiting for frozen requirements is a characteristic of sequential (e.g., Waterfall) models, which is contrary to the iterative approach where development and testing proceed with evolving requirements.
C. Deferring all system testing to the last iteration is a high-risk "big-bang" approach typical of sequential models and defeats the purpose of early feedback in iterative development.
D. An iterative life cycle requires a fundamentally different test strategy than a sequential one; it involves continuous integration, incremental testing, and extensive regression testing within each cycle.

1. ISTQB® Certified Tester Advanced Level Syllabus, Test Manager, Version 2012:

Section 2.3.3, Test Strategies for Iterative Development, p. 23: "In iterative lifecycles, such as RUP and Agile lifecycles, the test strategy is to test on an iteration-by-iteration basis... each iteration involves testing at one or more test levels." This supports performing system testing within the early iterations.

Section 5.2.4, Risk-based Testing, p. 61: "Risk-based testing uses risk to prioritize and emphasize the appropriate tests... The most important items should be tested first." The "stable core" with "most important features" represents the highest-risk items, justifying a large, early testing effort.

2. ISTQB® Certified Tester Foundation Level Syllabus, Version 2018 v3.1:

Section 2.1.2, Software Development Lifecycle Models, p. 10: "In iterative models, the feature sets are grown incrementally... Testing activities are carried out throughout the project." This directly contradicts deferring testing (Option C) or using a sequential strategy (Options A and D).

3. Sommerville, I. (2011). Software Engineering (9th ed.). Pearson Education.

Chapter 2, Section 2.2.2, Incremental development, p. 41: "Incremental development has a number of advantages... The cost of accommodating changing customer requirements is reduced... It is easier to get customer feedback on the development work that has been done." Allocating significant testing effort early facilitates this feedback loop on the core functionality.