Download presentation
Presentation is loading. Please wait.
1
Lecturer: Dr. AJ Bieszczad Chapter 1312-1 Predictive accuracy Predictions are biased when they are consistently different from the actual value. Predictions are noisy when successive predictions fluctuate more wildly than the actual value. U-plots can help us understand and reduce bias. Prequential likelihood helps reduce noise.
2
Lecturer: Dr. AJ Bieszczad Chapter 1312-2 Table 13.5. Code inspection statistics from AT&T.
3
Lecturer: Dr. AJ Bieszczad Chapter 1312-3 Table 13.6. Yield calculation. ActivityFaults found Faults injected Design inspection Code inspection CompileTestPost- developm ent Planning0222222 Detailed design 0245566 Design inspection 4 Code2271012 Code inspection 3 Compile5 Test4 Post- development 2 TOTAL20 Design inspection yield 4/4 = 100%4/6 = 67% 4/7 = 57.1% 4/7 = 57.1% 4/8 = 50% 4/8 = 50% Code inspection yield 3/5 = 60%3/10 = 30% 3/14 = 25.5% 3/16 = 18.8% Total yield4/4 = 100%6/6 = 100% 9/9 = 100%9/14 = 64.3% 9/16 = 56.3% 9/20 = 45%
4
Lecturer: Dr. AJ Bieszczad Chapter 1312-4 Table 13.7. Aggregate results from SEI benefits study. (Herbsleb et al. 1994) CategoryRangeMedian Total yearly cost of software process improvement activities$49,000 to $1,202,000 $245,000 Years engaged in software process improvement1 to 93.5 Cost of software process improvement per engineer$490 to $2004$1375 Productivity gain per year9% to 67%35% Early detection gain per year (faults discovered pre-test)6% to 25%22% Yearly reduction in time to market15% to 23%19% Yearly reduction in post-release fault reports10% to 94%39% Business value of investment in software process improvement (value returned on each dollar invested) 4.0 to 8.85.0
5
Lecturer: Dr. AJ Bieszczad Chapter 1312-5 Organization of Cleanroom studies Controlled experiment comparing reading with testing Controlled experiment comparing Cleanroom with Cleanroom-plus-testing Case study of Cleanroom on 3-person development team and 2-person test team Case study on 4-person development team and 2-person test team Case study on 14-person development team and 4-person test team
6
Lecturer: Dr. AJ Bieszczad Chapter 1312-6 Table 13.8. Results of reading vs. testing experiment 1. ReadingFunctional testingStructural testing Mean number of faults detected5.14.53.3 Number of faults detected per hour of use of technique 3.31.8 Table 13.9. Results of SEL case studies. Baseline valueCleanroom development Traditional development Lines of code per day26 20 Changes per thousand lines of code 20.15.413.7 Faults per thousand lines of code 7.03.36.0
7
Lecturer: Dr. AJ Bieszczad Chapter 1312-7
8
Lecturer: Dr. AJ Bieszczad Chapter 1312-8
9
Lecturer: Dr. AJ Bieszczad Chapter 1312-9
10
Lecturer: Dr. AJ Bieszczad Chapter 1312-10
11
Lecturer: Dr. AJ Bieszczad Chapter 1312-11
12
Lecturer: Dr. AJ Bieszczad Chapter 1312-12
13
Lecturer: Dr. AJ Bieszczad Chapter 1312-13
14
Lecturer: Dr. AJ Bieszczad Chapter 1312-14
15
Lecturer: Dr. AJ Bieszczad Chapter 1312-15
16
Lecturer: Dr. AJ Bieszczad Chapter 1312-16
17
Lecturer: Dr. AJ Bieszczad Chapter 1312-17
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.