ABSTRACT
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Testing may be defined as subjecting a device to conditions that indicate
its weaknesses, behavior characteristics, and modes of failure. It is a con-
tinuous operation throughout the development cycle that provides pertinent
team. Testing may be performed for three
basic reasons: basic information, verification, and validation. Basic information testing may include vendor evaluation, vendor
comparison, and component limitability. Verification is the process of evaluating the products of a given phase to ensure correctness and consistency
with respect to the products and standards provided as input to that phase.
Validation includes proving the subsystems and system meet the requirements
of the product specification. Testing is an essential part of any engineering development program. If the
development risks are high, the test program becomes a major component of
the overall development effort. To provide the basis for a properly integrated development test program, the design specification should cover all criteria
to be tested including function, environment, reliability, and safety. The test
program should be drawn up to cover assurance of all these design criteria. The ultimate goal of testing is assuring that the customer is satisfied. It is
the customer who pays the bills, and if we are to be successful in business
we have to solve their problems. We aim for quality, but quality isn’t just an abstract ideal. We are developing systems to be used, and used successfully, not
to be admired on the shelf. If quality is to be a meaningful and useful goal in
the real world, it must include the customer.
