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.