A Survey on Software Bug Evaluation (original) (raw)
Related papers
Bug Tracing System: An Approach to calculate the Severity and Priority of Bugs
Finding and fixing software's bugs is a not easy task, and a significant amount of effort is dedicated by software developers on this issue. In the world of software one cannot get rid of the bugs, fixes, patches etc. each of them have a severity and priority associated to it. There is not yet any formal relation between these components as both of these either depends on the developer and tester and project manager to be decided on. On one hand, the priority of a component depends on the cost and the efforts associated with it. While on the other, the severity depends on the efforts required to accomplish a particular task. This work proposes a formula that can draw a relationship among severity and priority.
A survey on bug prioritization
Artificial Intelligence Review, 2016
Daily large number of bug reports are received in large open and close source bug tracking systems. Dealing with these reports manually utilizes time and resources which leads to delaying the resolution of important bugs. As an important process in software maintenance, bug triaging process carefully analyze these bug reports to determine, for example, whether the bugs are duplicate or unique, important or unimportant, and who will resolve them. Assigning bug reports based on their priority or importance may play an important role in enhancing the bug triaging process. The accurate and timely prioritization and hence resolution of these bug reports not only improves the quality of software maintenance task but also provides the basis to keep particular software alive. In the past decade, various studies have been conducted to prioritize bug reports using data mining techniques like classification, information retrieval and clustering that can overcome incorrect prioritization. Due to their popularity and importance, we survey the automated bug prioritization processes in a systematic way. In particular, this paper gives a small theoretical study for bug reports to motivate the necessity for work on bug prioritization. The existing work on bug prioritization and some possible problems in working with bug prioritization are summarized.
Improving Software Quality Assurance Using Bug Tracking System
—This paper entitled Improving Software Quality Assurance Using Bug Tracking System is mainly for applications developed in a company to keep track of employee skills and based on the skills assigning of the task is done to an employee and aims at creation of a Bug Tracking System for enhancing the software quality. This project will be accessible to all developers and its facility allows developers to focus on creating the database schema and while letting the application server define table based on the fields in JSP and relationships between them. Improving Software Quality Assurance Using Bug Tracking System is an automated system that can be useful to employees and the managers in any functional organization. This Bug Tracking System gives the facility to define the tasks in the organization and also allows the managers to track the bugs spent by the employee for that particular task. A report generation facility is supported in BTS (Bug Tracking System) that allows the managers to analyse which those skills by employee are utilized and those which are not utilized. This tool can help managers for Bug estimation per project or application. This tool helps employees to document their Bugs and analyse.
An Efficient Model for Effective Bug Triage
2016
Most of the software companies needs to deal with large number of software bugs every day. Software bugs are unavoidable and fixing software bugs is an expensive task. The goal of effective bug triaging software is to assign potentially experienced developers to new-coming bug reports. To reduce time and cost of bug triaging, an automatic approach is proposed in this paper that predicts a developer with relevant experience to solve or fix the new coming bug report. In this paper, the five term selection methods on the accuracy of bug assignment are used. In addition, the load between developers based on their experience is re-balanced. The proposed system is built with intention to suggest or recommend the bug and not to automatically assign it. This allows a window to handle real time crisis that come up during project development lifecycle. IndexTerms— Mining software repositories, application of data pre-processing, data management in bug repositories, bug data reduction, feature...
Software Maintenance and Resolving the Bugs for Bug Triage
Fixing bugs in software development companies is a big problem which needs a lot of money. A bug repository manages the software bugs. Usually the software projects include many developers. The duty of the project manager is to assign projects to the developers. In the existing system we use text classification technique for assigning projects or bugs which consumes a large space and produces a low quality bug data. To overcome this problem, instance selection and feature selection is introduce to increase accuracy and decrease scale all together. In our work we combine both these techniques in bug repositories to reduce data.
DESIGN OF AN EFFECTIVE MECHANISM FOR AUTOMATED BUG TRIAGE SYSTEM
— Nowadays IT companies are spending more than 45 percent of their cost in fixing software bugs. Traditionally these bugs are fixed by manual assignment to a particular developer; this approach causes too much dependency. The new and alternative approach is the Bug Triage System, which fixes the bug and assigns the reported bug to a developer automatically so that it decreases the time and cost in manual work. Combine instance selection with feature selection to simultaneously reduce data scale on the bug dimension and the word dimension. We propose to apply machine learning technique in bug triage to predict which developer should be assigned on the bug, based on its description by applying text categorization.
Effective Bug Tracking Systems: Theories and Implementation
IOSR Journal of Computer Engineering, 2012
Bug tracking is an essential discipline in the domain of software engineering. It has far reaching effects on the system when effectively used. The information provided in terms of bugs and solutions in the bug reports can help software engineers to act on them quickly and ensure that they are either rectified or eliminated from the system. The bulk of information provided in the bug reports may cause problem to developers in ascertaining poorly designed information. Therefore the bug tracking systems are to be improved and follow certain standards. To overcome the problem, we propose four fundamental directions to enhancing effectiveness of bug tracking systems. To demonstrate the efficiency of the proposed directions, we develop a prototype application that tracks bugs effectively by capturing essential information from users and help resolve bugs quickly. I.
CommIT (Communication and Information Technology) Journal, 2016
Computer bug elimination is an important phase in the software development process. A ticketing system is usually used to classify the identified bug type and to assign a suitable developer. This system is handled manually and error prone. This paper proposes a new bug classification method using the fast string search algorithm. The method searches the error string and compares it to the full text. The approach is deployed to the software development process at PT. Selaras Anugerah Lestari and it results in a significant reduction in the average value of the time required to handle the bugs.
Towards a Classification of Bugs to Facilitate Software Maintainability Tasks
Software maintainability is an important software quality attribute that defines the degree by which a software system is understood, repaired, or enhanced. In recent years, there has been an increase in attention in techniques and tools that mine large bug repositories to help software developers understand the causes of bugs and speed up the fixing process. These techniques, however, treat all bugs in the same way. Bugs that are fixed by changing a single location in the code are examined the same way as those that require complex changes. After examining more than 100 thousand bug reports of 380 projects, we found that bugs can be classified into four types based on the location of their fixes. Type 1 bugs are the ones that fixed by modifying a single location in the code, while Type 2 refers to bugs that are fixed in more than one location. Type 3 refers to multiple bugs that are fixed in the exact same location. Type 4 is an extension of Type 3, where multiple bugs are resolved by modifying the same set of locations. This classification can help companies put the resources where they are needed the most. It also provides useful insight into the quality of the code. Knowing, for example, that a system contains a large number of bugs of Type 4 suggests high maintenance efforts. This classification can also be used for other tasks such as predicting the type of incoming bugs for an improved bug handling process. For example, if a bug is found to be of Type 4 then it should be directed to experienced developers.