scholarly journals Mining Severe Priority Bugs in Software Maintenance

2019 ◽  
Vol 8 (4S2) ◽  
pp. 729-732
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Maintenance ◽  
Maintenance Phase ◽  
Bug Reports ◽  
Bug Tracking ◽  
The Right ◽  
Software Bug ◽  
Positive Results

Maintenance of open source software is a hectic task as the number of bugs reported is huge. The number of projects, components and versions in an open source project also contribute to the number of bugs that are being reported. Classification of bugs based on priority and identification of the suitable engineers for assignment of bugs for such huge systems still remains a major challenge. Bugs that are misclassified or assigned to engineers who don’t have the component expertise, drastically affect the time taken towards bug resolution. In this paper we have explored the usage of data mining techniques on the classification of bugs and assignment of bugs to engineers.Our focus was on classifying bugs as either severe or non-severe and identification of engineers who have the right expertise to fix the bugs. The prediction of bug severity and identification of engineers were done by mining bug reports from JIRA, an open source software bug tracking tool. The mining process yielded positive results and will be a decision enhancer for severe bugs in the maintenance phase

scholarly journals MULTI-FEATURE MODEL FOR DUPLICATE BUG REPORTS DETECTION SOLUTION

2019 ◽  
Vol 1 (1) ◽  
pp. 29-36
Author(s):  
Phuc Minh Nhan ◽  
Thien Hoang Duy Nguyen
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Maintenance ◽  
Feature Model ◽  
Software Bugs ◽  
Bug Reports ◽  
Duplicate Bug Reports ◽  
Error Reports ◽  
Bug Management

For open source software such as Firefox, Eclipse, Subversion,. . . they usually have a system for bug management that sent by users. These bug reports help the system identify various software bugs which makes software maintenance better. However, a situation occurs that there are many error reports sent to  the processing repository that these bug reports were previously reported by different users, this is called duplicate bug reports. In this paper, we introduce a multi-feature model combined with weighted improvements from CFC (ClassFeature-Centroid) to detect duplicate bug reportsautomatically. We have experimented on three projects of Mozilla, Eclipse and OpenOffice. The results show that our method can improve 8-12% better as compared to the compared methods.

Automated classification of self-grooming in mice using open-source software

2017 ◽  
Vol 289 ◽  
pp. 48-56 ◽  
Author(s):  
Bastijn J.G. van den Boom ◽  
Pavlina Pavlidi ◽  
Casper J.H. Wolf ◽  
Adriana H. Mooij ◽  
Ingo Willuhn
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Automated Classification

Enterprise Resource Planning Under Open Source Software

2010 ◽  
pp. 1571-1589
Author(s):  
Ashley Davis
Keyword(s):  
Real Options ◽  
Open Source ◽  
Open Source Software ◽  
Enterprise Resource Planning ◽  
Resource Planning ◽  
Future Trends ◽  
Critical Factors ◽  
Real Options Theory ◽  
The Right ◽  
Options Theory

Open source software is becoming more prevalent in businesses today, and while still a relatively immature offering, open source enterprise resource planning (OS-ERP) systems are becoming more common. However, whether or not an OS-ERP package is the right software for a given organization is a little researched question. Building on the current real options thinking about platform acquisitions, this chapter proposes the five most critical factors to consider when evaluating an OS-ERP package. To adequately do this, a great deal of detail about the current offerings in OS-ERP software is presented, followed by a review of the real options theory and thinking behind using these factors to evaluate OS-ERP options. The international implications of OS-ERP are presented in the “Future Trends” section.

Social Network Structures in Open Source Software Development Teams

2009 ◽  
pp. 645-658
Author(s):  
Yuan Long ◽  
Keng Siau
Keyword(s):  
Social Network ◽  
Open Source ◽  
Open Source Software ◽  
Interaction Pattern ◽  
Network Structures ◽  
Monthly Data ◽  
Development Teams ◽  
Longitudinal View ◽  
Software Development Teams ◽  
Bug Tracking

Drawing on social network theories and previous studies, this research examines the dynamics of social network structures in open source software (OSS) teams. Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure. The finding suggests that the interaction pattern of OSS projects evolves from a single hub at the beginning to a core/periphery model as the projects move forward.

Adaptive Ranking Relevant Source Files for Bug Reports Using Genetic Algorithm

2021 ◽  
Author(s):  
Thi Mai Anh Bui ◽  
Nhat Hai Nguyen
Keyword(s):  
Genetic Algorithm ◽  
Software Maintenance ◽  
Large Scale ◽  
Maintenance Phase ◽  
Bug Localization ◽  
Software Projects ◽  
Source File ◽  
Bug Reports ◽  
Localization Model ◽  
Bug Report

Precisely locating buggy files for a given bug report is a cumbersome and time-consuming task, particularly in a large-scale project with thousands of source files and bug reports. An efficient bug localization module is desirable to improve the productivity of the software maintenance phase. Many previous approaches rank source files according to their relevance to a given bug report based on simple lexical matching scores. However, the lexical mismatches between natural language expressions used to describe bug reports and technical terms of software source code might reduce the bug localization system’s accuracy. Incorporating domain knowledge through some features such as the semantic similarity, the fixing frequency of a source file, the code change history and similar bug reports is crucial to efficiently locating buggy files. In this paper, we propose a bug localization model, BugLocGA that leverages both lexical and semantic information as well as explores the relation between a bug report and a source file through some domain features. Given a bug report, we calculate the ranking score with every source files through a weighted sum of all features, where the weights are trained through a genetic algorithm with the aim of maximizing the performance of the bug localization model using two evaluation metrics: mean reciprocal rank (MRR) and mean average precision (MAP). The empirical results conducted on some widely-used open source software projects have showed that our model outperformed some state of the art approaches by effectively recommending relevant files where the bug should be fixed.

