Once everyone has a clear picture of their roles and responsibilities in integration, and a stable set of platforms are established for integration, it is essential that a clear a well-formed set of verification requirements is established. These driving functional and performance requirements are essential for achieving a project's quality targets. It's not enough to just ask everyone to go do testing; there needs to be a way to 'close the loop' against the product requirements as they were flowed down to the various component producers, and determine how those components should and do interact. This focus must be on integration requirements, not requirements of the separate components, and assess how well the desired functional integration has been achieved through the development process. It also is important because requirements are so often themselves incorrect, inconsistent, or sufficiently ambigious that they are misunderstood.