软件工程教学课件Chapter-17.pptVIP

Debugging Effort * Symptoms Causes * Consequences of Bugs * Debugging Techniques brute force / testing backtracking induction deduction * Correcting the Error Is the cause of the bug reproduced in another part of the program? In many situations, a program defect is caused by an erroneous pattern of logic that may be reproduced elsewhere. What next bug might be introduced by the fix Im about to make? Before the correction is made, the source code (or, better, the design) should be evaluated to assess coupling of logic and data structures. What could we have done to prevent this bug in the first place? This question is the first step toward establishing a statistical software quality assurance approach. If you correct the process as well as the product, the bug will be removed from the current program and may be eliminated from all future programs. * Final Thoughts Think -- before you act to correct Use tools to gain additional insight If you’re at an impasse, get help from someone else Once you correct the bug, use regression testing to uncover any side effects * * 症状和原因 症状 原因 症状与原因出现的地方可能相隔很远 症状可能在另一个错误被改正时消失 实际上可能是由非错误因素引起的 可能是由系统或编译错误引起的 可能是人们坚信的假定引起的 症状可能是间断的 symptom cause symptom and cause may be geographically separated symptom may disappear when another problem is fixed cause may be due to a combination of non-errors cause may be due to a system or compiler error cause may be due to assumptions that everyone believes symptom may be intermittent * 错误的结果 危害度 轻微 普通 反感 严重 非常严重 灾难性 传染 错误类型 错误类型： 功能相关的错误、系统相关的错误、数据错误、 编码错误、设计错误、文档错误、违反标准等。 damage mild annoying disturbing serious extreme catastrophic infectious Bug Type Bug Categories: function-related bugs, system-related bugs, data bugs, coding bugs, design bugs, documentation bugs, standards violations, etc. * 调试技术 蛮干发/ 测试 回溯法 归纳法 排除法 * 纠正错误 这个错误的原因在程序的另一部分也产生过吗？在多数情况下，程序的错误是由错误的逻辑模式引起的，这种逻辑模式可能会在别的地方出现。 进行修改可能引发的“下一个错误”是什么？在改正错误之前，应该仔细考虑源代码（最好包括设计）以评估逻辑与数据结构之间的耦合