Global ETD Search

Search theses and dissertations gathered from participating repositories worldwide. Every result links back to the library that holds it. No account is needed.

Results

Showing 1 to 20 of 98 for “"bug reports"”.

  1. Assisted detection of duplicate bug reports

    Duplicate bug reports, reports which describe problems or enhancements for which there is already a report in a bug repository, consume time of bug triagers and software developers that might better be spent working on reports that describe unique requests. For many open source projects, the number …

    ubc Repository record for Assisted detection of duplicate bug reports (opens in a new tab) Download PDF for Assisted detection of duplicate bug reports (opens in a new tab)

  2. Detecting planning conversations in bug reports

    Software developers refer to bug reports as a reliable source of information. However, these bug reports are written in the form of conversations among developers and often become long depending on the complexity of the issue, necessitating a significant amount of time and effort to locate the …

    lethbridge Repository record for Detecting planning conversations in bug reports (opens in a new tab)

  3. Detecting inaccurate stack traces in bug reports

    … community is that incorrect information in bug reports is often found in non-structural fields such as bug descriptions and steps to reproduce. However, structural information such as software stack traces can be inaccurate, increasing the project costs due to wasted time in fixed faults. …

    lethbridge Repository record for Detecting inaccurate stack traces in bug reports (opens in a new tab)

  4. R2Fix: Automatically Generating Bug Fixes from Bug Reports

    Many bugs, even those that are known and documented in bug reports, remain in mature software for a long time due to the lack of the development resources to fix them. We propose a general approach, R2Fix, to automatically generate bug-fixing patches from free-form bug reports. R2Fix combines past …

    waterloo Repository record for R2Fix: Automatically Generating Bug Fixes from Bug Reports (opens in a new tab)

  5. Analysis and Interactive Visualization of Software Bug Reports

    A software Bug report contains information about the bug in the form of problem description and comments using natural language texts. Managing reported bugs is a significant challenge for a project manager when the number of bugs for a software project is large. Prior to the assignment of a newly …

    sask Repository record for Analysis and Interactive Visualization of Software Bug Reports (opens in a new tab)

  6. Software bug management from bug reports to bug signatures

    Bugs are prevalent in software systems, and how to effectively manage bugs has been an important activity in the software development life cycle. For example, in software testing and maintenance phases, bug report repositories are used for filing bugs and tracking their status changes; when a bug …

    nus Repository record for Software bug management from bug reports to bug signatures (opens in a new tab) Download file for Software bug management from bug reports to bug signatures (opens in a new tab)

  7. Empirical Analysis and Automated Classification of Security Bug Reports

    … based on the information provided in bug tracking systems and (2) to develop data analytics approaches for automatic classification of bug reports as security or non-security related. This work is based on using three NASA datasets as case studies. The empirical analysis showed that …

    wvu Repository record for Empirical Analysis and Automated Classification of Security Bug Reports (opens in a new tab)

  8. Studying and Leveraging User-Provided Logs in Bug Reports for Debugging Assistance

    Bug reports provide important information for developers to debug user-reported issues. During the debugging process, developers need to study the bug report and examine user-provided logs to understand the system execution paths that lead to the problem. Prior studies on bug reports also found …

    concordia Download PDF for Studying and Leveraging User-Provided Logs in Bug Reports for Debugging Assistance (opens in a new tab)

  9. Leveraging Identifier Naming Structures in Source Code and Bug Reports to Localize Relevant Bugs

    When bugs are found in source code, bug reports are created which contain relevant information for developers to locate and fix the bug. In large source code repositories, it can be difficult and time consuming for developers to manually analyze bug reports to locate a bug. The discovery of …

    rit Repository record for Leveraging Identifier Naming Structures in Source Code and Bug Reports to Localize Relevant Bugs (opens in a new tab)

  10. Machine Learning And Deep Learning Based Approaches For Detecting Duplicate Bug Reports With Stack Traces

    Many large software systems rely on bug tracking systems to record the submitted bug reports and to track and manage bugs. Handling bug reports is known to be a challenging task, especially in software organizations with a large client base, which tend to receive a considerable large number of bug …

    concordia Download PDF for Machine Learning And Deep Learning Based Approaches For Detecting Duplicate Bug Reports With Stack Traces (opens in a new tab)

  11. Learning to Rank Relevant Files for Bug Reports Using Domain knowledge, Replication and Extension of a Learning-to-Rank Approach

    Bug localization is one of the most important stages of the bug fixing process. Bad practices make the debugging a tedious task. Investigating bugs can contribute up to a large portion of the aggregate cost for a software project. An automated strategy that can provide a ranked list of source code …

    rit Repository record for Learning to Rank Relevant Files for Bug Reports Using Domain knowledge, Replication and Extension of a Learning-to-Rank Approach (opens in a new tab)

  12. Bug Triaging with High Confidence Predictions

    Correctly assigning bugs to the right developer or team, i.e., bug triaging, is a costly activity. A concerted effort at Ericsson has been done to adopt automated bug triaging to reduce development costs. We also perform a case study on Eclipse bug reports. In this work, we replicate the research …

    concordia Download PDF for Bug Triaging with High Confidence Predictions (opens in a new tab)

  13. Advancing Bug Report Management: Graph-Based Modeling, Large Language Models, and Quality Improvement

    … development, heavily dependent on effective bug report management. Bug reports are vital artifacts in this process, enabling developers to identify, prioritize, and resolve software defects. However, managing these reports effectively poses two major challenges: (1) accurate prediction of bug …

    calgary Repository record for Advancing Bug Report Management: Graph-Based Modeling, Large Language Models, and Quality Improvement (opens in a new tab)

  14. Improving Bug Localization with Textual and Multimedia Information Retrieval Leveraging Large Language Models

    Software bugs and failures cost the global economy billions of dollars every year. Software developers also spend ∼50% of their programming time tackling these bugs and failures. Over the last two decades, software engineering researchers have put forward many techniques using Information Retrieval …

    sask Repository record for Improving Bug Localization with Textual and Multimedia Information Retrieval Leveraging Large Language Models (opens in a new tab)

  15. Leveraging Q&A platforms to improve issue management in software projects

    Traditional issue management systems like Bugzilla are widely used in open source and commercial projects. Stack Exchange uses its online question and answer (Q&A) platform to manage bugs, which brings several new unique features that are not offered in traditional bug management systems. In this …

    queens Repository record for Leveraging Q&A platforms to improve issue management in software projects (opens in a new tab)

  16. Automatic bug triaging techniques using machine learning and stack traces

    … the option to report the crash using automated bug tracking systems. These tools capture software crash and failure data (e.g., stack traces, memory dumps, etc.) from end-users. These data are sent in the form of bug (crash) reports to the software development teams to uncover the causes of the …

    concordia Download PDF for Automatic bug triaging techniques using machine learning and stack traces (opens in a new tab)

  17. Toward Leveraging Artificial Intelligence to Support the Identification of Accessibility Challenges

    … of accessibility in user reviews or bug reports, to help technology professionals prioritize their handling, and, thus, to create more inclusive apps. Particularly, we propose a model that takes as input accessibility user reviews or bug reports and learns their keyword-based features …

    unt Repository record for Toward Leveraging Artificial Intelligence to Support the Identification of Accessibility Challenges (opens in a new tab)

  18. Analysis and Classification Of Software Fault-Proneness And Vulnerabilities

    Software bugs are expensive to fix and can lead to catastrophic consequences. Therefore, their analysis and the use of machine learning for prediction are of the utmost importance. Many prediction models have been proposed and different factors affecting the prediction performance have been …

    wvu Repository record for Analysis and Classification Of Software Fault-Proneness And Vulnerabilities (opens in a new tab)

  19. Data-mining the Ubuntu Linux Distribution for bug analysis and resolution

    … for users. To accomplish these goals, software bugs must be tracked and fixed. However, as the number of users increase and bug reports grow advanced tools such as data mining must be used to increase the effectiveness of all contributors to the project. Thus, this report involved collecting a …

    texas Repository record for Data-mining the Ubuntu Linux Distribution for bug analysis and resolution (opens in a new tab)

Page 1 of 5