What is the term for the practice of collecting requirements from stakeholders or other sources?

The term that describes the practice of collecting requirements from stakeholders or other sources is "elicitation." This process involves engaging with various stakeholders, such as users, clients, and subject matter experts, to gather the information needed to define the requirements for a project or system. Elicitation is crucial because it helps to ensure that the project team fully understands the needs and expectations of stakeholders, which lays the foundation for successful project outcomes.

During the elicitation process, various techniques such as interviews, surveys, and workshops are often employed to facilitate open communication and comprehensive understanding. This practice not only focuses on what the stakeholders say they want but may also uncover hidden requirements that need to be addressed.

In contrast, analysis refers to the process of examining the collected information to identify patterns, define gaps, or inform decisions. Documentation involves recording and organizing the elicited requirements for future reference, while specification means detailing the requirements in a formalized manner for clarity and consensus. Each of these activities is part of a broader requirements management framework, but elicitation is specifically focused on the gathering phase.