These questions imply the need for at least two other measures. The firstis to
Valuate the quality of your code reviews. If you followed the code-review process
(see Chapter 9) and used an up-to-date code-review checklist, you would probably
have a high-yield review. The best indicator of this would be finding very few defects
while compiling. In the PSP 10 or fewer defects per KLOC during compiling
considered low. Without a pretty good code review, you are unlikely to get this low a number
Unfortunately, if your environment doesn't use a compile phase,
this measure is not available. In these cases, you can use the data on the coding- type
defects found in unit testing and, on a TSP team, the coding-type defects
found during inspections and unit testing. For these purposes, defect types 10
through 50 can be considered coding-type defects.
These questions imply the need for at least two other measures. The firstis to Valuate the quality of your code reviews. If you followed the code-review process(see Chapter 9) and used an up-to-date code-review checklist, you would probablyhave a high-yield review. The best indicator of this would be finding very few defectswhile compiling. In the PSP 10 or fewer defects per KLOC during compilingconsidered low. Without a pretty good code review, you are unlikely to get this low a number Unfortunately, if your environment doesn't use a compile phase, this measure is not available. In these cases, you can use the data on the coding- type defects found in unit testing and, on a TSP team, the coding-type defects found during inspections and unit testing. For these purposes, defect types 10through 50 can be considered coding-type defects.
การแปล กรุณารอสักครู่..