- Year not given · 3+4.5+2.5 marks
Requirement gathering processes compared
Short answer
Common processes: interviews, questionnaires, observation, JAD, prototyping, and use cases. Interviews: structured/unstructured questioning of stakeholders for deep insight but time-consuming. JAD: facilitated workshop for fast consensus but hard to schedule. Prototyping: early partial system to refine requirements, uncovers UI issues but may raise false expectations.
What are different processes for requirements gathering? Explain at least three. Prepare a comparative chart with pros and cons of each.
Processes for requirement gathering
Requirement gathering (elicitation) is the process of discovering the requirements of a system from users, customers and other stakeholders. Common processes (techniques) are:
- Interviews (structured / closed and unstructured / open)
- Questionnaires and surveys
- Observation and ethnography
- Joint Application Development (JAD) / facilitated workshops
- Brainstorming
- Prototyping
- Scenarios and use cases
- Document and existing-system analysis
In practice several are combined, because no single technique captures all requirements.
Explanation of three processes
1. Interviews The analyst meets stakeholders one to one or in small groups and asks questions about the current system and the new one.
- Closed interviews use a predefined list of questions.
- Open interviews have no fixed agenda; issues are explored freely. Steps: prepare (identify interviewees, study background, prepare questions), conduct (start with open and context-free questions, then specific ones, listen and take notes), and follow up (write a summary and get it confirmed). Example: interviewing the accounts officer of a college about how fees are collected, what reports are needed and what problems exist.
2. Joint Application Development (JAD) / facilitated workshop A structured meeting, often lasting one to several days, in which users, managers, analysts and developers work together under a neutral facilitator, with a scribe to record decisions. Participants review the scope, describe processes, list requirements, resolve conflicts on the spot and agree priorities. Example: a bank holds a two-day JAD session with branch managers, tellers, IT and audit staff to agree the requirements of a new loan-processing system.
3. Prototyping A quick, partial version of the system (often just screens) is built and shown to users. Users try it and suggest changes; the cycle repeats until requirements are clear. Prototypes may be paper sketches, clickable mock-ups or working code; they may be thrown away or evolved. Example: showing a clickable mock-up of a mobile ticket-booking app so users can decide the booking steps and seat-selection layout.
Comparative chart
| Process | Pros | Cons |
|---|---|---|
| Interviews | Rich, detailed information; can clarify doubts immediately; builds rapport | Time consuming; depends on interviewer skill; users miss tacit knowledge; biased by individuals |
| JAD / workshop | Fast agreement; conflicts resolved together; strong user ownership | Hard to schedule key people; costly; dominant people may control; needs skilled facilitator |
| Prototyping | Users see and use system; uncovers missing and UI requirements; reduces risk | Can be costly; users may expect it to be final; may encourage poor-quality design |
| Questionnaires | Reach many users cheaply; easy to analyse statistically | Low response rate; no follow-up questions; questions may be misread |
| Observation | Reveals real work practices and tacit requirements | Time consuming; people act differently when watched; misses rare events |
Choosing a process: interviews are best for getting an overview from key people, questionnaires when users are many and spread out, JAD when several departments must agree quickly, and prototyping when the user interface or requirements are unclear. Most projects combine two or three, for example interviews first, then a JAD session, then a prototype to confirm the agreed requirements.
✓ Answer checked by Claude Sonnet 5.5
Related questions
- Requirement gathering and analysis techniques · Software Engineering, chapter 1
- Importance of requirement engineering; elicitation techniques · Software Engineering, chapter 1
- Short note: Requirement gathering methods · Object Oriented Analysis and Design, chapter 2
- Distribution layouts, pros/cons, improvements · Water Supply Engineering, chapter 7 · asked 4×
- Phase shift method of SSB generation: pros and cons · Communication Systems, chapter 2 · asked 2×
- Collective intelligence pros and cons · Information System, chapter 4