If you’ve taken part in any sort of web project, you have hopefully defined, referenced, and/or tested a requirement. You’ve also felt the impact of requirements gathering on your work. A good requirement can make your job easier by taking the mystery out of what is needed. A bad requirement can lead to more work, or even wasted effort. I explored how to mine for detailed requirements in Questioning (the) Authority. In the year since I wrote that article, I’ve wrestled with how to manage the natural evolution of business requirements to functional requirements as you progress through a project. How do you create traceable requirements?