Requirements elicitation techniques in Software Engineering - Mini Project: Build & Apply

Requirements Elicitation Techniques

📖 Scenario: You are part of a software development team tasked with gathering clear and complete requirements for a new project. To do this effectively, you need to understand and apply different requirements elicitation techniques.

🎯 Goal: Build a simple structured list of common requirements elicitation techniques with brief descriptions. This will help you remember and explain these techniques to your team.

📋 What You'll Learn

Create a dictionary named elicitation_techniques with exact keys and descriptions

Add a variable named priority_threshold to filter important techniques

Use a dictionary comprehension to select techniques with priority above the threshold

Add a final summary string describing the selected techniques

💡 Why This Matters

🌍 Real World

Requirements elicitation is a key step in software development to understand what users and stakeholders need. Using structured techniques helps gather clear and complete requirements.

💼 Career

Software engineers, business analysts, and project managers use these techniques to ensure the software meets user expectations and reduces costly changes later.

1

Create the initial data structure

Create a dictionary called elicitation_techniques with these exact entries: 'Interviews' with description 'Direct discussions with stakeholders', 'Surveys' with description 'Questionnaires to gather information', 'Workshops' with description 'Group sessions to explore requirements', 'Observation' with description 'Watching users perform tasks', and 'Document Analysis' with description 'Reviewing existing documentation'.

Software Engineering

# Create the elicitation_techniques dictionary with exact keys and descriptions
# Your code here

Hint

Use a Python dictionary with the exact keys and string values as described.

2

Add a priority threshold

Create a dictionary called technique_priority with these exact entries: 'Interviews': 5, 'Surveys': 3, 'Workshops': 4, 'Observation': 2, and 'Document Analysis': 1. Then create a variable called priority_threshold and set it to 3.

Software Engineering

elicitation_techniques = {
    'Interviews': 'Direct discussions with stakeholders',
    'Surveys': 'Questionnaires to gather information',
    'Workshops': 'Group sessions to explore requirements',
    'Observation': 'Watching users perform tasks',
    'Document Analysis': 'Reviewing existing documentation'
}
# Create technique_priority dictionary and priority_threshold variable
# Your code here

Hint

Use a dictionary for priorities and a simple integer variable for the threshold.

3

Filter techniques by priority

Use a dictionary comprehension to create a new dictionary called important_techniques that includes only those techniques from elicitation_techniques whose priority in technique_priority is greater than or equal to priority_threshold.

Software Engineering

elicitation_techniques = {
    'Interviews': 'Direct discussions with stakeholders',
    'Surveys': 'Questionnaires to gather information',
    'Workshops': 'Group sessions to explore requirements',
    'Observation': 'Watching users perform tasks',
    'Document Analysis': 'Reviewing existing documentation'
}

technique_priority = {
    'Interviews': 5,
    'Surveys': 3,
    'Workshops': 4,
    'Observation': 2,
    'Document Analysis': 1
}

priority_threshold = 3

# Your code here

Hint

Use a dictionary comprehension with elicitation_techniques.items() and check priority with technique_priority[technique].

4

Add a summary description

Create a string variable called summary that says exactly: 'Selected techniques are Interviews, Surveys, and Workshops.'

Software Engineering

elicitation_techniques = {
    'Interviews': 'Direct discussions with stakeholders',
    'Surveys': 'Questionnaires to gather information',
    'Workshops': 'Group sessions to explore requirements',
    'Observation': 'Watching users perform tasks',
    'Document Analysis': 'Reviewing existing documentation'
}

technique_priority = {
    'Interviews': 5,
    'Surveys': 3,
    'Workshops': 4,
    'Observation': 2,
    'Document Analysis': 1
}

priority_threshold = 3

important_techniques = {technique: desc for technique, desc in elicitation_techniques.items() if technique_priority[technique] >= priority_threshold}

# Your code here

Hint

Assign the exact string to the variable summary.

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