Requirements elicitation techniques in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is requirements elicitation in software engineering?

Requirements elicitation is the process of gathering information from stakeholders to understand what the software system should do.

beginner

Name three common techniques used for requirements elicitation.

Common techniques include interviews, questionnaires, and observation.

beginner

How does an interview help in requirements elicitation?

An interview allows direct communication with stakeholders to ask questions and clarify their needs in detail.

intermediate

What is the purpose of prototyping in requirements elicitation?

Prototyping creates a simple model of the system to help stakeholders visualize and refine their requirements.

intermediate

Why is observation useful in requirements elicitation?

Observation helps understand how users perform tasks in their real environment, revealing needs they might not express directly.

Which technique involves asking stakeholders direct questions to gather requirements?

A Observation

B Interview

C Prototyping

D Document analysis

Interviews involve direct questioning of stakeholders to understand their needs.

What is the main benefit of using prototypes during requirements elicitation?

A To visualize and refine requirements

B To finalize the software code

C To test the software performance

D To replace user feedback

Prototypes help stakeholders see a model of the system and improve their requirements.

Which technique involves watching users perform their tasks in their normal environment?

A Brainstorming

B Questionnaires

C Observation

D Interviews

Observation means watching users to understand their real work habits and needs.

Which of the following is NOT a requirements elicitation technique?

A Interviews

B Workshops

C Questionnaires

D Code debugging

Code debugging is related to fixing software, not gathering requirements.

Why are workshops useful in requirements elicitation?

A They allow group discussion and consensus building

B They replace the need for interviews

C They are used to write the final code

D They test software usability

Workshops bring stakeholders together to discuss and agree on requirements.

Explain the role of interviews and observation in requirements elicitation.

Think about how you would learn what someone wants by talking and watching.

Describe how prototyping can improve the requirements gathering process.

Imagine showing a rough draft to get better ideas.