Which technique is commonly used for requirements elicitation?

Surveys and interviews are widely recognized techniques for requirements elicitation because they facilitate direct communication between the stakeholders and the project team. These methods allow for gathering detailed information, insights, and expectations from the end users or clients, thereby identifying their needs and desires accurately. Interviews provide an opportunity for in-depth discussions, allowing the interviewer to explore topics deeply, clarify ambiguities, and probe for additional insights. Surveys, on the other hand, can reach a larger audience quickly, allowing for the collection of a wide range of opinions and preferences which can help prioritize requirements based on user feedback.

In contrast, the other techniques mentioned do not focus specifically on the process of gathering user requirements. Cost-benefit analysis is primarily a financial assessment tool used to evaluate the feasibility of a project. Implementation reviews assess how well the requirements have been executed and whether the system meets the established criteria, but do not gather new requirements. Change logs document modifications to requirements but do not aid in eliciting initial or additional requirements from stakeholders.