New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB ATM Exam - Topic 3 Question 35 Discussion

Actual exam question for ISTQB's ATM exam
Question #: 35
Topic #: 3
[All ATM Questions]

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 each. It is planned to develop the most important features to have a stable core of the application in the first three iterations and to add the additional features in the last six iterations.

At the beginning of the first iteration, only a draft version of the requirements specification document for the core features is available. Assume that during each of the first three iterations, the chosen features are fully completed and unit tested.

Which of the following statements is true in this context?

K4 3 credits

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Floyd
3 months ago
Applying a sequential test strategy in an iterative model? No way!
upvoted 0 times
...
Dulce
3 months ago
Wait, are we really only testing at the end? That seems risky!
upvoted 0 times
...
Beckie
3 months ago
Allocating effort for system testing in the first three iterations makes sense.
upvoted 0 times
...
Lawrence
4 months ago
I disagree, system testing should happen throughout the iterations.
upvoted 0 times
...
Bernardine
4 months ago
The system test phase should start when all requirements are frozen.
upvoted 0 times
...
Hortencia
4 months ago
I wonder if we should really apply the same strategy as in a sequential model. It feels like iterative models require a different approach to testing.
upvoted 0 times
...
Marvel
4 months ago
I feel like option C is too extreme; I can't recall any scenario where we would only test in the last iteration. That doesn't seem right.
upvoted 0 times
...
Kristeen
4 months ago
I think we practiced a question where we had to allocate testing efforts across iterations, and it seems like we should focus on system testing early on for the core features.
upvoted 0 times
...
Craig
5 months ago
I remember discussing how system testing typically starts after requirements are finalized, but I'm not sure if that's the case here since it's iterative.
upvoted 0 times
...
Kaycee
5 months ago
I've got a strategy in mind, but I want to double-check my understanding before committing to an answer.
upvoted 0 times
...
Alesia
5 months ago
I'm a bit confused by the options. I'll need to carefully consider the differences between them and how they align with the iterative development approach described.
upvoted 0 times
...
Trinidad
5 months ago
Okay, I think I've got a handle on this. The key is to recognize that the system will be developed incrementally, so the testing approach needs to match that.
upvoted 0 times
...
Barney
5 months ago
Hmm, the iterative life-cycle model and the partial requirements specification make this a bit tricky. I'll need to think through the implications for the testing strategy.
upvoted 0 times
...
Sarah
5 months ago
This question seems straightforward, but I want to make sure I understand the context correctly before answering.
upvoted 0 times
...
Lajuana
5 months ago
Okay, let's see. I'm pretty sure function modules and billable item statuses are involved, but I'm not sure about the other two options.
upvoted 0 times
...
Shenika
5 months ago
Hmm, this is a tough one. I'm not sure if it's synchronous, collaborative, or passive-aggressive. I'll have to weigh the options carefully.
upvoted 0 times
...
Sabine
10 months ago
Testing? More like 'guessing' in this project. I bet the developers are already working on features for the last six iterations, and the requirements are still 'drafty'.
upvoted 0 times
...
Anjelica
10 months ago
Option A is a trap. Freezing requirements completely before testing? That's just asking for trouble in an agile world.
upvoted 0 times
...
Nicolette
10 months ago
Haha, option D is a classic 'do the opposite of what you should' kind of answer. Sequential life cycle and iterative are like night and day when it comes to testing.
upvoted 0 times
Timothy
8 months ago
Haha, option D is a classic 'do the opposite of what you should' kind of answer. Sequential life cycle and iterative are like night and day when it comes to testing.
upvoted 0 times
...
Samira
9 months ago
B) You should allocate a large effort for system testing during the first three iterations
upvoted 0 times
...
Ettie
9 months ago
A) The system test phase should start when all the requirements are frozen
upvoted 0 times
...
...
Vernice
10 months ago
I disagree with option C. Waiting until the last iteration to do all the system testing is a recipe for disaster in an iterative model.
upvoted 0 times
...
Ronald
10 months ago
Option B makes the most sense. With an iterative life cycle, system testing should be integrated throughout the development process, not just at the end.
upvoted 0 times
Odette
9 months ago
B) You should allocate a large effort for system testing during the first three iterations
upvoted 0 times
...
Xochitl
9 months ago
A) The system test phase should start when all the requirements are frozen
upvoted 0 times
...
Crista
10 months ago
B) You should allocate a large effort for system testing during the first three iterations
upvoted 0 times
...
...
Stevie
11 months ago
I believe the system test phase should start when all the requirements are frozen. It's crucial for overall quality.
upvoted 0 times
...
Sommer
11 months ago
I agree with Helene. It's important to ensure the core features are stable before adding additional features.
upvoted 0 times
...
Helene
11 months ago
I think we should allocate a large effort for system testing during the first three iterations.
upvoted 0 times
...

Save Cancel