Comparative Assessment of Software Quality Classification Techniques: An Empirical Case Study

2004 ◽  
Vol 9 (3) ◽  
pp. 229-257 ◽  
Author(s):  
Taghi M. Khoshgoftaar ◽  
Naeem Seliya
Keyword(s):  
Software Quality ◽  
Comparative Assessment ◽  
Classification Techniques ◽  
Quality Classification

A RULE-BASED SOFTWARE QUALITY CLASSIFICATION MODEL

2008 ◽  
Vol 15 (03) ◽  
pp. 247-259
Author(s):  
TAGHI M. KHOSHGOFTAAR ◽  
LOFTON A. BULLARD ◽  
KEHAN GAO
Keyword(s):  
Software Quality ◽  
Rough Set Theory ◽  
Classification Model ◽  
Equal Frequency ◽  
Rule Based ◽  
Functional Aspects ◽  
Quality Classification ◽  
Proposed Model ◽  
Software Modules

A rule-based classification model is presented to identify high-risk software modules. It utilizes the power of rough set theory to reduce the number of attributes, and the equal frequency binning algorithm to partition the values of the attributes. As a result, a set of conjuncted Boolean predicates are formed. The model is inherently influenced by the practical needs of the system being modeled, thus allowing the analyst to determine which rules are to be used for classifying the fault-prone and not fault-prone modules. The proposed model also enables the analyst to control the number of rules that constitute the model. Empirical validation of the model is accomplished through a case study of a large legacy telecommunications system. The ease of rule interpretation and the transparency of the functional aspects of the model are clearly demonstrated. It is concluded that the new model is effective in achieving the software quality classification.

scholarly journals The Relation of Test-Related Factors to Software Quality: A Case Study on Apache Systems

2021 ◽  
Vol 26 (2) ◽  
Author(s):  
Fabiano Pecorelli ◽  
Fabio Palomba ◽  
Andrea De Lucia
Keyword(s):  
Software Quality ◽  
Compelling Evidence ◽  
Related Factors ◽  
Code Coverage ◽  
Production Code ◽  
Software Code ◽  
Class Test ◽  
Code Quality ◽  
Lack Of Knowledge

AbstractTesting represents a crucial activity to ensure software quality. Recent studies have shown that test-related factors (e.g., code coverage) can be reliable predictors of software code quality, as measured by post-release defects. While these studies provided initial compelling evidence on the relation between tests and post-release defects, they considered different test-related factors separately: as a consequence, there is still a lack of knowledge of whether these factors are still good predictors when considering all together. In this paper, we propose a comprehensive case study on how test-related factors relate to production code quality in Apache systems. We first investigated how the presence of tests relates to post-release defects; then, we analyzed the role played by the test-related factors previously shown as significantly related to post-release defects. The key findings of the study show that, when controlling for other metrics (e.g., size of the production class), test-related factors have a limited connection to post-release defects.

AN EMPIRICAL STUDY OF SOFTWARE METRICS FOR ASSESSING THE PHASES OF AN AGILE PROJECT

2012 ◽  
Vol 22 (04) ◽  
pp. 525-548 ◽  
Author(s):  
GIULIO CONCAS ◽  
MICHELE MARCHESI ◽  
GIUSEPPE DESTEFANIS ◽  
ROBERTO TONELLI
Keyword(s):  
Software Quality ◽  
Web Application ◽  
Software Metrics ◽  
Pair Programming ◽  
Application Development ◽  
Agile Practices ◽  
Code Metrics ◽  
Agile Process ◽  
Adoption Level

We present an analysis of the evolution of a Web application project developed with object-oriented technology and an agile process. During the development we systematically performed measurements on the source code, using software metrics that have been proved to be correlated with software quality, such as the Chidamber and Kemerer suite and Lines of Code metrics. We also computed metrics derived from the class dependency graph, including metrics derived from Social Network Analysis. The application development evolved through phases, characterized by a different level of adoption of some key agile practices — namely pair programming, test-based development and refactoring. The evolution of the metrics of the system, and their behavior related to the agile practices adoption level, is presented and discussed. We show that, in the reported case study, a few metrics are enough to characterize with high significance the various phases of the project. Consequently, software quality, as measured using these metrics, seems directly related to agile practices adoption.

Trusting Computers Through Trusting Humans

2008 ◽  
pp. 3460-3474
Author(s):  
Alison Adam ◽  
Paul Spedding
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Computer System ◽  
Software Quality ◽  
Software Verification ◽  
Mathematical Proof ◽  
Quality Standards ◽  
Software Quality Assurance ◽  
The Social

This article considers the question of how we may trust automatically generated program code. The code walkthroughs and inspections of software engineering mimic the ways that mathematicians go about assuring themselves that a mathematical proof is true. Mathematicians have difficulty accepting a computer generated proof because they cannot go through the social processes of trusting its construction. Similarly, those involved in accepting a proof of a computer system or computer generated code cannot go through their traditional processes of trust. The process of software verification is bound up in software quality assurance procedures, which are themselves subject to commercial pressures. Quality standards, including military standards, have procedures for human trust designed into them. An action research case study of an avionics system within a military aircraft company illustrates these points, where the software quality assurance (SQA) procedures were incommensurable with the use of automatically generated code.

Sign in / Sign up

Export Citation Format

Share Document