In requirements elicitation, which strategies are appropriate for discovering accurate user needs in an information system project?

Introduction / Context:
Eliciting user requirements is the foundation of a successful system. High quality requirements come from triangulating multiple strategies so that stated needs, real workflows, and validated prototypes converge into a precise specification.

Given Data / Assumptions:

• Stakeholders include end users, managers, auditors, and IT staff.
• The current system (manual or automated) embodies tacit knowledge.
• There is uncertainty or ambiguity in initial problem statements.

Concept / Approach:
Effective elicitation combines inquiry (interviews, workshops), observation of the as-is process and data, and prototyping. Interviews reveal goals and constraints; observation exposes exceptions and workarounds; prototypes turn abstract ideas into concrete screens and reports that users can critique, reducing misinterpretation risk.

Step-by-Step Solution:

Verification / Alternative check:
Requirements are validated when independent methods (spoken needs, observed behavior, prototype feedback) agree. If disagreement persists, revisit assumptions or stakeholder alignment.

Why Other Options Are Wrong:

Common Pitfalls:
Using only interviews (risk of idealized answers), ignoring edge cases seen in observation, or skipping prototypes which help surface usability gaps early.

Final Answer:
All of the above.