This article states that “developer misunderstandings of user requirements are the leading cause of defects in software.” I do believe the developer should be better connected to the actual requirement. However even when using different methodologies, like Agile, there can be a disconnect. Documentation, conversations, phone calls, meetings after meetings all take place before the developer sits down to code. It is essentially up to the developer to translate what needs to be done based on a myriad of communication. And yet everyone is trying to figure out why this disconnect exists and the answer always seems to be either less process or more process! Niether of which truly addresses the problem. In my mind within a project you have different groups, all with very different needs. Analyst may do better with more process while developers prefer less process.
In my humble opinion there is one fundamental need for all parties involved, and that is a simple concise definition of the requirement. If all the meetings, conversations, emails and documentation could center around this simple thing we would have a common ground from which begin and end.