CAPM Practice: Determine how to gather requirements

'Requirements elicitation' is preferred because 'gathering' implies requirements exist fully-formed, waiting to be collected. In reality, requirements must be actively drawn out through skilled facilitation — stakeholders often can't articulate their real needs without help. The word choice reflects a fundamentally different mindset.

**Why not A:** Elicitation and gathering are not completely different activities. Elicitation is the broader, more accurate term that encompasses gathering along with other techniques for drawing out requirements. Treating them as entirely separate concepts misses the relationship between the two.

**Why not C:** The distinction between elicitation and gathering is not about who performs them. Both are carried out by business analysts and involve stakeholder interaction. The real difference is that elicitation implies an active, facilitative process of drawing out information, while gathering suggests passive collection.

**Why not D:** Elicitation and gathering do not address different requirement types. Both can apply to functional, non-functional, business, or stakeholder requirements. The distinction is about the approach and mindset used to obtain requirements, not the categories of requirements being collected.