Requirements elicitation techniques in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify a common technique used to gather requirements by talking directly to users.

Software Engineering

The technique called [1] involves asking users questions to understand their needs.

Drag options to blanks, or click blank then click option'

ABrainstorming

BPrototyping

CInterview

DObservation

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing interviews with brainstorming sessions.

Thinking prototyping is the same as interviewing.

An Interview is a direct conversation with users to gather detailed requirements.

2fill in blank

medium

Complete the code to name the technique where users' actions are watched to understand their work.

Software Engineering

In the [1] technique, analysts watch users perform tasks to gather requirements.

Drag options to blanks, or click blank then click option'

AObservation

BSurvey

CFocus Group

DDocument Analysis

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up observation with surveys.

Thinking focus groups involve watching users silently.

Observation means watching users as they work to learn about their needs.

3fill in blank

hard

Fix the error in the code by selecting the correct technique used to gather many users' opinions quickly.

Software Engineering

A [1] collects feedback from many users using structured questions.

Drag options to blanks, or click blank then click option'

AInterview

BSurvey

CBrainstorming

DPrototyping

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing surveys with interviews.

Thinking brainstorming is a data collection method.

A Survey uses questionnaires to gather information from many people efficiently.

4fill in blank

hard

Fill both blanks to complete the code describing a technique where participants {{BLANK_1}} ideas aloud, and the facilitator uses {{BLANK_2}} to record and organize thoughts.

Software Engineering

During a focus group, participants [1] ideas aloud, and the facilitator uses [2] to capture and structure these ideas.

Drag options to blanks, or click blank then click option'

Ashare

Bignore

Cnote-taking

Drandom guessing

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'ignore' or 'random guessing' which do not fit the context.

Confusing note-taking with ignoring ideas.

In a focus group, participants share ideas, and note-taking helps record and organize them.

5fill in blank

hard

Fill all three blanks to complete the code describing a technique where a {{BLANK_1}} is created to show users, {{BLANK_2}} feedback is collected, and {{BLANK_3}} helps improve the design.

Software Engineering

In prototyping, a [1] is built, [2] feedback is gathered, and [3] is used to refine the system.

Drag options to blanks, or click blank then click option'

Amodel

Buser

Citeration

Ddocument

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'document' with 'model' for the prototype.

Mixing up 'iteration' with 'user' feedback.

Prototyping involves building a model, collecting user feedback, and using iteration to improve the design.

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