Are you using a particular methodology? That very much drives how you approach requirements.
I like how Larman's approaches this in his "Applying UML and Patterns".
Wikipedia is also a starting point to find your way.
Chetan Parekh wrote:Please recommend good books on Software Requirement Gathering and Management.
Althougth it is focused upon a specific tool the following book provides a very good look at gathering requirements and analyzing them in order to provide a useful business/development strategy.
Busess Process Management with JBoss jBPM: A Practical Guide for Business Analysts by Matt Cumbrelidge (PACKT Publishing, 2007).
Ran
Check your pockets for water buffalo. You might need to use this tiny ad until locate a water buffalo: