Requirement Elicitation

A detailed description of the software product and quality parameters of the product is defined in the requirements capture and specification phase in the software life cycle. The hierarchical decomposition during those development phases describes how the product will meet its customer requirements and what quality attributes are consistent with the product.

Sometimes requirement specifications might be not perfect enough or fail to capture the actual user requirements accurately. Because of that, the end product won’t meet the customer’s expectations and It may cause an unsatisfied customer. Due to these reasons, the project might be failed. Even it may damage the goodwill of the software development organization. Therefore, requirements should be valid and ensure the captured requirements will meet actually what customers need. The system analyst is responsible to understand how the live business operation is happening and how the software product will contribute to the operation.

Requirement election helps overcome these challenges. The Elicitation of requirements can be defined as the tasks that business analysts or system analysts perform to obtain information from stakeholders and confirm the results. Requirement elicitation is the process of discovering, researching the requirements of a system from end-users or receiving information from stakeholders or other related sources.

Discovering requirements and design information is done through elicitation. In order to discover requirements and design information, talk to stakeholders, research topic, the experiment will be done. Requirement elicitation might be planned or unplanned activity. Planned Requirement elicitation activities are experiments, workshops, surveys, etc. Last minutes collaboration or just-in-time conversation can be considered as unplanned elicitation activities.