Requirements must be specified before attempting to construct a product or develop a software. If the correct requirements are not known, one cannot design or build the correct product or software, and consequently the product does not fulfill the user's needs.

Statistics show that 60% of errors originate with the requirements and analysis activities and therefore already exist at design time. Though product developers always have the opportunity to eliminate the largest category of error, they choose, or worse their managers decide, to rush headlong into constructing the wrong product. And thus they pay many times the price for the product than they would have if the requirements had been gathered and managed correctly at the very first beginning.

"Keep in mind that poor quality is passed on. It is as simple as that."