[Editor Note to Publisher: This Figure had to be assembled in parts as it could not be Pasted special without crashing Powerpoint and running out of memory in Word?????? Figure in Powerpoint is Complete – See Debugging *293]
1. A System is not mere specifications of itself, or a “mock up” Prototype. The “debugging” Process should include fault-consequent revalidation (in software called “regression testing”) that the fault “removal” Process has “succeeded”, and hopefully that it has not injected additional identifiable faults inadvertently.
2. The implication is that some QC Processes on Systems (for example, testing, field trials, user complaints, service/maintenance or repair analysis) have identified some faults, and “debugging” Means removing the faults, which were identified by that Process. The Debugging Process is well downstream of the corresponding SQC Processes of Editing and Edit-Auditing, which deal with fixing Defects (in specifications), not faults (in Systems).
This Concept entered by Diane O'Brien.