Are Developers Fixing Their Own Bugs?

2013 ◽  
pp. 79-98
Author(s):  
Daniel Izquierdo-Cortazar ◽  
Andrea Capiluppi ◽  
Jesus M.. Gonzalez-Barahona
Keyword(s):  
Management System ◽  
Source Code ◽  
The Other ◽  
Software Project ◽  
Software Bugs ◽  
Bug Fixing ◽  
Maintenance Activities

The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.

scholarly journals Are Developers Fixing Their Own Bugs?

2011 ◽  
Vol 3 (2) ◽  
pp. 23-42 ◽  
Author(s):  
Daniel Izquierdo-Cortazar ◽  
Andrea Capiluppi ◽  
Jesus M.. Gonzalez-Barahona
Keyword(s):  
Management System ◽  
Source Code ◽  
The Other ◽  
Software Project ◽  
Software Bugs ◽  
Bug Fixing ◽  
Maintenance Activities

The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.

La gestion forestière écosystémique multifonctionnelle et son importance pour la biodiversité (essai) | Multifunctional forest ecosystem management and its importance for biodiversity (essay)

2010 ◽  
Vol 161 (8) ◽  
pp. 311-315
Author(s):  
Jean-Philippe Schütz ◽  
Brice de Turckheim
Keyword(s):  
Ecosystem Management ◽  
Basic Principle ◽  
Forest Ecosystem ◽  
Sustainable Management ◽  
Management System ◽  
The Other ◽  
Carbon Management ◽  
Gestion Forestière ◽  
Forest Ecosystem Management

The basic principle of Pro Silva silviculture is to be multifunctional and to seek to combine into a harmonious whole all the benefits provided by the forest. It is thus a management system constantly adapted to follow the evolution of different needs and requirements. On the occasion of the International Year of Biodiversity, it is here explained why this form of management meets in an optimal manner the interests of biodiversity without however pushing into the background the other functions, in particular carbon management. Intrinsically it corresponds to the principles of sustainable management, maintaining the balance between economic, social and ecological interests.

Design and Evaluation of Usable Systems

2002 ◽  
Vol 46 (3) ◽  
pp. 367-371
Author(s):  
John F. McGrew
Keyword(s):  
Genetic Algorithm ◽  
Change Management ◽  
Management System ◽  
Design Method ◽  
The Other ◽  
Design Team ◽  
Style Analysis ◽  
Decision Style ◽  
Parallel Design

This paper discusses a case study of a design and evaluation of a change management system at a large Telecommunications Corporation. The design and evaluation were done using the facilitated genetic algorithm (a parallel design method) and user decision style analysis. During the facilitated genetic algorithm the design team followed the procedure of the genetic algorithm. Usability was evaluated by applying user decision style analysis to the designed system. The design is compared with an existing system and with one designed by an analyst. The change management system designed by the facilitated genetic algorithm took less time to design and decision style analysis indicated it would be easier to use than the other two systems.

Mining Bug Report Repositories to Identify Significant Information for Software Bug Fixing

2021 ◽  
Author(s):  
Bancha Luaphol ◽  
Jantima Polpinij ◽  
Manasawee Kaenampornpan
Keyword(s):  
The Other ◽  
Problem Domain ◽  
Significant Information ◽  
Bug Reports ◽  
Bug Fixing ◽  
Classification Technique ◽  
Bug Report ◽  
Multiple Issues ◽  
Improved Accuracy ◽  
Software Bug

Most studies relating to bug reports aims to automatically identify necessary information from bug reports for software bug fixing. Unfortunately, the study of bug reports focuses only on one issue, but more complete and comprehensive software bug fixing would be facilitated by assessing multiple issues concurrently. This becomes a challenge in this study, where it aims to present a method of identifying bug reports at severe level from a bug report repository, together with assembling their related bug reports to visualize the overall picture of a software problem domain. The proposed method is called “mining bug report repositories”. Two techniques of text mining are applied as the main mechanisms in this method. First, classification is applied for identifying severe bug reports, called “bug severity classification”, while “threshold-based similarity analysis” is then applied to assemble bug reports that are related to a bug report at severe level. Our datasets are from three opensource namely SeaMonkey, Firefox, and Core:Layout downloaded from the Bugzilla. Finally, the best models from the proposed method are selected and compared with two baseline methods. For identifying severe bug reports using classification technique, the results show that our method improved accuracy, F1, and AUC scores over the baseline by 11.39, 11.63, and 19% respectively. Meanwhile, for assembling related bug reports using threshold-based similarity technique, the results show that our method improved precision, and likelihood scores over the other baseline by 15.76, and 9.14% respectively. This demonstrate that our proposed method may help increasing chance to fix bugs completely.

scholarly journals Conceptual model of the ferry que management system in ferry ports in the Republic of Croatia

Pomorstvo ◽  
2020 ◽  
Vol 34 (2) ◽  
pp. 354-362
Author(s):  
Dino Županović ◽  
Luka Grbić ◽  
Marijan Cukrov
Keyword(s):  
Information Technology ◽  
Conceptual Model ◽  
Management System ◽  
Supply And Demand ◽  
The Other ◽  
Border Crossings ◽  
Local Approach ◽  
Traffic Demand ◽  
Macroscopic Level ◽  
The Republic

