A successful project demands a correct and thorough requirements specification. This paper proposes techniques and strategies for handling business rules and requirements. The guidelines we provide are based on our own experiences with the development of large-scale enterprise applications as well as research we have done on best practices for requirements management proposed by other authors. The techniques are based on recursively classifying software requirements into logical coherent classes of requirements so that they improve developers' conception of the requirements and streamline the navigation to the next steps in the process. The techniques proposed in this paper, provide a mechanism for keeping track of requirements and help the development team to test the software in a more efficient way.