Q. What is requirement elicitation methods?

Subsequent to receiving the problem statement from the customer the first step is to arrange a meeting with the customer. During the meeting or else interview both the parties would like to understand each other. Usually specialized developers frequently called requirement engineers interact with the customer. The objective of conduct an interview is to understand the customer's expectation from the software. Both parties have dissimilar goals, feelings, opinions, vocabularies, understanding but one thing in common both want the project to be a success.

With this is mind requirement engineers normally arrange interviews. Requirements engineers should be open minded and should not approach the interview with pre-conceived notion about what is required. Interview may perhaps open-ended or structured. In open ended interview there is no pre-set agenda. Context free questions possibly asked to understand the problem and to have an overview of the situation.

In structured interview outline of fairly open questions is prepared. Occasionally a proper questionnaire is designed for the interview. Interview possibly started with simple questions to set people at ease. Subsequent to making atmosphere comfortable and calm specific questions possibly asked to understand the requirements the customer may be allowed to voice his or her perception about a possible solution.