Which activity is part of requirements gathering?

• A. Capture data from prospective application users and stakeholders.
• B. Finalize the vision of the application.
• C. Validate the functionality of the application and ensure stakeholders are ready to accept it.
• D. Determine the project budget.

Answer: (A)

Requirements gathering is about eliciting and capturing what the system needs to do from those who will use it and be affected by it. Capturing data from prospective users and stakeholders directly feeds this process: it gathers the real needs, constraints, and success criteria that the project must address. Through interviews, workshops, and observations, you learn what information must be collected, what workflows must be supported, what rules govern the business, and what priorities drive the solution. This input forms the foundation for designing the data model, processes, and interfaces that the app will implement, ensuring the final product meets actual user needs.

Finishing the vision of the application is a higher-level, directional step that sets goals and scope, not the detailed gathering of requirements. Validating functionality and ensuring stakeholders are ready to accept the solution is about verification and acceptance testing, not initial gathering. Determining the project budget relates to cost planning and resource forecasting, again outside of requirements elicitation.