---
title: "Short note: Requirement gathering methods"
subject: "Object Oriented Analysis and Design"
chapter: 2
key: "semester_6/object_oriented_analysis_and_design:short-note-requirement-gathering-methods"
source: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/short-note-requirement-gathering-methods
site: BCT Engineering
---

# Short note: Requirement gathering methods

Object Oriented Analysis and Design · Chapter 2: Object Oriented Analysis

- Asked in: 2070 Bhadra, 5 marks
- Video: [Requirement Gathering Techniques For A Business Analyst](https://www.youtube.com/watch?v=8EBWxW5Cn1g) — Stefano - The Agile Business Analyst
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/short-note-requirement-gathering-methods
- Whole chapter: https://www.bctengineer.com/md/semester_6/object_oriented_analysis_and_design/chapter-2

## Question

Write a short note on Methods of requirement gathering.

## Short answer

Requirement gathering (elicitation) discovers stakeholder needs using interviews, questionnaires, observation, document analysis, JAD workshops, prototyping, and use cases. A mix of methods is used, and outputs are validated and recorded in use cases and a software requirements specification.

## Answer

**Requirement gathering** (elicitation) is the activity of finding out what the users and stakeholders need from the system. Common methods are:

1. **Interviews** - Direct questions to users and managers, structured or open. Gives detailed and personal information, but is time-consuming.
2. **Questionnaires/Surveys** - Written questions to many users. Good for large groups and statistics; answers are less detailed.
3. **Observation (Ethnography)** - Watching users do their work in the real setting. Shows what people actually do, including things they forget to say.
4. **Document analysis** - Studying existing forms, reports, manuals, rules and the old system.
5. **Joint Application Development (JAD) / Workshops** - Structured meetings of users, analysts and developers to agree on requirements quickly.
6. **Brainstorming** - A group generates many ideas freely and filters them later.
7. **Prototyping** - A quick working mock-up is shown to users; their feedback clarifies unclear requirements.
8. **Use cases and scenarios** - Describe interactions between actors and the system step by step; the standard way in OOA.
9. **Domain/market study and focus groups** - Compare similar systems and discuss with a selected group of users.

A mix of methods is normally used. The results are written as use cases and a Software Requirements Specification (SRS), and are checked with the stakeholders (validation).

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. What is the main advantage of observation (ethnography)?
   A. It needs no users
   B. It produces statistics
   C. It reaches thousands cheaply
   D. Shows what users actually do, including unspoken things
   Answer: D. Watching real work reveals things people forget to say. (Key point: Observation)

2. Questionnaires are best for:
   A. Rapid agreement in a meeting
   B. Large groups, with less detailed answers
   C. Detailed personal information
   D. Mock-ups
   Answer: B. They suit many users and statistics but lack depth. (Key point: Questionnaires)

3. Prototyping helps requirements by:
   A. Designing the database
   B. Writing the SRS
   C. Replacing all interviews
   D. Letting users give feedback on a quick working mock-up
   Answer: D. Feedback on a mock-up clarifies unclear requirements. (Key point: Prototyping)

4. The gathered requirements are normally written as:
   A. Test results
   B. Source code only
   C. Use cases and an SRS, validated with stakeholders
   D. A deployment diagram
   Answer: C. A mix of methods is used; results are documented and validated. (Key point: Output of gathering)

## Related in other subjects

- [Requirement gathering and analysis techniques](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Arequirement-gathering-techniques) — Software Engineering, chapter 1
- [Requirement gathering processes compared](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Arequirement-gathering-processes) — Software Engineering, chapter 1