Requirements Gathering Techniques
Requirements gathering is the process of collecting and documenting what a system must do. It is one of the most critical phases of SAD because inaccurate or incomplete requirements lead to system failure. Analysts use multiple techniques to ensure all stakeholder needs are captured.
Types of Requirements
| Type | Description | Example |
|---|---|---|
| Functional | What the system should do | Generate monthly sales reports |
| Non-Functional | How the system should perform | Response time under 2 seconds |
| Business Rules | Policies governing operations | Discount applies only for orders over $100 |
| Constraints | Limitations on the system | Must run on existing hardware |
Technique 1: Interviews
One-on-one conversations with stakeholders to gather detailed information about their needs, processes, and pain points.
Advantages:
- Allows in-depth exploration of complex topics
- Non-verbal cues provide additional insight
- Can address follow-up questions immediately
Disadvantages:
- Time-consuming for large groups
- Interviewer bias can influence responses
- Requires skilled interviewer
Technique 2: Questionnaires
Written or electronic surveys distributed to a large number of stakeholders to collect standardized information.
Best for:
- Gathering data from many people across locations
- Quantifying preferences and satisfaction levels
- Validating findings from other techniques
Technique 3: Observation
Analysts watch users perform their daily tasks to understand actual workflows, identify bottlenecks, and discover undocumented requirements.
Two modes:
- Passive observation: Watching without interfering
- Active observation: Participating in the work while observing
Technique 4: Joint Application Development (JAD)
A facilitated workshop bringing together stakeholders, users, and analysts to collaboratively define requirements in real-time.
JAD Session Structure:
1. Introduction & Objectives (15 min)
2. Current System Review (30 min)
3. Requirement Brainstorming (60 min)
4. Prioritization & Conflict Resolution (45 min)
5. Summary & Next Steps (15 min)Technique 5: Document Analysis
Reviewing existing documentation such as procedure manuals, forms, reports, business plans, and system specifications to understand current operations and requirements.
Technique 6: Prototyping
Building a preliminary version of the system to gather feedback and validate requirements with users before full development begins.
Combining Techniques
No single technique captures all requirements. Effective analysts combine multiple techniques to cross-validate findings and ensure completeness. The right mix depends on project size, complexity, and stakeholder availability.
Summary
Requirements gathering is the foundation of successful system development. Mastering multiple techniques and knowing when to apply each one ensures that analyst capture comprehensive, accurate, and actionable requirements.