Software code quality and source code metrics dataset

2009

The validation of software quality metrics lacks statistical significance. One reason for this is that the data collection requires quite some effort. To help solve this problem, we develop tools for metrics analysis of a large number of software projects (146 projects with ca. 70.000 classes and interfaces and over 11 million lines of code). Moreover, validation of software quality metrics should focus on relevant metrics, i.e., correlated metrics need not to be validated independently. Based on our statistical basis, we identify correlation between several metrics from well-known objectoriented metrics suites. Besides, we present early results of typical metrics values and possible thresholds. 1.

VIII SBQS-Simpósio Brasileiro De Qualidade De …, 2009

The overall goal of this work is to study software metrics and develop a tool for automatic quality evaluation of source code for free and open source software (FLOSS). This tool will be based on metrics that, combined and configured by specialists, will provide automatic analysis of features such as flexibility, clarity, modularity and software maintainability.

Electron. Commun. Eur. Assoc. Softw. Sci. Technol., 2013

Measuring source code maintainability has always been a challenge for software engineers. To address this problem, a number of metrics-based quality models have been proposed by researchers. Besides expressing source code maintainability in terms of numerical values, these models are also expected to provide explicable results, i.e. to give a detailed list of source code fragments that should be improved in order to reach higher overall quality. In this paper, we propose a general method for drilling down to the root causes of a quality rating. According to our approach, a relative maintainability index can be calculated for each source code element for which metrics are calculated (e.g. methods, classes). The index value expresses the source code element’s contribution to the overall quality rating. We empirically validated the method on the jEdit open source tool, by comparing the results with the opinions of software engineering students. The case study shows that there is a high...

Abstract The open source software ecosystem comprises more than a hundred thousand applications of varying quality. Individuals and organizations wishing to use open source software packages have scarce objective data to evaluate their quality. However, open source development projects by definition allow anybody to read, and therefore evaluate their source code. In addition, most projects also publish process-related artefacts, such as bug databases, mailing lists, and configuration management system logs.

Lecture Notes in Computer Science, 2014

The number of software systems under development and maintenance is rapidly increasing. The quality of a system's source code tends to decrease during its lifetime which is a problem because maintaining low quality code consumes a big portion of the available eorts. In this research we investigated one aspect of code change, the version control commit operations (add, update, delete). We studied the impact of these operations on the maintainability of the code. We calculated the ISO/IEC 9126 quality attributes for thousands of revisions of an industrial and three open-source software systems. We also collected the cardinality of each version control operation type for every investigated revision. Based on these data, we identied that operation Add has a rather positive, while operation Update has a rather negative eect on the quality. On the other hand, for operation Delete we could not nd a clear connection to quality change.

Without the software development and software product knowledge it's very complicated to understand, keep away from improvement in the quality of software. There should be some dimension process to forecast the software development, and to appraise software products and its quality. In This paper provides a brief view on Software Metrics, Software Quality and Software Metrics techniques that will forecast and evaluate the specified superiority factors of software which will relate to quality. It additional discusses regarding the Quality as given through the principles like ISO, principal elements necessary for the Software Metrics and Software Quality as the measurement method to forecast the Quality in the Software. Java source code evolution are using for Software Metrics, like Defect Metrics, Size Metrics, and Complexity Metrics. Presented experiments are proving that, the software quality can be analyzed, observed, and enhanced through software metrics usage.

Acta Cybernetica, 2015

Software maintenance consumes huge efforts. Its cost strongly depends on the quality of the source code: an easy-to-maintain code needs much less effort than the maintenance of a more problematic one. Based on experiences, the maintainability of the source code tends to decrease during its lifetime. However, in most of the cases, this decrease is not a smooth linear one, but there are larger and smaller ups and downs, and the net root of these changes generally results in a negative tendency. Detecting common development patterns which similarly influence the maintainability could help to stop or even turn back source code erosion. In this research the scale of the ups and downs are investigated, namely that which version control operations cause bigger and which smaller changes in the maintainability. We calculated the maintainability and collected the cardinality of each version control operation for every revision of four inspected software systems. With the help of these data we checked which version control operation causes higher absolute code quality changes and which lower. We found clear connection between version control operations and the variance of the maintainability changes. File Additions and file Deletions caused significantly higher variance in maintainability changes compared to file Updates. Commits containing higher number of operations-regardless of the type of the operation-caused higher variance in maintainability changes than those commits containing lower number of operations. As a practical conclusion, it is recommended to pay special attention to the quality of commits containing new file additions, e.g. with the help of a mandatory code review.

Information Systems …, 2002

2017

Nowadays, developers tend to adopt a component-based software engineering approach, reusing own implementations and/or resorting to third-party source code. This practice is in principle cost-effective, however it may also lead to low quality software products, if the components to be reused exhibit low quality. Thus, several approaches have been developed to measure the quality of software components. Most of them, however, rely on the aid of experts for defining target quality scores and deriving metric thresholds, leading to results that are context-dependent and subjective. In this work, we build a mechanism that employs static analysis metrics extracted from GitHub projects and defines a target quality score based on repositories’ stars and forks, which indicate their adoption/acceptance by developers. Upon removing outliers with a one-class classifier, we employ Principal Feature Analysis and examine the semantics among metrics to provide an analysis on five axes for source co...

Proceedings of the 11th Panhellenic Conference on Informatics, 2007

The open source software ecosystem comprises more than a hundred thousand applications of varying quality. Individuals and organizations wishing to use open source software packages have scarce objective data to evaluate their quality. However, open source development projects by definition allow anybody to read, and therefore evaluate their source code. In addition, most projects also publish process-related artefacts, such as bug databases, mailing lists, and configuration management system logs. The software ...