Case Studies on Product Quality of Pair Programming - PowerPoint PPT Presentation

1 / 11
About This Presentation
Title:

Case Studies on Product Quality of Pair Programming

Description:

Intranet. Product Type. 6. 6. 6. 6. Iterations. 5.2. 5.5. 10 ... CAN and CLN are the same as above definitions. Relative Defect Density. DN= Si NN% / CLN X1000 ... – PowerPoint PPT presentation

Number of Views:45
Avg rating:3.0/5.0
Slides: 12
Provided by: Aar765
Category:

less

Transcript and Presenter's Notes

Title: Case Studies on Product Quality of Pair Programming


1
Case Studies on Product Quality of Pair
Programming
  • Hung-Fu (Aaron) Chang

2
Outline
  • Motivation
  • Case Study
  • Background Description
  • Data Source
  • Method
  • Summary of Empirical Results
  • Conclusion and Discussion
  • References

3
Motivation
  • The questions we have for pair programming is
  • Higher productivity?
  • Better readability?
  • Lower defect rates?
  • More useful in complex jobs?

4
Case Study Background Description
5
Case Study Data Source
6
Case Study Method (1/2)
  • Pair Programming Effort Percent
  • PP() Ep/Et
  • Ep is effort spent on PP during the iteration, Et
    is total programming effort spent on the
    iteration
  • Productivity
  • PN CLN/EN
  • CLN is the number of logical LOC produced with
    programming style N in the iteration, EN is
    effort spent with programming style N in the
    iteration
  • Rationale for PP

7
Case Study Method (2/2)
  • Density of Coding Standard Deviations
  • SNFN/CANX100
  • FN is the number of failures to adhere to coding
    standards (ie. Deviations) made with programming
    style N, CAN is the number of all physical LOC
    produced with programming style N in the
    iteration
  • Comment Ratio
  • RN (CAN - CLN)/CAN
  • CAN and CLN are the same as above definitions
  • Relative Defect Density
  • DN Si NN / CLN X1000
  • i is the index denoting each found defect, NN is
    the relative amount of effort spent with
    programming style N in the task where the defect
    I has been made

8
Case Study Summary of Empirical Results
9
Conclusion and Discussion
  • Real project data present empirical findings
    which is more clear and scientific
  • Cases showed pair programming does not provide
    some of the quality benefits as previous studies
    suggested
  • More detail level can be extended
  • Defect tracing in different programming styles
  • Can study on the severity of the defect

10
References
  • Roger S. Pressman, Software Engineering A
    Practitioners Approach, McGraw Hill ,2001
  • Hanna Hulkko, Pekka Abrahamsson, A Multiple Case
    Study on the Impact of Pair Programming on
    product quality, ICSE 2005
  • L. Williams and R. Kessler, Pair Programming
    Illuminated, Addison-Wesley, 2003
  • K. Nilsson, A Summary from a Pair Programming
    Survey Increasing Quality with Pair
    Programming, 2003

11
Questions?
Write a Comment
User Comments (0)
About PowerShow.com