Chapter15ProjectingDefects（缺陷预测）.pptVIP

山东大学齐鲁软件学院 Chapter 15 Projecting Defects(缺陷预测) outline Analyze and use your defect data to help improve both planning accuracy and product quality. Determine how best to prevent or find the defects you inject. Control the quality of your work. Defect rates Defect injection rate typically range from about 50~250 defects per KLOC. With Figure15.1 15.2 shown: Defect density as a function of the years. Some quality practices learn with experience. defect levels are largely a matter of personal discipline. After PSP training, engineers understood the numbers and types of defects. And then reduced their total defect injection rates. Defect rates number are big! Defect injection is a natural consequence of being human. Average 100 defects/KLOC About 50 defects/KLOC after PSP training. So there are 50,000 defects in a 1,000,000 LOC program. All of them must be found and fixed before delivery. Using defect data Gather defects datahelp understanding the defects you inject to your program. Design a personal checklistfor code reviewing to remove defects. Establish a code standardhelp to prevent defects injected in coding. Then what’s our next step? what’s our final goal? Using Defect Data Task: Using historical defect data to make a reasonably good projections of the number of defects you will inject and remove in each phase of a programming project. Advantage: By accurate estimates of defect levels, you can determine the likely quality of the program being developed. Then you can decide whether additional defect-removal steps are needed. The final goaldefect-free programming, can not be achieved only by estimate, it should be approached by systematic work and step by step. Defects collect, Defect remove and preventcode review and code standard, Defect estimate. Defect density Defect density(Dd): the defects per thousand lines of code, measured by defects/KLOC. Add up the total numbers of defects found. Count the number of new and changed LOC Calculate the defects per