This paper proposes a model for optimizing the ferry traffic and the traffic demand at the macroscopic level by using information technology (IT) and the existing tourist amenities as a key element for achieving harmonization of supply and demand, i.e. optimization of the assessed system. Proposed approach differs from the other/present models because it includes the application of the macroscopic, instead of the microscopic (local) approach, i.e. harmonization of the ferry infrastructure demand from the place of its origin (road border crossings) to the place of its operation, i.e. the ferry infrastructure, and not solely in particular segments of the ferry infrastructure.

scholarly journals Crossbred Local Chickens from East Nusa Tenggara Province Indonesia Under Semi Intensive Management System

2021 ◽  
Vol 748 (1) ◽  
pp. 012003
Author(s):  
N.G.A Mulyantini S.S ◽  
Ulrikus R Lole
Keyword(s):  
Weight Gain ◽  
Artificial Insemination ◽  
Management System ◽  
Egg Production ◽  
Abdominal Fat ◽  
Production Performance ◽  
The Other ◽  
Intensive Management ◽  
Commercial Grower ◽  
Local Chickens

Abstract The objective of this study was to compare the performance of four-breed combination under semiintensive management system. The experiment used 160 females and 40 males chickens as parents. Artificial insemination was performed to produce the experimental chicken of the four breed combinations (1. Sabu x Sabu, 2. Sabu x Semau, 3. Sabu x KUB, 4. Semau x KUB). The chickens were fed with chick starter crumb sad libitum from day old to 4 weeks of age. From 4-8 weeks of age, chickens were allowed to scavenge during the day, and also given commercial grower pellets + rice bran + corn (5:4:1). Combination of Sabu x KUBfrom 4-8 weeks of age were significantly heavier (P < 0.05) than the other combination breeds. Feed intake in the Sabu x KUB group was the lowest, and their weight gain was the highest among the others group(P < 0.05). The combination Sabu x KUB also had the highest egg production, and hatchability. However, the percentage of abdominal fat of Sabu x KUB were higher than others groups. In conclusion, combination Sabu x KUB had the best growth performance and egg production performance, but not for the percentage of abdominal fat.

Erratum: Fibers of word maps and the multiplicities of non-abelian composition factors

2021 ◽  
Vol 31 (01) ◽  
pp. 201-204
Author(s):  
Alexander Bors
Keyword(s):  
Source Code ◽  
The Other ◽  
Title One ◽  
Composition Factors

We discuss two corrections concerning the paper mentioned in the title. One of them pertains to a slight error in a statement from a different paper that was used. For this statement, it is explained how to fix it and why this does not affect the correctness of our results. The other is concerned with an error in the original GAP source code used to verify some of our results. This error, which was subsequently fixed, did affect the correctness of one of our main theorems, which is now given in corrected (and stronger) form.

Plagiarism Detection Algorithm for Source Code in Computer Science Education

2015 ◽  
Vol 13 (4) ◽  
pp. 29-39 ◽  
Author(s):  
Xin Liu ◽  
Chan Xu ◽  
Boyu Ouyang
Keyword(s):  
Hash Function ◽  
Source Code ◽  
College Education ◽  
Detection Algorithm ◽  
Longest Common Subsequence ◽  
The Other ◽  
Plagiarism Detection ◽  
Detection Algorithms ◽  
Common Subsequence ◽  
Basic Concepts

Nowadays, computer programming is getting more necessary in the course of program design in college education. However, the trick of plagiarizing plus a little modification exists among some students' home works. It's not easy for teachers to judge if there's plagiarizing in source code or not. Traditional detection algorithms cannot fit this condition. The author designed an effective and complete method to detect source code plagiarizing according to the popular way of students' plagiarizing. There are two basic concepts of the algorithm. One is to standardize the source code via filtration against to remove the majority noises intentionally blended by plagiarists. The other one is an improved Longest Common Subsequence algorithm for text matching, using statement as the unit for matching. The authors also designed an appropriate HASH function to increase the efficiency of matching. Based on the algorithm, a system was designed and proved to be practical and sufficient, which runs well and meet the practical requirement in application.

Data in DevOps and Its Importance in Code Analytics

2020 ◽  
pp. 182-208
Author(s):  
Girish Babu ◽  
Charitra Kamalaksh Patil
Keyword(s):  
Software Development ◽  
Management System ◽  
Source Code ◽  
Test Validation ◽  
Test Coverage ◽  
Iterative Processes

Robust DevOps plays a huge role in the health and sanity of software. The metadata generated during DevOps need to be harnessed for deriving useful insights on the health of the software. This area of work can be classified as code analytics and comprises of the following (but not limited to): 1. commit history from the source code management system (SCM); 2. the engineers that worked on the commit; 3. the reviewers on the commit; 4. the extent of build (if applicable) and test validation prior to the commit, the types of failures found in iterative processes, and the fixes done; 5. test extent of test coverage on the commit; 6. any static profiling on the code in the commit; 7. the size and complexity of the commit; 8. many more. This chapter articulates many ways the above information can be used for effective software development.

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.

Sign in / Sign up

Export Citation Format

Share Document