In
software development,
engineering,
science,
manufacturing, and
business, its developers, researchers, manufacturers, and related personnel must understand and agree upon methods of obtaining data and making
measurements. It is common for a
physical property to be strongly affected by the precise method of testing or measuring that property. As such, fully documenting
experiments and measurements while providing needed documentation and descriptions of
specifications,
contracts, and test methods is vital. Using a
standardized test method, perhaps published by a respected
standards organization, is a good place to start. Sometimes it is more useful to modify an existing test method or to develop a new one, though such home-grown test methods should be validated and, in certain cases, demonstrate technical equivalency to primary, standardized methods. Again, documentation and full disclosure are necessary. A well-written test method is important. However, even more important is choosing a method of measuring the correct property or characteristic. Not all tests and measurements are equally useful: usually a test result is used to predict or imply suitability for a certain purpose. For example, if a manufactured item has several components, test methods may have several levels of connections: • test results of a raw material should connect with tests of a component made from that material • test results of a component should connect with
performance testing of a complete item • results of laboratory performance testing should connect with field performance These connections or
correlations may be based on published literature, engineering studies, or formal programs such as
quality function deployment.
Validation of the suitability of the test method is often required. ==Content==