Which of the following is NOT a requirements gathering technique? a. Exploratory prototypes b. Facilitated workshops c. Review existing code d. Surveys
The Correct Answer and Explanation is:
Correct Answer: c. Review existing code
Explanation
Requirements gathering is a crucial phase in the software development lifecycle where stakeholders’ needs are identified, understood, and documented. It involves various techniques to ensure that the final system aligns with user expectations. Common techniques include interviews, surveys, facilitated workshops, and prototyping. However, not all activities associated with understanding a system are considered formal requirements gathering methods.
Let’s briefly examine each option:
- a. Exploratory Prototypes
Exploratory prototyping is a recognized requirements gathering technique. It involves building quick and often low-fidelity models of the system to help stakeholders visualize and refine requirements. This method allows users to interact with a model of the system and provide feedback, which helps in clarifying and evolving the requirements. - b. Facilitated Workshops
Facilitated workshops are collaborative meetings that bring together key stakeholders to elicit requirements in a structured setting. A facilitator guides discussions to uncover business needs, prioritize features, and resolve conflicts. This method is highly effective for capturing comprehensive and agreed-upon requirements. - c. Review Existing Code
Reviewing existing code is more of a reverse engineering or system analysis activity rather than a requirements gathering technique. While it can provide insights into how an existing system functions, it doesn’t directly involve engaging stakeholders to gather new requirements. Instead, it helps in understanding legacy systems or verifying implementation, making it more relevant to maintenance or system redesign tasks. - d. Surveys
Surveys are a structured way to gather requirements from a large number of users or stakeholders. They involve distributing questionnaires that collect opinions, preferences, and needs. This technique is efficient for quantitative data collection and is especially useful when stakeholders are geographically dispersed.
Conclusion:
While reviewing existing code can support understanding an existing system, it is not a direct method for gathering user or stakeholder requirements. Therefore, option c is the correct answer.
