Practice effective elicitation of requirements. Even if you write an outstanding BRD, it will be useless until you have identified and documented all of the relevant needs.
Use plain language free of jargon.
Examine previous projects.
Double-check the documentation.
High-level requirements, unlike comprehensive project plans, focus on the "what" of the project rather than the "how." This means that a high-level requirements list will lack granular information about each project phase and each team member's responsibilities.
Recognize the user's requirements.
The requirements should be clear.
Simple, specific, succinct, and comprehensive requirements should be used.
Testable requirements are essential.
Design and implementation should be kept independent from requirements.