Test and measurement
The purpose of a test is to discover faults of a product. Sometimes people say the contrary, i.e. to confirm that everything is hopefully alright. As a young engineer in automotive industry, once I have enthusiastically discovered a crucial problem in a test. The project manager was not amused and asked to repeat the test. Varying the test conditions slightly, I finally succeeded not to reproduce the fault any longer. Everybody was glad to keep the schedule, but the fault remained unfixed. Only a test showing as many faults as possible will be worth its costs. In order to avoid bad surprises close to delivery, it is reasonable to test during and after the design of a product. Early tests during development are often done in a less-systematic manner relying on the experience of the tester. Later tests approach requirements by standards and laws (precompliance). In the latest steps, compliance tests are done. In contrary to previous tests, now it is truly the goal of a manufacturer to demonstrate the fulfilment of standards and laws (and the goal of society and legislation referring to standards to keep immature or even unsafe products away from customers). This chapter will show equipment and methods for research and development in early stages as well as precompliance and compliance to common standards.
Test and measurement, Page 1 of 2
< Previous page Next page > /docserver/preview/fulltext/books/tr/pbtr012e/PBTR012E_ch9-1.gif /docserver/preview/fulltext/books/tr/pbtr012e/PBTR012E_ch9-2.gif