CAPM Practice: Determine how to gather requirements

Requirements analysis transforms raw input from elicitation into organized, refined, and verified requirements. This includes resolving conflicts, eliminating ambiguity, identifying gaps, and ensuring requirements are complete, consistent, and feasible.

**Why not A:** Budget approval is a project management activity, not the primary goal of requirements analysis. While requirements analysis may inform cost estimates, its core purpose is to ensure requirements are complete, consistent, and clearly understood by all stakeholders.

**Why not B:** Reducing the number of requirements is not the goal of requirements analysis. The objective is to ensure each requirement is necessary, well-defined, and traceable to a business need. While analysis may identify redundancies, the aim is quality and clarity rather than simply minimizing count.

**Why not D:** Converting requirements to technical design is a downstream activity that occurs after requirements analysis is complete. Requirements analysis focuses on understanding and refining what is needed from a business perspective, not on prescribing how the solution will be built technically.