1 / 19

Laitenberger, etal IEEE TOSE May 2001

An Internally Replicated Quasi-Experimental Comparison of Checklist and Perspective-Based Reading of Code Documents. Laitenberger, etal IEEE TOSE May 2001. Overview - What did you learn?. Inspections Experimentation. Inspections. SINCE Fagan's initial work presented in 1976 [24], software

vanessad
Download Presentation

Laitenberger, etal IEEE TOSE May 2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Internally Replicated Quasi-Experimental Comparison of Checklist and Perspective-Based Reading of Code Documents Laitenberger, etal IEEE TOSE May 2001

  2. Overview - What did you learn? • Inspections • Experimentation

  3. Inspections SINCE Fagan's initial work presented in 1976 [24], software inspection has emerged in software engineering as one of the most effective and efficient methods for software quality improvement. A software inspection usually consists of several activities including planning, defect detection, defect collection, and defect correction [53].3 Inspection planning is performed by an organizer who schedules all subsequent inspection activities. The defect detection and defect collection activities can be performed either by inspectors individually or in a group meeting.

  4. What is PBR Reading?

  5. Exp Context Guidelines – C2 C2: If a specific hypothesis is being tested, state it clearly prior to performing the study and discuss the theory from which it is derived, so that its implications are apparent. Recent empirical findings reveal that the synergy effect of inspection meetings is rather low in terms of impact on defects detected [55], [85], [44]. Therefore, defect detection can be considered as an individual rather than a group activity. the effectiveness5 of PBR and its cost per defect ratio are compared with those of CBR.

  6. Conduct and collect – DC1 DC1: Define all software measures fully, including the entity, attribute, unit and counting rules. 5. In this study, effectiveness is defined as the proportion of all defects in the code that were found by applying one reading technique.

  7. Exp Context C1 C1: Be sure to specify as much of the industrial context as possible. In particular, clearly define the entities, attributes, and measures that are capturing the contextual information.

  8. Exp Design Guidelines - TTYP D1: Identify the population from which the subjects and objects are drawn. D2: Define the process by which the subjects and objects were selected. D3: Define the process by which subjects and objects are assigned to treatments.

  9. Evaluation of Experiment

  10. Exp Design Guidelines – class D4: Restrict yourself to simple study designs or, at least, to designs that are fully analyzed in the statistical literature. If you are not using a well-documented design and analysis method, you should consult a statistician to see whether yours is the most effective design for what you want to accomplish.

  11. Conduct and collect – DC3? DC3: Describe any quality control method used to ensure completeness and accuracy of data collection.

  12. Conduct and collect – DC5 and 6? DC5: For observational studies and experiments, record data about subjects who drop out from the studies. DC6: For observational studies and experiments, record data about other performance measures that may be affected by the treatment, even if they are not the main focus of the study.

  13. Analysis A1: Specify any procedures used to control for multiple testing. A2: Consider using blind analysis. A3: Perform sensitivity analyses.

  14. Analysis A4: Ensure that the data do not violate the assumptions of the tests used on them. A5: Apply appropriate quality control procedures to verify your results. A3: Perform sensitivity analyses.

  15. Presentation P1: Describe or cite a reference for all statistical procedures used. P2: Report the statistical package used. P3: Present quantitative results as well as significance levels. Quantitative results should show the magnitude of effects and the confidence limits.

  16. Presentation P4: Present the raw data whenever possible. Otherwise, confirm that they are available for confidential review by the reviewers and independent auditors. P5: Provide appropriate descriptive statistics. P6: Make appropriate use of graphics.

  17. Interpretation I1: Define the population to which inferential statistics and predictive models apply. I2: Differentiate between statistical significance and practical importance. I3: Define the type of study. I4: Specify any limitations of the study.

  18. Results?

  19. For L7 (Tues 9/17) • L Prechelt and B Unger, “An experiment measuring the effects of Personal Software Process (PSP) Training”, IEEE TOSE may 2000 pp465-479

More Related