Q: 5
Consider the following statement.
Projects may cycle between ADM phases, in planned cycles covering multiple phases.
What does it illustrate?
Options
Discussion
I don’t think it’s A. B fits since cycling phases is iteration, not just requirements stuff.
C or B? ADM cycles can feel like requirements management too, but TOGAF calls that iteration. I've seen similar wording on practice tests and usually B is safest, though I wonder if A could trip people up.
Why not A here? Cycling phases sounds more like iteration than actual requirements handling.
B tbh, fits the idea of going back through ADM cycles. Not seeing how A would apply here.
A is wrong, B. Cycling phases is all about iteration in ADM, not requirements management.
Definitely B here.
I wouldn’t say it’s B. A makes more sense because requirements management actually causes the cycling between ADM phases, especially when stakeholder needs change mid-process. Maybe not what most would pick, but TOGAF ties iteration heavily to managing evolving requirements. Am I stretching it?
B tbh, cycling through ADM phases is pretty much the definition of iteration in TOGAF terms. Requirements management (A) is always ongoing but isn't what this statement's describing. Makes sense to pick B here, unless I'm missing something subtle.
B here, it's about iteration. The ADM cycling through phases is classic iterative process, not so much requirements management. Pretty sure B is what they're asking for but open to other ideas.
A or B? ADM does cycle phases to adjust requirements, so I went with A since requirements management is what drives the need for iteration in the first place. If the main focus was on the process itself, B makes sense, but if it's about what triggers those planned cycles, I think A could fit. Seen TOGAF make this distinction in some scenarios. Anyone else see it that way?
Be respectful. No spam.
