Bug-Tracking Mechanism

1.0 INTRODUCTION
The system which enables to detect the defect or bugs is known as Defect tracking system. It is also referred as bug tracking system. This system not only detects the bugs but also provides complete information about the detected bugs. The use of bug tracking systems as a tool to manage maintenance activities is extensive in which the systems serve as a central repository for monitoring the progress of bug reports, requesting additional information from reporters, and discussing potential solutions for fixing the bug(Lee et al, 2017). The main advantage of a bug-tracking system is that it provides a clear centralized overview of development requests including bugs and improvements, and their state. During defining the product roadmap, the valuable input is provided by prioritized list of pending.
The information provided in bug reports is used by developers to identify the cause of defect and narrow down the reasonable files that need fixing. According to the customer requirements, the developers develop the project. The quality checker identifies the bugs during the testing phase. When ‘n’ number of bugs is encountered, then tester adds the bug id and information in the database. The quality checker reports to both developer and project manager. For both the developer and project manager, the bug details in the database table are accessible. Many bug-tracking systems like which are used by most open source software projects, allow users to enter bug reports directly, whereas other systems are used only internally in a company or organization doing software development. Usually, bug tracking systems are integrated with other software project management applications. Bud tracking system is essential in software development and they are used widely by companies developing software products. In a corporate environment, a bug-tracking system is used for generating reports on the productivity of programmers at fixing bugs. Sometimes, this yields inaccurate results as different bugs may have different levels of severity and complexity. The severity of a bug is not directly related to the complexity of fixing the bug.
According to Angel et al, 2018 “A survey conducted amongst developers from the APACHE, ECLIPSE, and MOZILLA projects found out which information items are considered useful to help resolve bugs and found that items such as stack traces, steps to reproduce, observed and expected behavior, test cases, and screenshots ranked high on the list of preferred information by developers”. Fox & Orlina (2015) suggest that “previous research has shown that reporters often omit these important items and developers are then forced to actively solicit information from reporters and, depending on their responsiveness, this may stall development.” This affects the bug fixing mechanism as the bugs take long time to be fixed. This results in the gathering of unresolved bugs in the databases.
The main reason for this is that most bug tracking systems today have ended up by just becoming a complex search engine with too big databases of reported bugs but do not help in any way is resolving a bug. Due to this, the work of the developers is more difficult as resolving the bug is limited to the prior experience of the developer which may or may not be sufficient in resolving the bug on his own. Also, the tracking becomes more difficult because of the bugs. The situation may go worse if the developer is working n multiple projects. Since most of the current systems have too many complex interfaces and roles and limited access, tracking and fixing bugs became a difficult job for the developers today.
Bug tracking is a system which is used to solve out any type of bugs in any software. It is mostly useful for any software company. In this system we have design different types of user permission like developer, tester having different rights to connect software.(German et al, 2016) A bug tracking system helps us to keep track of bugs detected by tester of software and provide complete details regarding bugs to the developer as well as project manager of the software being tested. Bug Tracking System ensures the user of it will be able track the bug details as well as the status of debugging. For many years, bug-tracking mechanism is employed only in some of the large software development houses. Most of the other small firms and developers never bothered with bug tracking at all, instead they simply relied on shared lists and email to monitor the status of defects. This procedure is error-prone and tends the developer to consider the bug as insignificant which ends up being dropped or ignored. Bug Tracking System plays a vital role in the testing phase. The Bug Tracking System maintains the different user interfaces separately i.e., it provides separate environments for project manager, developer and tester. Bugs will be assigned to a person along with a bug id, screenshot, description, project name, etc. Bug can be submitted to the tester with an attachment for detailed report of the bug. Admin can maintain users, projects, organizations, bug categories, bug priorities, status of bug etc.

1.1 AIM AND OBJECTIVE OF THE STUDY
The aim of this research is to study the bug and the mechanisms to resolve and its life cycle in which it is determined how the bug arises and its consequences.
This project aims at creation of a Bug Tracking System. 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. This system provides the following facilities.
The objectives of this system are:
• To keep track of employee skills and based on the skills assigning of the task is done to an employee.
• Employee does bugs capturing. It can be done on daily basis.
Various Reports are generated by this System for an employee and as well as to a manager.

1.2 STATEMENT OF THE PROBLEM
• Information retrieval is a very big process.
• Lack of organization of the files may porn to information loss due to accidental deletion of files.
• No security because the files are visible to the users.
• Report generation will be a big task.

1.3 SIGNIFICANCE OF THE STUDY
Bug tracking is the process of reporting and tracking the progress of bugs from discovery through to resolution, where a bug is defined as a deviation from requirements. Other terminology frequently used to describe this process include
• problem tracking
• change management
• fault management
• trouble tickets

1.4 SCOPE AND LIMITATION OF THE STUDY
This study covers design and implementation of a Bug Tracking Mechanism. Bug tracking systems are most commonly used in the coding and testing phases of the software development process. However, tracking systems can in fact be used for many other purposes such as general issue tracking, simple task lists, help desk situations or contact management, where the focus is on the tracking aspect rather than what is being tracked. Even in software development, tracking systems are quite often not limited to simply tracking bugs, but extended to track feature requests or enhancements as well as enquiries.

1.5 DEFINITION OF TERMS
Bug :- A software bug (or just “bug”) is an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (e.g., producing an incorrect result). Most bugs arise from mistakes and errors made by people in either a program’s source code or its design, and a few are caused by compilers producing incorrect code.
Bug report:-A bug report is a document that contains all information on a certain bug. Usually, it includes the data of a person who has detected it and the information on the possible ways of its correction.
Bug list:-Each software development project has its own bug list. It is a document that contains all information on the bugs that were detected during a certain project.
Bug tracking tool:-A bug tracking tool is a software application designed to automate most stages of the bug tracking process.