In requirements elicitation, which strategies are appropriate for discovering accurate user needs in an information system project?
-
AAsking questions through interviews, workshops, and surveys
-
BObtaining information by observing and analyzing the present system
-
CBuilding quick prototypes to validate and refine requirements
-
DAll of the above
-
ERelying only on vendor brochures
Answer
Correct Answer: All of the above
Explanation
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:
1) Conduct stakeholder mapping and schedule structured interviews. 2) Shadow users performing tasks; collect forms, reports, and data samples. 3) Draft user stories and acceptance criteria from findings. 4) Create low-fidelity mockups or working prototypes for feedback. 5) Iterate until requirements are consistent, testable, and prioritized.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:
Single-source reliance (for example, only brochures) ignores real context and leads to mismatched solutions.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.