Micro Pattern Fault-Proneness

Abstract

One of the goals of Software Engineering is to reduce, or at least to try to control, the defectiveness of software systems during the development phase. The aim of our study is to analyze the relationship between micro patterns (introduced by Gil and Maman) and faults in a software system. Micro patterns are similar to design patterns, but their characteristic is that they can be identified automatically, and are at a lower level of abstraction with respect to design patterns. Our study aims to show, through empirical studies of open source software systems, which categories of micro patterns are more correlated to faults. Gil and Maman demonstrated, and subsequent studies confirmed, that 75% of the classes of a software system are covered by micro patterns. In our study we also analyze the relationship between faults and the remaining 25% of classes that do not match with any micro pattern. We found that these classes are more likely to be fault-prone than the others. We also studied the correlation among all the micro patterns of the catalog, in order to verify the existence of relationships between them.

Smart contracts vulnerabilities: a call for blockchain software engineering?

“…• Design patterns • Testing The aim of BOSE is to create a bridge between traditional software engineering and blockchain software development, defining new ad-hoc methodologies, fault analysis [18], patterns [19], [20], quality metrics, security strategies and testing approaches [21] capable of supporting a novel and disciplined area of software engineering.…”

113 times Tomcat: A dataset

“…number of issues, defects, etc. ), or for patterns detection [5,3]. Additionally, it could be interesting to investigate if and how metrics change among different components of the same system.…”

113 times Tomcat: A dataset

“…To calculate these metrics, we used Understand 3.1 (build 766) 4 . We computed all the software metrics available in Understand which are categorized in the following groups: Complexity Metrics (e.g., McCabe Cyclomatic) 5 , Volume Metrics (e.g, Lines of Code) 6 , OO (e.g., Coupling Between Object Classes) 7 . For each system, we provided metrics for 3 different levels of granularity: system, file and class level, considering a total of 61 categories.…”