Requirements elicitation techniques in Software Engineering - Step-by-Step Execution

Concept Flow - Requirements elicitation techniques

Start: Identify Stakeholders

↓

Choose Elicitation Technique

↓

Conduct Elicitation Session

↓

Gather Requirements Data

↓

Analyze & Validate Requirements

↓

End

The process starts by identifying stakeholders, then selecting and applying a technique to gather requirements, followed by analyzing and validating the collected information.

Execution Sample

Software Engineering

1. Identify stakeholders
2. Select technique (e.g., interview)
3. Prepare questions
4. Conduct interview
5. Document requirements

This sequence shows how an interview technique is used step-by-step to gather requirements from stakeholders.

Analysis Table

Step	Action	Details	Output
1	Identify stakeholders	List all people involved or affected	Stakeholder list created
2	Select technique	Choose interview for detailed info	Interview chosen
3	Prepare questions	Draft open-ended questions	Question list ready
4	Conduct interview	Ask questions and listen carefully	Raw requirements notes
5	Document requirements	Organize notes into clear statements	Requirements document
6	Analyze & validate	Check for completeness and correctness	Validated requirements
7	End	Requirements ready for next phase	Process complete

💡 All steps completed to gather and validate requirements using the chosen technique.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
Stakeholder List	Empty	Stakeholders identified	Stakeholders list unchanged	Unchanged	Unchanged	Unchanged	Unchanged
Technique	None	None	Interview selected	Unchanged	Unchanged	Unchanged	Unchanged
Questions	None	None	None	Questions prepared	Unchanged	Unchanged	Unchanged
Raw Notes	None	None	None	None	Interview conducted, notes taken	Unchanged	Unchanged
Requirements Document	None	None	None	None	None	Document created	Validated document

Key Insights - 3 Insights

Why do we identify stakeholders before choosing a technique?

Because knowing who is involved helps select the best way to gather their needs, as shown in Step 1 and Step 2 of the execution_table.

What happens if questions are not prepared before the interview?

The interview may miss important information or be unfocused, which is why Step 3 prepares questions to guide the session.

Why is analyzing and validating requirements important after gathering them?

To ensure the requirements are complete and correct before moving forward, as shown in Step 6 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after Step 4?

A Stakeholder list created

B Raw requirements notes

C Interview chosen

D Requirements document

💡 Hint

Check the 'Output' column for Step 4 in the execution_table.

At which step does the technique get selected?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Action' column in the execution_table to find when the technique is chosen.

If questions were not prepared, which variable in variable_tracker would remain 'None' after Step 3?

A Questions

B Stakeholder List

C Technique

D Raw Notes

💡 Hint

Check the 'Questions' row in variable_tracker after Step 3.

Concept Snapshot

Requirements elicitation involves:
- Identifying stakeholders
- Choosing a technique (interview, survey, etc.)
- Preparing and conducting sessions
- Gathering and documenting requirements
- Analyzing and validating before use

Full Transcript

Requirements elicitation techniques help gather information from stakeholders to understand what a software system should do. The process starts by identifying who the stakeholders are. Then, a suitable technique like interviews or surveys is chosen. Questions are prepared to guide the session. The elicitation session is conducted to collect raw requirements. These are then documented clearly. Finally, the requirements are analyzed and validated to ensure they are complete and correct before moving forward in the project.

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