what elements should be in each requirement (e.g., language construct), ensuring a full range of requirements categories are articulated (e.g., coverage), and establishing a requirements peer review practice with clear criteria. This will help a project get the whole picture of the requirements with completeness and clarity.
1. "Why Isn't Someone Coding Yet (WISCY)? Avoiding Ineffective Requirements", by Charlene Gross, SEPG Conference, May 2004, Software Engineering Institute.
2. "Managing Requirements", Ludwig Consulting Service, August 2006, http://www.jiludwig.com/Categories.html
3. "ABCs of Requirements Engineering", by Mario E. Moreira, CM Journal in CM Crossroads, June 2005