Wgu C857 Study Guide Rated A+

Module Test {Ans: The purpose of a module test is to find discrepancies between the program's modules and their *module interface specifications*}Debugging By Brute Force {Ans: Least mentally straining, but also the least effective and time consuming -Debugging with a storage dump. -Debugging according to the common suggestion to ''scatter print statements throughout your program.'' -Debugging with automated debugging tools.}Error-Repairing Techniques {Ans: -Where there is one bug, there is likely to be another -Fix the error, not just the symptom -The probability of the fix is not 100% -The probability of the fix being correct drops as the size of the program increases -Beware of the possibility that an error correction creates a new error -The process of error repair should put you temporarily back into the design phase -Change the source code, not the object code}Integration Test {Ans: Tests that the *System Design* and the *Program Structure Design* do not behave appropriately *Is not regarded as a separate test, however, is being tested iteratively throughout module testing*}External Specifications (Software Development Process) {Ans: Define the exact representation of the program to the users}Review {Ans: An evaluation of a life-cycle work product(s) or project status