1 / 40

Code Inspection

Code Inspection. Robson Ytallo Silva de Oliveira. Overview. Introduction Code Inspection Techniques Code Inspection : A Survey Summary Concluding Remarks. Introduction. “T he software inspection process is generally considered a software engineering best practice” [Wheeler, 1996].

francine-richard
Download Presentation

Code Inspection

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. Code Inspection Robson Ytallo Silva de Oliveira

  2. Overview • Introduction • Code Inspection Techniques • Code Inspection : A Survey • Summary • Concluding Remarks

  3. Introduction “The software inspection process is generally considered a software engineering best practice” [Wheeler, 1996].

  4. Introduction • Code InspectionGoals • Find and fix defects • InSoftware Reuse • Make the code easier to understand and change • Improve the maintainability of the code • Minimizing redundancies • Improving language proficiency • Improving safety and portability

  5. Introduction • Real Example of Benefits • NASA (Jet Propulsion Laboratory) • Saved $25,000 per Inspection • Around 300 Inspections • Saved $7,5 million

  6. Code Inspection Techniques • The Relevant Techniques • Formal Technical Review • Pratical Model • Variants of the Pratical Model

  7. Code Inspection Techniques • Formal Technical Review (FTR) • Five-Step Inspection Method • Overview • Preparation • Inspection Meeting • Rework • Followup

  8. Code Inspection Techniques • Pratical Model • Three-Step • Preparation • Collection • Repair

  9. Code Inspection Techniques • Variants of the Pratical Model • Active Design Review (ADR) • Phased Inspection (PI) • N-Fold Inspections • High Price

  10. Code Inspection : A Survey • Before 1976 • From 1976 until today • Several Variants • New Techniques • New Models • Tools

  11. [Hatton, 1995] • Compiler Writers’ Responsability • Static Inspection • Advantage • Disadvantage

  12. [Porter et al., 1997] • Cost-Benefits Experiment for Code Inspection Techniques • Conclusions • Advantage • Problems • Measurement Problems • Discontinuing Treatments • Simplified Instrumentation

  13. [Porter et al., 1997] • Motivation • [Votta et al., 1985] • Preparation X Inspection Meeting • Real Group x Nominal Group • Experiment 1 • Conclusion • Paper’s Conclusion

  14. [Wood et al., 1997] • [Basili et al., 1980] • Techniques Comparation • Techniques Combination • Conclusion

  15. [Johnson, 1998]

  16. [Brykczynski, 1999] • Checklists • Update “Build organizational knowledge bases on review.” [Johnson, 1998] • Size

  17. [Travassos et al., 1999] • Reading Techniques • Importance in OO Designs • Problem

  18. [Kimble et al., 2000] • An Alternative Source Code Analysis • Parser • Modified Notation • Control Flow Diagram – CFD • Thread Analysis

  19. [Adams, 2000] • Before 1976 • Apollo 11 • Inspections and Reviews’ Necessities

  20. [Nandivada et al., 2000] • The 9 Quadrant Model for Code Reviews

  21. [Nandivada et al, 2000]

  22. [Siy et al., 2001] • Motivation • Minor defects • Proposal • Classify soft maintenance issues • Cost benefit model • Survey • Results • Conclusions

  23. [Biffl et al., 2001] • Statistical Model • Inspection Effectiveness • Economic Model • Inspection Benefits • Conclusions • Best mix of Reading Techniques • Optimal Team Size • Additional Inspector

  24. [Biffl et al., 2001] • Reinspections • Cost-Benifit Model • Conclusion

  25. [Wohlin et al., 2002] • Benchmarking • Inspection Benchmarking “Build organizational knowledge bases on review.” [Johnson, 1998] • Conclusion

  26. [Tyran et al., 2002] • Real Group vs Nominal Group • Group Support Systems – GSS “Investigate computer-mediated review technology.” [Johnson, 1998] • Conclusion

  27. [Parnas et al., 2003] • Inspection Methods vs Informal Reviews • Workshop on Inspection in Software Engineering – WISE • IEEE Software Magazine • IEEE Transactions on Software Engineering • The future of inspection • Refine the software Inspection Process • Systems with Real-Time requirements and Concurrent Activities • Tool Supported Software Inspection

  28. [Thelin et al., 2003] • Usage-based Reading Technique (UBR) • Conclusion

  29. [Travassos et al., 2004] • Framework ISPIS • Integration Mechanism • Historical Data • Conclusion “Build organizational knowledge bases on review.” “Investigate computer-mediated review technology.” [Johnson, 1998]

  30. [Remillard, 2005] • Source Code Review Systems • Bugzilla • It isn’t Formal Inspections Supported • CodeStriker • Pure text files • Recommendation

  31. Summary

  32. Concluding Remarks • FTR – Some Variants • Cost-Benefit • Future • Real-Time Requirements • Concurrent Activities

  33. Towards a well-defined requirements for software components inspection • Meetings • Preparation • Reviews • Cost Benefit • Tools • Models • Benchmarking

  34. References • HATTON, Les et al. Static Inspection: Tapping the whells of software. 1995. • PORTER, Adam et al. An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development. 1997. • PORTER, Adam et al. Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies. 1997. • WOOD, Murray et al. Comparing and Combining Software Defect Detection Techniques: A Replicated Empirical Study. 1997.

  35. References • JOHNSON, Philip. Reengineering Inspection. 1998. • BRYKCZYNSKI, Bill. A Survey of Software Inspection Checklists. 1999. • TRAVASSOS, Guilherme et al. Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality. 1999. • KIMBLE, James et al. An Alternative Source Code Analysis. 2000. • ADAMS, Tom. The God of Inspection. 2000.

  36. References • NANDIVADA, Ravi et al. The 9 Quadrant Model for Code Reviews. 2000. • SIY, Harvey et al. Does The Modern Code Inspection Have Value?. 2001. • BIFFL, Stefan et al. Influence of Team Size and Defect Detection Technique on Inspection Effectiveness. 2001. • BIFFL, Stefan et al. Investigating the Cost-Effectiveness of Reinspections in Software Development. 2001.

  37. References • WOHLIN, Claes et al. Software Inspection Benchmarking - A Qualitative and Quantitative Comparative Opportunity. 2002. • TYRAN, Craig et al. Improving Software Inspections with Group Process Support. 2002. • PARNAS, David et al. The Role of Inspection in Software Quality Assurance. 2003. • THELIN, Thomas et al. Prioritized Use Cases as a Vehicle for Software Inspections. 2003.

  38. References • TRAVASSOS, Guilherme et al. ISPIS: A Framework Supporting Software Inspection Processes. 2004. • REMILLARD, Jason. Source Code Review Systems. 2005.

  39. That's All Folks

More Related