The process of Requirement Analysis

Once all the stakeholder requirements have been gathered, a structured analysis of these can be done after modeling the requirements. Some of the Software Requirements Analysis techniques used are requirements animation, automated reasoning, knowledge-based critiquing, consistency checking, analogical and case-based reasoning.

It is always a next to impracticable job to get a) faultless requirements b) to do perfect analysis on the requirements c) lastly to convert them faultlessly into design or take to next SDLC level. In fact irrespective of metrics we use to measure requirements and take it to next level we should always keep in mind that the person who is gathering them and who is giving them both are human beings and lot of noise get introduced while in their communication. Hence requirements are bound to misled from their actual meaning to the understanding of gatherer.
This makes almost 30% of requirements either completely useless or almost impossible to convert them into a software product. Now should be done minimize such a huge gap. Almost all of the requirements should be supported by facts and data. Always remember the difference between stakeholders and end users, end users will be using your solutions so always double check any gathered requirement with them.