Building quality into a product mandates extensive testing throughout the product development process. Testing starts with Customer Needs and product conception and continues through the development process to the manufacturing floor. If Customer Need translations misinterpret the initial voice of the customer, then the delivered product will fail acceptance testing and validation. Product quality requires testing early and testing often inclusive of requirement translations.
Testing requires cycles of requirement analysis, test strategy development, test design, test case development, test execution, results reporting, defect management, traceability, and best practices to be incorporated into the concept, design, optimization, and manufacturing phases of product development. Requirements are to product development as arrows are to archery. Well written requirements provide the developer the tools to create the desired product and hit product goals. Building quality into requirements mandates that testing start with the verification of requirements.
Prior to the allocation of requirements, prior to creation of a model, and prior to the first line of code being written, the requirements must be tested just as the embedded software, embedded controller, and the product hardware would be tested. Requirements MUST be verified for correctness, conciseness, clarity, completeness, and continuity. Requirements specify the target to hit. Without measurable, testable, and quantifiable requirements, that have been verified and validated, it cannot be determined if the conceived product was developed.