CAPM Practice: Determine how to gather requirements

RAD prototyping produces rough, quick models (paper sketches, clickable wireframes) that stakeholders react to concretely. Rather than asking 'what do you want?' (hard to answer abstractly), it shows options and asks 'what's wrong with this?' — eliciting specific, actionable requirements through reaction.

**Why not B:** RAD prototyping is not a programming framework that generates requirements from code. RAD (Rapid Application Development) prototyping involves quickly building working models of a system to help stakeholders visualize and refine their requirements. Requirements drive the prototype, not the other way around. The prototype serves as a communication tool to validate and elicit requirements through hands-on interaction.

**Why not C:** RAD prototyping does not involve building a full application without requirements. The entire purpose of prototyping in RAD is to iteratively develop requirements through rapid feedback cycles. Each prototype iteration refines the understanding of what stakeholders need. Skipping requirements entirely would result in an undirected development effort with no stakeholder alignment.

**Why not D:** RAD prototyping does not mean developing multiple applications simultaneously. RAD focuses on rapidly iterating on a single system or solution through successive prototype versions. Each iteration incorporates stakeholder feedback to progressively refine the design and requirements. Building multiple applications at once describes parallel development, which is an unrelated project management concept.