Meiyappan Nagappan
Brendan Murphy
ABSTRACT
Software metrics, such as code complexity metrics and code churn metrics, are used to predict failures. In this paper we study a specific set of metrics called code construct metrics and relate them to post release failures. We use the values of the code construct metrics for each file to characterize that file. We analyze the code construct metrics along with the post release failure data on the files (that splits the files into two classes: files with post release failures and files without post release failures). In our analysis we compare a file with post release failure to a set of files without post release failures, that have similar characteristics. In our comparison we identify which code construct metric, more often than the others, differs the most between these two classes of files. The goal of our research is to find out which code construct metrics can perhaps be used as symptoms of post release failures. In this paper we analyzed the code construct metrics of Eclipse 2.0, 2.1, and 3.0. Our results indicate that MethodInvocation, QualifiedName, and SimpleName, are the code constructs that differentiates the two classes of files the most and hence are the key symptoms/indicators of a file with post release failures in these versions of Eclipse.
- D. C. Arnold, D. H. Ahn, B. R. de Supinski, G. L. Lee, B. P. Miller, M. Schulz, "Stack Trace Analysis for Large Scale Debugging," Parallel and Distributed Processing Symposium, 2007. IPDPS 2007. IEEE International, vol., no., pp.1--10, 26--30. March 2007Google Scholar
- T. M. Chilimbi, B. Liblit, K. Mehra, A. V. Nori, K. Vaswani, "HOLMES: Effective statistical debugging via efficient path profiling," Software Engineering, 2009. ICSE 2009. IEEE 31st International Conference on, vol., no., pp. 34--44, 16--24. May 2009 Google ScholarDigital Library
- M. Fowler, "Refactoring: Improving the Design of Existing Code," 1st ed. Addison-Wesley, June 1999.Google Scholar
- S. Hangal, M. S. Lam, "Tracking Down Software Bugs Using Automatic Anomaly Detection," 24th International Conference on Software Engineering, 2002, pp. 291--300. Google ScholarDigital Library
- F. Khomh, M. D. Penta, and Y. G. Gueheneuc, "An Exploratory Study of the Impact of Code Smells on Software Change-proneness," 16th Working Conference on Reverse Engineering, 2009, pp. 75--84. Google ScholarDigital Library
- R. Marinescu, "Detection strategies: Metrics-based rules for detecting design flaws," in Proceedings of the 20th International Conference on Software Maintenance, 2004, pp. 350--359. Google ScholarDigital Library
- T. Zimmermann, R. Premraj, A. Zeller, "Predicting Defects for Eclipse," Third International Workshop on Predictor Models in Software Engineering (PROMISE'07: ICSE Workshops 2007), pp.9--16, 2007. Google ScholarDigital Library
Index Terms
- Which code construct metrics are symptoms of post release failures?
Recommendations
Are Slice-Based Cohesion Metrics Actually Useful in Effort-Aware Post-Release Fault-Proneness Prediction? An Empirical Study
Background. Slice-based cohesion metrics leverage program slices with respect to the output variables of a module to quantify the strength of functional relatedness of the elements within the module. Although slice-based cohesion metrics have been ...
Are architectural smells independent from code smells? An empirical study
Highlights- Case study analyzing the correlations among code smells, groups of code smells and architectural smells.
AbstractBackground. Architectural smells and code smells are symptoms of bad code or design that can cause different quality problems, such as faults, technical debt, or difficulties with maintenance and evolution. Some studies ...
Post Release Versions based Code Change Quality Metrics
WCI '15: Proceedings of the Third International Symposium on Women in Computing and InformaticsSoftware Metric is a quantitative measure of the degree to which a system, component or process possesses a given attribute. Bug fixing, new features (NFs) introduction and feature improvements (IMPs) are the key factors in deciding the next version of ...
Comments