4.1 Test activity drives project convergence

Test has classically been defined as being the process of executing a program with the intent of finding errors [1]. For aggressive, high-tech companies pursuing new markets, this is not the case. In a global sense, these companies face an ever-changing target market where customer needs evolve. Initial product definition is based primarily upon speculation. As a result, it is imperative that the product track changes in customer need, which results in requirements changes over time, or, as it is called, feature creep. Requirements also change as a result of new information collected during product development; they often have to be enhanced to resolve ambiguity. In some instances they are simply incorrect and need to be partially rewritten.

A mechanism must be put in place to first address the ambiguity and inaccuracy of product requirements. Second, this mechanism must guide product development activity toward an ever-changing market need. Last, it must serve to efficiently coordinate the efforts of engineers working on diverse technologies used in complex embedded systems. This mechanism is called test.

Test is an active process though which product development is guided toward actual market need. In its simplest form, test exercises the product in a manner consistent with its actual use in the marketplace. Results are used in characterizing the product and managing its release to the customer with the full expectation that the delivery is not bug free. As will be seen, there can be up to four phases of...