SISTUHS Interview Practice Test

Which description best captures a simple requirements elicitation session with stakeholders?

Begin with a long presentation of a proposed solution.

Only ask yes/no questions and document minimal detail.

Focus on high-level goals without validation.

Include goals, open-ended questions, capture needs/constraints, document, and validate with stakeholders.

In a simple requirements elicitation session, the goal is to uncover and agree on what stakeholders actually need, including goals, specific needs, and any constraints, and to verify that understanding with them. The description that best fits this approach includes setting goals, using open-ended questions to explore what stakeholders want and why, capturing needs and constraints, documenting what’s learned, and validating those findings with the stakeholders. This sequence promotes thorough discovery, clear understanding, and buy-in from everyone involved.

Why the other ideas don’t fit as well: starting with a long presentation of a proposed solution can bias stakeholders and short-circuit genuine discovery; asking only yes/no questions and recording minimal detail misses the nuance and breadth of needs; focusing on high-level goals without validation risks misalignment and missing important constraints that could affect feasibility.