An Empirical Study of Factors and their Relationships in Outsourced Software Maintenance

2006 ◽  
Author(s):  
Pankaj Bhatt ◽  
Gautam Shroff ◽  
Williams K. ◽  
Arun K. Misra
Keyword(s):  
Empirical Study ◽  
Software Maintenance

Comparing Software Bugs in Clone and Non-clone Code: An Empirical Study

2017 ◽  
Vol 27 (09n10) ◽  
pp. 1507-1527
Author(s):  
Judith F. Islam ◽  
Manishankar Mondal ◽  
Chanchal K. Roy ◽  
Kevin A. Schneider
Keyword(s):  
High Risk ◽  
Empirical Study ◽  
Software Development ◽  
Comparative Study ◽  
Software Maintenance ◽  
Statistical Significance ◽  
Ongoing Debate ◽  
Software Bugs ◽  
Bug Fixing

Code cloning is a recurrent operation in everyday software development. Whether it is a good or bad practice is an ongoing debate among researchers and developers for the last few decades. In this paper, we conduct a comparative study on bug-proneness in clone code and non-clone code by analyzing commit logs. According to our inspection of thousands of revisions of seven diverse subject systems, the percentage of changed files due to bug-fix commits is significantly higher in clone code compared with non-clone code. We perform a Mann–Whitney–Wilcoxon (MWW) test to show the statistical significance of our findings. In addition, the possibility of occurrence of severe bugs is higher in clone code than in non-clone code. Bug-fixing changes affecting clone code should be considered more carefully. Finally, our manual investigation shows that clone code containing if-condition and if–else blocks has a high risk of having severing bugs. Changes to such types of clone fragments should be done carefully during software maintenance. According to our findings, clone code appears to be more bug-prone than non-clone code.

scholarly journals An Empirical Study of the Impacts of Clones in Software Maintenance

2011 ◽  
Author(s):  
Manishankar Mondal ◽  
Md. Saidur Rahman ◽  
Ripon K. Saha ◽  
Chanchal K. Roy ◽  
Jens Krinke ◽  
...  
Keyword(s):  
Empirical Study ◽  
Software Maintenance

Supporting Requirements to Code Traceability Creation by Code Comments

2021 ◽  
Vol 31 (08) ◽  
pp. 1099-1118
Author(s):  
Guohua Shen ◽  
Haijuan Wang ◽  
Zhiqiu Huang ◽  
YaoShen Yu ◽  
Kai Chen
Keyword(s):  
Empirical Study ◽  
Software Maintenance ◽  
Source Code ◽  
The Other ◽  
Different Types ◽  
The Creation ◽  
The Impact ◽  
Code Tracing

Requirements-to-code tracing is an important and costly task that creates trace links from requirements to source code. These trace links help engineers reduce the time and complexity of software maintenance. Code comments play an important role in software maintenance tasks. However, few studies have focused intensively on the impact of code comments on requirements-to-code trace links creation. Different types of comments have different purposes, so how different types of code comments provide different improvements for requirements-to-code trace links creation? We focus on learning whether code comments and different types of comments can improve the quality of trace links creation. This paper presents a study to evaluate the contribution of code comments and different types of code comments to the creation of trace links. More specifically, this paper first experimentally evaluates the impact of code comments on requirements-to-code trace links creation, and then divides code comments into six categories to evaluate its impact on trace links creation. The results show that the precision increases by an average of 15% (based on the same recall) after adding code comments (even for different trace links creation techniques), and the type of Purpose comments contributes more to the tracing task than the other five. This empirical study provides evidence that code comments are effective in tracing links creation, and different types of code comments contribute differently. Purpose comments can be used to improve the accuracy of requirements-to-code trace links creation.

Guiding Bug Triage through Developer Analysis in Bug Reports

2016 ◽  
Vol 26 (03) ◽  
pp. 405-431 ◽  
Author(s):  
Tao Zhang ◽  
Geunseok Yang ◽  
Byungjeong Lee ◽  
Alvin T. S. Chan
Keyword(s):  
Empirical Study ◽  
Software Maintenance ◽  
Large Scale ◽  
Software Projects ◽  
Bug Reports ◽  
Bug Fixing ◽  
Bug Report ◽  
Report Analysis ◽  
Mozilla Firefox ◽  
Triage Algorithm

An important part of software maintenance is bug report analysis during bug-fixing, especially for large-scale software projects. Since bugs reported to the bug repository need to be fixed, triagers are responsible to identify appropriate developers to execute the fix. Previous research focused on optimizing this process, such as by duplicate detection and use of developer recommendations for reducing the workload of triagers. However, there were scant studies that analyzed developer roles (e.g. reporter and assignee) in the bug-fixing process. Therefore, in this paper, we perform an in-depth empirical study of the different roles that developers perform in bug resolution. By extracting the factors that affect bug resolution from the analysis results, we propose a novel bug triage algorithm to recommend the appropriate developers to fix a given bug. We implement the proposed recommendations on the Eclipse and Mozilla Firefox projects, with the results showing that the new bug triage algorithm can effectively recommend which experts should fix given bugs.

Sign in / Sign up

Export Citation Format

Share Document