From Android Bug Reports to Android Bug Handling Process

2016 ◽  
Vol 7 (4) ◽  
pp. 1-18
Author(s):  
Liguo Yu
Keyword(s):  
Project Management ◽  
Open Source ◽  
Tracking System ◽  
Software Project ◽  
Bug Reports ◽  
Bug Report ◽  
Bug Tracking ◽  
Android Development ◽  
Comprehensive Study

Android is an operating system for mobile devices. Its development is led by Google and some other companies. Because of the open-source property of Android, anyone can report a bug through its online bug tracking system. In this paper, we analyze the bug reports of Android operating systems. Specifically, through this study, we would like to answer the following questions regarding Android development and its project management: (1) Could Android bug reports be handled on time? (2) What is the distribution of different maintenance activities initiated by Android bug reports? (3) How long does it take to handle an Android bug report? (4) Are the number of followers and the number of following messages of an Android bug report related to the effort spent on handling this bug report? Through answering these questions, this paper presents a comprehensive study of Android bug reporting and handling process. The information and knowledge obtained through this case study could help us better understand open-source software project, such as its development process and project management.

How the FLOSS Research Community Uses Email Archives

2012 ◽  
Vol 4 (1) ◽  
pp. 37-59 ◽  
Author(s):  
Megan Squire
Keyword(s):  
Software Engineering ◽  
Open Source ◽  
Open Source Software ◽  
Development Process ◽  
Relevant Literature ◽  
Research Community ◽  
Email Message ◽  
Object Of Study ◽  
Broad Overview

Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work.

A Commit Messages-Based Bug Localization for Android Applications

2019 ◽  
Vol 29 (04) ◽  
pp. 457-487 ◽  
Author(s):  
Tao Zhang ◽  
Wenjun Hu ◽  
Xiapu Luo ◽  
Xiaobo Ma
Keyword(s):  
Open Source ◽  
Software Maintenance ◽  
State Of The Art ◽  
Bug Localization ◽  
Two Phase ◽  
Android Apps ◽  
Bug Reports ◽  
Android Applications ◽  
The Given ◽  
General Method

Recently, there has been consistent growth in Android applications (apps). Under these circumstances, software maintenance for Android apps becomes an essential and important task. The core of software maintenance is to locate bugs in source files. Previous bug localization approaches mainly focus on open-source desktop software (e.g. Eclipse, Mozilla, GCC). Even though a few studies locate the bugs in the Android apps, they are dedicated to a special app named ZXing, without developing a general method to locate the bugs in Android apps by taking into account the unique characteristics of Android apps’ bug reports. Such characteristics include fewer number of historical bug reports, insufficient detailed description, etc. These characteristics hinder existing localization approaches from being directly delivered to Android apps, because lack of enough information degrades the performance of those localization approaches relying on historical bug reports. Commit messages include more informative data which can provide the details of reported bugs. Therefore, in this paper, we propose a novel information retrieval-based approach which utilizes commit messages to locate new bugs in Android apps. This approach not only considers the structured textual similarity between the given bug and the candidate source files, but also computes the unstructured textual similarities between the new bug and the commit messages linked to the corresponding source files. According to the experimental results on 10 popular open-source Android apps managed by GitHub, our approach outperforms the state-of-the-art bug localization methods that include BugLocator, BLUiR, and two-phase model.

A Method of Statistical Process Control for Successful Open Source Software Projects and Its Application to Determining the Development Period

2016 ◽  
Vol 23 (05) ◽  
pp. 1650018 ◽  
Author(s):  
Shigeru Yamada ◽  
Masakazu Yamaguchi
Keyword(s):  
Process Control ◽  
Open Source ◽  
Statistical Process Control ◽  
Open Source Software ◽  
Execution Time ◽  
Tracking System ◽  
Time Model ◽  
Statistical Process ◽  
Software Release ◽  
Bug Tracking

A software development paradigm for open source software (OSS) project has been rapidly spread in recent years. On the other hand, an effective method of quality management has not been established due to the unique development characteristics such as no testing phase. In this paper, we assume that the number of fault-detections observed on the bug tracking system tends to infinity, and discuss a method of statistical process control (SPC) for OSS projects by applying the logarithmic Poisson execution time model as a software reliability growth model (SRGM) based on a nonhomogeneous Poisson process (NHPP). Then, we propose a control chart method based on the logarithmic Poisson execution time model for judging the statical stability state, and estimating the additional development time for attaining the objective software failure intensity, i.e., the target value of the instantaneous fault-detection rate per unit time. We also discuss an optimal software release problem for determining the optimum time when to stop OSS development and to transfer it to user operation. Further, numerical illustrations for SPC are shown by applying the actual fault-count data observed on the bug tracking system.

Sign in / Sign up

Export Citation Format

Share Document