+1 vote
in Hazardous Waste Management by (86.7k points)
Which among these is not a heuristic for stakeholder’s needs elicitation?

(a) Determine stakeholder goal as the context of stakeholder needs and desires

(b) Study user tasks

(c) Learn about problem domain at the later stages

(d) All of the mentioned

This question was addressed to me in an international level competition.

This question is from Needs Elicitation Documentation and Analysis topic in section Requirements Specification and Planning of Software Architecture

1 Answer

0 votes
by (650 points)
The correct answer is (c) Learn about problem domain at the later stages. In stakeholder needs elicitation, the heuristics (practical methods) for effective requirements gathering include: Determining stakeholder goals as the context is essential for understanding their needs. Studying user tasks helps identify what stakeholders actually do and need. However, learning about the problem domain at the later stages is NOT a heuristic for needs elicitation - it should be done during the initial stages of requirements gathering to properly understand the context and create suitable solutions. In software architecture and requirements planning, domain knowledge must be acquired early to inform proper elicitation techniques. Therefore, (c) is the incorrect heuristic among the options given, making it the correct answer to this question.

Related questions

We welcome you to Carrieradda QnA with an open heart. Our small community of enthusiastic learners are very helpful and supportive. Here on this platform, you can ask questions and receive answers from other members of the community. We also monitor posted questions and answers periodically to maintain the quality and integrity of the platform. Hope you will join our beautiful community.

Discover smart and simple ways to live in Japan: Mikataa | The Japanese Ways | EV Pulse

...