Success in software development is highly dependent on understanding and then capturing requirements. However, the quality of requirements specifications varies widely. Missing, poorly stated, or ambiguous requirements cause problems and result in rework. Combating these problems requires us to ask the right questions to make the requirements specifications better, clearer, and more complete, and then describe requirements in a clear, complete, consistent, unambiguous, and precise way.

Methods / Techniques for Requirement Analysis

1. One-on-one interviews
2. Group interviews
3. Facilitated sessions
4. Joint application development (JAD)
5. Questionnaires
6. Prototyping, Flowcharting, block diagrams, sequence diagrams etc.
7. Use cases
8. Following people’s work routine
9. Brainstorming
10. Domain Modelling, Process modelling