Bug Tracking for Improving Software Reliability

Bug Tracking for Improving Software Reliability

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 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

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.

The objectives of Bug Tracking System

  • 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.

Overview

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

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.

  • problem tracking

  • change management

  • fault management

  • trouble tickets

For a bug tracking software it is essential to have:

1. Reporting facility– complete with fields that will let you provide information about the bug, environment, module, severity, screenshots etc.

2. Assigning– What good is a bug when all you can do is find it and keep it to yourself, right?

3. Progressing through the life cycle stages– Workflow

4. History/work log/comments

5. Reports– graphs or charts

6. Storage and retrieval– Every entity in a testing process needs to be uniquely identifiable, the same rule applies to bugs too. So, a bug tracking tool must provide a way to have an ID, which can be used to store, retrieve (search) and organise bug information.

Component of Bug tracking system:

1.Interface (fronted)

2. Database (Back end)

A major component of bug tracking system is a database that record facts about known bugs. Facts included the time a bug was reported its severity , the erroneous program behavior and the identity of person who reported it and any programmers who may be working on fixing it.

Modules in the system:

1. Administrator

Create , delete and import user profiles.

Create and delete project details

Allow password changes

Can grant permission

2. General User

Contain Developer, tester, Team leader , project manager.

Can View All defect details but cannot edit the existing bug report.

Database Tables:

1. Login_tables

2. User_info_table

3. Project_info_table

4. Defect_Label

Limitations of the system:

Only the permanent employees can access the system.

System works with windows’98 and its compatible environments.

Advanced techniques are not used to check the authorization.

Once the employee is registered to a course cannot drop, without completing.

Future Enhancements:

It is not possible to develop a system that makes all the requirements of the user. User requirements keep changing as the system is being used. Some of the future enhancements that can be done to this system are:

As the technology emerges, it is possible to upgrade the system and can be adaptable to desired environment.

Because it is based on object-oriented design, any further changes can be easily adaptable.

Based on the future security issues, security can be improved using emerging technologies.

Attendance module can be added

sub admin module can be added

Bug Tracker- Lucid solutions

Lucid Solutions offers the most advanced processes and methodologies to assist publishers and developers to successfully certify, adapt and improve the quality of your consoles, mobiles, web and PC products while reducing time and cost.

we work in an extremely secured environment to analyse, evaluate, measure, report and successfully deliver a wide range of services.

We have highly trained and expert Quality Assurance Engineers for bug tracking and finding solutions.

Leave a Reply