Abstract
Although systems development testing is a critical ingredient in the successful design of a system, it is often regarded as an unnecessary effort needed only to correct errors on poorly designed (or unlucky) systems. The author explains why testing is, in fact, the one constant element of systems development that must be performed more often and why computer-aided software engineering (CASE) does not eliminate the need for testing.