What is Requirement Gathering ? Explain different Requirement Gathering methods. [1+4]

Requirement Gathering is the initial phase of the Software Development Life Cycle (SDLC) where stakeholders' needs, expectations, and constraints are identified, analyzed, and documented. It ensures that the final product aligns with user requirements and business goals, reducing the risk of project failure.

Methods of Requirement Gathering

1. Interviews
   • One-on-one or group discussions with stakeholders (clients, users, developers).
   • Helps clarify ambiguous requirements and gather detailed insights.
   • Example: Interviewing bank employees to understand ATM system needs.

2. Surveys/Questionnaires

   • Structured questionnaires distributed to a large group of users.
   • Useful for gathering quantitative data and opinions.
   • Example: Sending a feedback form to students before developing an e-learning platform.

3. Observation

   • Directly observing users performing tasks in their natural environment.
   • Helps identify real-world problems and workflow inefficiencies.
   • Example: Watching hospital staff use outdated software to find pain points.

4. Workshops (Joint Application Development - JAD)

   • Collaborative sessions with stakeholders to brainstorm and refine requirements.
   • Encourages teamwork and quick decision-making.
   • Example: A JAD session with doctors and IT experts to design a telemedicine app.

5. Document Analysis

   • Reviewing existing documents (reports, manuals, contracts) to extract requirements.
   • Useful when historical data or past projects provide useful insights.
   • Example: Analyzing old purchase orders to design a new inventory management system.

6. Prototyping

   • Creating a mock-up or working model of the system to gather feedback.
   • Helps visualize requirements and validate ideas early.
   • Example: Building a wireframe of a mobile app before full development.

Each method has its strengths—interviews for depth, surveys for scalability, observation for realism, workshops for collaboration, document analysis for historical data, and prototyping for validation. A combination of these techniques ensures comprehensive requirement gathering.