Requirements elicitation techniques in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Interviews in Requirements Elicitation

Which of the following best describes the main advantage of using interviews as a requirements elicitation technique?

A They allow direct interaction with stakeholders to clarify ambiguous requirements.

B They automatically generate detailed system documentation without human input.

C They replace the need for any other elicitation techniques in complex projects.

D They are the fastest method to gather requirements from a large number of users simultaneously.

💡 Hint

Think about how interviews help in understanding stakeholder needs.

Interviews provide a direct way to communicate with stakeholders, allowing the analyst to ask questions and clarify unclear points, which helps in gathering accurate requirements.

📋 Factual

intermediate

Identifying a Common Drawback of Questionnaires

What is a common limitation of using questionnaires for requirements elicitation?

A They are too expensive and time-consuming compared to other methods.

B They require face-to-face meetings with every stakeholder.

C They always produce biased results because of interviewer influence.

D They often result in incomplete or unclear answers due to lack of interaction.

💡 Hint

Consider how the absence of direct communication affects responses.

Questionnaires do not allow immediate follow-up questions, so respondents might provide incomplete or unclear answers, limiting the quality of gathered requirements.

🔍 Analysis

advanced

Comparing Prototyping and Observation

Which statement correctly compares prototyping and observation as requirements elicitation techniques?

A Prototyping is less effective because it does not involve any user interaction.

B Prototyping involves creating a model to gather feedback, while observation involves watching users perform tasks without interference.

C Both techniques rely solely on stakeholder interviews to collect requirements.

D Observation requires building a working system first, whereas prototyping only uses surveys.

💡 Hint

Think about how each technique gathers information from users.

Prototyping creates a sample system to get user feedback, while observation involves watching users in their environment to understand their needs without direct questioning.

❓ Reasoning

advanced

Choosing the Best Technique for Ambiguous Requirements

A project has many unclear and conflicting requirements from different stakeholders. Which elicitation technique is most suitable to resolve these ambiguities?

A Observation of users without asking questions to avoid bias.

B Distributing questionnaires to collect individual opinions separately.

C Joint Application Development (JAD) sessions to facilitate stakeholder collaboration.

D Reading existing documentation without stakeholder involvement.

💡 Hint

Consider which method encourages discussion and consensus.

JAD sessions bring stakeholders together to discuss and resolve conflicting requirements through collaboration and negotiation.

❓ Comparison

expert

Evaluating the Effectiveness of Brainstorming vs. Document Analysis

Which of the following correctly contrasts brainstorming and document analysis in requirements elicitation?

A Brainstorming generates new ideas through group creativity, while document analysis reviews existing materials to extract requirements.

B Document analysis is a creative group activity, whereas brainstorming only involves reading manuals.

C Both techniques require no stakeholder involvement and rely solely on automated tools.

D Brainstorming is used only after document analysis is complete and cannot be done independently.

💡 Hint

Think about the nature of each technique and how they gather information.

Brainstorming is a group activity to generate ideas and uncover hidden requirements, while document analysis involves studying existing documents to find relevant information.

Practice

1. Which of the following is a primary goal of requirements elicitation techniques in software engineering?

easy

A. To test the software for bugs

B. To write the final code for the software

C. To gather and understand what users and stakeholders want

D. To deploy the software to users

Solution

1. Step 1: Understand the purpose of requirements elicitation

   Requirements elicitation is about collecting needs and expectations from users and stakeholders before development.

2. Step 2: Differentiate from other software phases

   Writing code, testing, and deployment happen after requirements are gathered.

3. Final Answer:

   To gather and understand what users and stakeholders want -> Option C

4. Quick Check:

   Requirements elicitation = gathering needs [OK]

Hint: Elicitation means gathering needs from users [OK]

Common Mistakes:

• Confusing elicitation with coding or testing
• Thinking deployment is part of elicitation

2. Which of the following is the correct description of the interview technique in requirements elicitation?

easy

A. A group discussion with many stakeholders at once

B. A written questionnaire sent to users

C. Watching users interact with the current system silently

D. A one-on-one conversation to gather detailed information

Solution

1. Step 1: Define the interview technique

   An interview is a direct, one-on-one conversation to get detailed user needs.

2. Step 2: Compare with other techniques

   Group discussions are workshops, questionnaires are surveys, and silent watching is observation.

3. Final Answer:

   A one-on-one conversation to gather detailed information -> Option D

4. Quick Check:

   Interview = one-on-one talk [OK]

Hint: Interview means talking directly to one person [OK]

Common Mistakes:

• Mixing interviews with group workshops
• Confusing interviews with surveys or observations

3. Consider a project team using both surveys and observations to gather requirements. What is the main benefit of combining these two techniques?

medium

A. It reduces the total time needed to gather requirements

B. It provides both user opinions and actual user behavior insights

C. It eliminates the need for stakeholder meetings

D. It ensures all requirements are gathered without any missing

Solution

1. Step 1: Understand surveys and observations

   Surveys collect user opinions via questions; observations watch real user actions.

2. Step 2: Identify combined benefit

   Using both gives a fuller picture: what users say and what they actually do.

3. Final Answer:

   It provides both user opinions and actual user behavior insights -> Option B

4. Quick Check:

   Surveys + observations = opinions + behavior [OK]

Hint: Combine opinions (surveys) with actions (observations) [OK]

Common Mistakes:

• Assuming combination always saves time
• Believing it guarantees no missing requirements

4. A team used only interviews to gather requirements but missed some important user needs. What is the most likely reason?

medium

A. They did not use multiple elicitation techniques together

B. Interviews always produce incomplete data

C. Users do not know their own needs

D. Interviews are only for technical requirements

Solution

1. Step 1: Recognize limitation of single technique

   Using only interviews can miss some needs because users may forget or not mention everything.

2. Step 2: Importance of multiple techniques

   Combining interviews with surveys, observations, or workshops improves completeness.

3. Final Answer:

   They did not use multiple elicitation techniques together -> Option A

4. Quick Check:

   Single technique misses needs; combine methods [OK]

Hint: Use multiple techniques to avoid missing needs [OK]

Common Mistakes:

• Thinking interviews always fail
• Blaming users for not knowing needs
• Assuming interviews only cover technical needs

5. A software team wants to ensure they capture both explicit and hidden user requirements for a complex system. Which combination of elicitation techniques is best suited for this goal?

hard

A. Observations and interviews, to see real behavior and ask detailed questions

B. Interviews and workshops, to discuss and clarify needs interactively

C. Only surveys, because they reach many users quickly

D. Workshops alone, since group consensus covers all needs

Solution

1. Step 1: Identify explicit vs hidden requirements

   Explicit needs are clearly stated; hidden needs are revealed by watching real user behavior.

2. Step 2: Match techniques to requirement types

   Observations reveal hidden needs by watching actions; interviews clarify explicit needs by asking questions.

3. Step 3: Evaluate other options

   Surveys alone miss hidden needs; workshops help but may not reveal hidden behaviors fully.

4. Final Answer:

   Observations and interviews, to see real behavior and ask detailed questions -> Option A

5. Quick Check:

   Hidden + explicit needs = observations + interviews [OK]

Hint: Use observation for hidden, interviews for explicit needs [OK]

Common Mistakes:

• Relying only on surveys or workshops
• Ignoring hidden requirements from behavior
• Assuming group talks reveal all needs