Question:

A development team conducts interviews, observations, and questionnaires before starting system design. The goal is to understand user expectations, constraints, and workflows. This activity primarily supports?

Show Hint

Elicitation is about "Collecting," while Analysis is about "Refining" and "Checking for Conflicts." Always associate interviews and surveys with the Elicitation stage.
Updated On: Jul 4, 2026
  • Requirement elicitation
  • Coding phase
  • Testing phase
  • Deployment
Show Solution
collegedunia
Verified By Collegedunia

The Correct Option is A

Solution and Explanation

Concept:
Requirement Engineering is the first and most critical phase of the Software Development Life Cycle (SDLC). It is broadly divided into two sub-stages: Elicitation and Analysis. Elicitation is the process of "gathering" or "extracting" requirements from stakeholders, customers, and end-users.

Step 1:
Identifying Elicitation Techniques.
The question mentions specific methods:
Interviews: Direct communication with stakeholders to understand their vision.
Observations: Watching how users currently perform tasks to identify pain points and workflows.
Questionnaires: Gathering data from a large group of users to find common needs. These are all classic techniques used during the Elicitation phase to discover what the system is actually supposed to do.

Step 2:
Distinguishing from other phases.

Coding: Involves writing the actual software using a programming language. This happens much later.
Testing: Involves verifying that the code works as intended.
Deployment: Involves delivering the finished product to the client environment.

Step 3:
Conclusion.
Since the activity described involves "understanding user expectations and workflows" before any design or code exists, it is clearly part of the requirement gathering process, specifically known as Requirement Elicitation.
Was this answer helpful?
0
0