Ans: (i) Equivalence class testing is based on partitioning the input domain of a program into a number of equivalence classes so that the test of a representative value of each class is equivalent to testing any other value. Two steps for this method are Identify equivalence class by taking each input condition and partition into valid and invalid classes. Generate the test cases using the equivalence class of the previous step. The test cases are generated for the valid and the invalid classes. (ii) User documentation contains descriptions of the functions of a system without reference to how these functions are implemented. Examples are installation guide and reference guide. System documents contain all the facets of the system, including analysis, specification design, implementation, testing, security error diagnosis and recovery. Examples are SRS and system test plan. (iii) Core dumps are a debugging technique. A printout of all relevant memory locations is obtained and studied. All dumps should be well documented and retained for possible use on subsequent problems. Its advantages are that a complete dump of memory at a crucial time is obtained Require CPU and I/O time and can get expensive if used indiscriminately. Sometimes it is difficult to interpret the dump which is represented using hexadecimal numbers.