The statement is false. While attentive listening is a critical skill, it is only one part of effective communication, often referred to as active listening. Active listening involves not only hearing the customer's words but also confirming understanding. This frequently requires asking clarifying questions to resolve ambiguities, explore details, and uncover unstated assumptions. Forbidding questions would lead to misinterpretations of requirements, resulting in a product that fails to meet the customer's actual needs. Effective requirements elicitation is a collaborative dialogue, not a passive reception of information.

A. True: This is incorrect because it promotes a passive communication model. Never asking for clarification is a fundamentally flawed practice that leads to critical misunderstandings, incorrect assumptions, and project failure.

1. IEEE Computer Society. (2014). Guide to the Software Engineering Body of Knowledge (SWEBOK), Version 3.0. In Chapter 2, "Software Requirements," Section 2.1.2, "Requirements Elicitation Techniques," describes methods like interviews and focus groups, which are inherently interactive and depend on asking questions to clarify and elaborate on stakeholder needs.

2. Pohl, K. (2010). Requirements Engineering: Fundamentals, Principles, and Techniques. Springer. In Chapter 6, "Elicitation," Section 6.2.1, "Communication Skills," it is stated that "Asking the right questions is a central skill for a requirements engineer... Clarification questions help to resolve ambiguities." (p. 137).

3. Sommerville, I. (2016). Software Engineering (10th ed.). Pearson. In Chapter 4, "Requirements Engineering," Section 4.2, "Requirements Elicitation," the text explains that developing a complete understanding of a problem is difficult and requires stakeholders and engineers to work together, which involves questioning and discussion to refine requirements.