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.