| Home |
| Information on Debugging |
| Steps To Debugging |
| Quiz 1 |
| Quiz 2 |
| Quiz 3 |
| References & Logins |
Debugging is the method of figuring out why a process or system doesn't work properly
Debugging is ususally applied to computer or communication systems, especially software,
but the techniques are the same whether the systems are mechanical, architectural, business and so on.
Though debugging relies on logical reasoning and is usually "learned from experiecnce," there are general debugging principles and effective strageties.
We can relate debugging to everyday life not just IT. People debug and troubleshoot all the time.
For example when their cars don't start, they figure out whether the battery is dead or whether there is a lack of fuel.
faults and failures in everyday life usually invlove otherwise correct, working systems with a broken or worn out part.
That is the system is properly designed and constructed, however some part failed.
When debugging an Information system it is slightly different. In Information Systems, we might have entered wrong data or wrong configuration
information in a working system. When it's corrected, the system works. Another possibility is the system might have a logical design error.
In software such logical errors are quite possible even in commerical software, and users must be aware that they may not be using a correct, working system.
When debugging an information system, remember that we a almost contribute to part of the problem. We command the computer to do tasks and we input
the information. When the computer is in an error state despite our thinking that everything should have worked perfectl, two of the three possible problems
-wrong data, wrong command, or broken system invlove humans. Futhermore, since the hardware and software have been tested thoroughly, the two possiblities that
involve us are the two most likely possibilites. Our commands or data probably led to the problem, so we'll have to fix them. Computers cannot debug themselves