Diagnosis-solution problems are similar to troubleshooting. Most diagnosis-solution problems require identifying a fault state, just like troubleshooting. However, in troubleshooting, the goal is to repair the fault and get the system back online as soon as possible, so the solution strategies are more restrictive. Diagnosis-solution problems usually begin with a fault state similar to troubleshooting (e.g. symptoms of a sick person). The physician examines the patient and considers patient history before making an initial diagnosis. In a spiral of data collection, hypothesis generation, and testing, the physician focuses in a specific etiology and differential diagnosis of the patient’s problem. At that point, the physician must suggest a solution. Frequently, there are multiple solutions and solution paths, so the physician must justify a particular solution. It is this ambiguity in solution paths that distinguishes diagnosis-solution problems from trouble shooting.

Diagnosis-solution problems are similar to troubleshooting. Most diagnosis-solution problems require identifying a fault state, just like troubleshooting. However, in troubleshooting, the goal is to repair the fault and get the system back online as soon as possible, so the solution strategies are more restrictive. Diagnosis-solution problems usually begin with a fault state similar to troubleshooting (e.g. symptoms of a sick person). The physician examines the patient and considers patient history before making an initial diagnosis. In a spiral of data collection, hypothesis generation, and testing, the physician focuses in a specific etiology and differential diagnosis of the patient’s problem. At that point, the physician must suggest a solution. Frequently, there are multiple solutions and solution paths, so the physician must justify a particular solution. It is this ambiguity in solution paths that distinguishes diagnosis-solution problems from trouble shooting.