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.

scholarly journals Analysis on Relationship between Code Quality and Code Coverage in an XP Environment: A Case Study on the SWURV Project

2021 ◽  
Author(s):  
Hua Li
Keyword(s):  
Defect Density ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Code Coverage ◽  
Software Products ◽  
Root Cause ◽  
Residual Defect ◽  
Software Product ◽  
Code Quality

The thesis used hypothesis testing and correlation analysis methods to explore the relationship between structural code coverage and the quality of software developed in an eXtreme Programming (XP) environment, via a case study of a commercial software product. We find that improving code coverage is helpful to detect residual defects, but it is not enough, and we also need other testing, like acceptance testing, in the process of XP software development to provide good quality software products. In addition, in order to investigate why the strength of association between code coverage and residual defect density is not as strong as that presented in prior work, a detailed defect root cause analysis is performed, showing that over 96% of bugs cannot be detected by improving code coverage. Based on the defect categories and distribution of defect root cause, six improvement actions are proposed for future XP projects.

scholarly journals Developing A Code Readability Model To Improve Software Quality

2012 ◽  
pp. 206-210
Author(s):  
Venkatesh Podugu
Keyword(s):  
Graphical User Interface ◽  
Software Quality ◽  
Software Maintenance ◽  
Software Metrics ◽  
Software Defect ◽  
Code Changes ◽  
Software Code ◽  
The Many ◽  
Code Quality

Software maintenance is one of the main phase in software evaluation. This paper presents the relation between software metrics and maintainability. This paper explains about the concept of Software code readability and its relation to software quality. The quality of code is very essential for the future and for the reuse purpose. Here generated a code readability model to calculate the readability of the code by selecting the snippets and these snippets are to be given to the expert to rate them. Collecting the features of code and combing the judgments generated the readability model. This paper focus on providing the graphical user interface (GUI),to the code readability model to improve the understanding of software code readability. By providing the readability of code to the many open source projects, automatically informing the existed code quality to improve the quality of code. It show that this readability model developed is correlates strongly with three measures of software quality: code changes in software, defect log messages and automated defect reports. It measures correlations over many releases of selected projects.

scholarly journals Analysis on Relationship between Code Quality and Code Coverage in an XP Environment: A Case Study on the SWURV Project

2021 ◽  
Author(s):  
Hua Li
Keyword(s):  
Defect Density ◽  
Extreme Programming ◽  
Acceptance Testing ◽  
Code Coverage ◽  
Software Products ◽  
Root Cause ◽  
Residual Defect ◽  
Software Product ◽  
Code Quality

The thesis used hypothesis testing and correlation analysis methods to explore the relationship between structural code coverage and the quality of software developed in an eXtreme Programming (XP) environment, via a case study of a commercial software product. We find that improving code coverage is helpful to detect residual defects, but it is not enough, and we also need other testing, like acceptance testing, in the process of XP software development to provide good quality software products. In addition, in order to investigate why the strength of association between code coverage and residual defect density is not as strong as that presented in prior work, a detailed defect root cause analysis is performed, showing that over 96% of bugs cannot be detected by improving code coverage. Based on the defect categories and distribution of defect root cause, six improvement actions are proposed for future XP projects.

Hodgkin Disease and Pregnancy - A Case Report

2014 ◽  
Vol 68 (2) ◽  
pp. 104-106
Author(s):  
Aleksandra Pivkova Veljanovska ◽  
Sonja Genadieva Stavrik ◽  
Zlate Stojanoski ◽  
Lazar Cadievski ◽  
Adela Stefanija ◽  
...  
Keyword(s):  
Case Report ◽  
Pregnant Women ◽  
Hodgkin Disease ◽  
Morbidity And Mortality ◽  
Chemotherapy Treatment ◽  
Related Factors ◽  
Hematological Disorder

Abstract The article presents a case with diagnosed Hodgkin disease (HD) during pregnancy. The aim of this case study was to present diagnostic possibilities in determining HD stage during pregnancy and therapeutic dilemmas. The incidence of HD during pregnancy is 3.2% of all cases with this malignant hematological disorder. The treatment of this disease during pregnancy depends on disease-related factors, pregnancy-related factors, as well as possible implications for fetal morbidity and mortality. The need of analysis of the nature of the disease during pregnancy indicates examination of a larger series of pregnant women with HD and the drawn conclusions affect the decision whether chemotherapy treatment should start immediately or it should be postponed for after delivery.

