Which of the following techniques is generally NOT considered a legitimate requirements-gathering method?

Question

BlackTom AI · Accepted Answer

Requirements gathering must be systematic and evidence-based: methods should elicit, validate, and document stakeholder needs rather than rely on guesswork.

1. Relevant knowledge points and concepts
- Requirements gathering: activities to discover stakeholder needs, constraints, and acceptance criteria.
- Good methods are verifiable, repeatable and produce traceable artifacts (e.g., interview transcripts, prototypes, documentation).
- Common legitimate techniques: document review, interviews, focus groups, observation, surveys, prototyping, workshops, contextual inquiry, use cases, and user stories.
- Illegitimate approaches are those that rely on unverified assumptions, guesswork, or lack stakeholder validation.

2. Step-by-step reasoning process
Step 1: Examine each option against the criteria of being systematic and verifiable.
Step 2: Determine whether the option produces evidence or enables stakeholder validation.
Step 3: Eliminate options that are recognized, standard elicitation techniques.
Step 4: Select the option that fails the criteria.

3. Intermediate steps / evaluation of options
- Reviewing existing documentation and processes: produces artifacts and context; is a standard elicitation technique.
- Prototyping: creates tangible models for feedback and validation; widely used to clarify and verify requirements.
- Interviews and focus groups: direct stakeholder engagement to elicit needs and priorities; foundational elicitation techniques.
- Randomly assuming user needs without verification: produces no evidence, bypasses stakeholders, and cannot be validated — effectively guesswork.

4. Why the correct answer is correct
"Randomly assuming user needs without verification" is not a legitimate requirements-gathering method because it lacks stakeholder involvement, produces unverifiable and untraceable requirements, and increases risk of delivering the wrong product. Legitimate methods aim to reduce uncertainty through evidence and feedback; random assumptions do the opposite.

5. Why the other options are incorrect
- Reviewing existing documentation and processes: legitimate — helps understand current state and constraints.
- Prototyping: legitimate — supports validation and discovery through iteration.
- Interviews and focus groups: legitimate — directly collect stakeholder needs and perspectives.

6. Conclusion
Therefore, the technique that is generally NOT considered legitimate is "Randomly assuming user needs without verification," which matches the provided answer.

Which of the following techniques is generally NOT considered a legitimate requirements-gathering method?单项选择题

类似问题

The following are several top factors for project failure. Which of these is directly related to the requirements process?

Question at position 46 The main purpose of requirements gathering is to: Write the final documentationTest the system for bugsSetup the hardwareDefine what the users need

What is one of the most valuable roles of a programmer during requirements gathering?

Which of these is not a requirements gathering method?

The features and functionality required in a software project being developed are listed in which stage?

What is the purpose of Requirements Gathering?

The features and functionality required in a software project being developed are listed in which stage?

更多留学生实用工具

智能学习助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单