ABSTRACT
Testing software is by no means an easy task. For anything but the simplest programs, it is an extremely demanding discipline that must be carefully planned and controlled if it is to stand any chance of giving a reliable guide to the innate quality level of the product in terms of remaining residual defects. However, the fundamental point of diagram is to underline the pivotal role played by these documents in ensuring that quality is being built into software, and that this is taking place before a line of code has ever been written. As the awareness of software engineering and quality issues on the part of purchasers improves, there is likely to be increasing demands to inspect test records of a released version of code. Create a document describing the procedure to be followed in testing software. Include the necessary prerequisites before testing can commence, how testing is to be conducted, and how the results are to be recorded.
