You are absolutely correct. We've recently implemented a process where the QA person does all the requirements gathering and the writing of the specification (which includes a description of why the programming is needed ... what purpose will it fulfill). Once that is done, a meeting is held between management, the QA person who wrote the spec, and the developer who will be assigned the spec. The results of the meeting may require a spec adjustment, or more clarification. We encourage constant dialogue between the assigned QA and developer staff throughout the life of the project. This method has proven to be very successful for us, and has significantly reduced project cost.