I used to spend ages tying together my test cases to the requirements. One thing that always out-foxed me though was what to do with those tests that didn’t directly tie to a requirement. Or the new test ideas that popped up later in the process that threatened to destroy our carefully planned schedule. It wasn’t until I got to be in charge of my own testing that I realised I’d been getting it all wrong.I was focussing on the spec and requirements as being the single source for test ideas. I was planning coverage based on tests, which were based on this Word document. I was planning release dates based on a requirements document. I was lying to myself, management and our customers. There is more to the system than the requirements. The requirements are just a small section of the system. The system is bigger than that. So don’t become consumed with saying you are complete when you have tested just the requirements. There is much much more. And the diagram below barely scratches the surface.