Implementation of a positive youth development program by class teachers in a Chinese context

2012 ◽  
Vol 24 (3) ◽  
pp. 273-280
Author(s):  
Daniel T.L. Shek ◽  
Daniel W.M. Lung ◽  
Yammy L.Y. Chak
Keyword(s):  
Youth Development ◽  
Positive Youth Development ◽  
Program Implementation ◽  
Development Program ◽  
Related Factors ◽  
Chinese Context ◽  
Youth Development Program ◽  
The People ◽  
Study Results

Abstract This paper reports the findings of a case study in which a curriculum-based positive youth development program (Project P.A.T.H.S.) was implemented by the class teachers in a school. School-related factors which contributed to the success of program implementation were identified in the study. Results showed that factors facilitating the program implementation were closely related to the “5Ps” model (i.e., program, people, process, policy and place). While all the above factors contributed to the success of program implementation, the “people” factor was identified as the most crucial factor. Overall, both the students and program implementers perceived the program to be effective in promoting holistic development in the program participants.

Why Do Developers Reject Refactorings in Open-Source Projects?

2022 ◽  
Vol 31 (2) ◽  
pp. 1-23
Author(s):  
Jevgenija Pantiuchina ◽  
Bin Lin ◽  
Fiorella Zampetti ◽  
Massimiliano Di Penta ◽  
Michele Lanza ◽  
...  
Keyword(s):  
Open Source ◽  
Software Quality ◽  
Good Practice ◽  
Source Code ◽  
Code Review ◽  
Code Quality ◽  
Shed Light

Refactoring operations are behavior-preserving changes aimed at improving source code quality. While refactoring is largely considered a good practice, refactoring proposals in pull requests are often rejected after the code review. Understanding the reasons behind the rejection of refactoring contributions can shed light on how such contributions can be improved, essentially benefiting software quality. This article reports a study in which we manually coded rejection reasons inferred from 330 refactoring-related pull requests from 207 open-source Java projects. We surveyed 267 developers to assess their perceived prevalence of these identified rejection reasons, further complementing the reasons. Our study resulted in a comprehensive taxonomy consisting of 26 refactoring-related rejection reasons and 21 process-related rejection reasons. The taxonomy, accompanied with representative examples and highlighted implications, provides developers with valuable insights on how to ponder and polish their refactoring contributions, and indicates a number of directions researchers can pursue toward better refactoring recommenders.

scholarly journals A social work study on detecting organizational and job related factors creating stress: A case study of hydro power employees

2012 ◽  
Vol 2 (4) ◽  
pp. 1447-1454 ◽  
Author(s):  
Gholamali Iravani ◽  
Akbar Iravani ◽  
Ebrahim Jafari ◽  
Samaneh Salimi ◽  
Mohammad Reza Iravani
Keyword(s):  
Social Work ◽  
Work Study ◽  
Related Factors ◽  
Hydro Power

Toward a Model of Brand Creation for International Large-Scale Sporting Events: The Impact of Leadership, Context, and Nature of the Event

2008 ◽  
Vol 22 (5) ◽  
pp. 526-549 ◽  
Author(s):  
Milena M. Parent ◽  
Benoit Séguin
Keyword(s):  
Large Scale ◽  
Sporting Events ◽  
Related Factors ◽  
Initial Event ◽  
Leadership Group ◽  
Leadership Context ◽  
The Impact ◽  
Communication Paths ◽  
Brand Creation

The purpose of this study was to develop a model of brand creation for one-off large-scale sporting events. A case study of the 2005 Montreal FINA (Fédération Internationale de Natation) World Championships highlighted the importance of the leadership group (which must include individuals with political/networking, business/management, and sport/event skills), the context, and the nature of the event for creating the event’s brand. The importance of each aspect is suggested to vary depending on the situation. For example, the lack of an initial event brand will result in the leadership group having the greatest impact on the event’s brand creation process. Findings also highlighted differing communication paths for internal and external stakeholders. Thus, this study contributes to the literature by focusing on brand creation and its related factors instead of the management and outcomes of a brand.

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.

Sign in / Sign up

Export Citation Format

Share Document