Web Based Bug Tracking System

Electrical Electronics Engineering

A web-based bug tracking system is a comprehensive software tool designed to streamline the process of identifying, documenting, and resolving issues or bugs within software development projects. This dynamic platform serves as a centralized hub where teams can log, prioritize, assign, and track bugs throughout their lifecycle, ensuring efficient communication and collaboration among stakeholders. By leveraging features such as real-time updates, customizable workflows, issue categorization, and robust reporting capabilities, organizations can enhance productivity, streamline bug resolution processes, and ultimately deliver high-quality software products to their customers. With its user-friendly interface and scalability, a web-based bug tracking system empowers teams to efficiently manage software defects while maintaining transparency and accountability, thereby facilitating continuous improvement and fostering a culture of excellence in software development.

ABSTRACT

Bugs have been existed as a problem in the system and they are normally inevitable in software development. Most software bugs arise from mistakes and errors made by people in either a program, source code or its technical design. Huge amount of bugs could be found in system development. It was relatively difficult to manage bugs in simple word documents or remember everything in one’s head. Thus Change and Bug Tracking (CBT) System has been introduced in order to keep track of the reported bug in the system. By using this tracking system, every user can report and follow up the issue in the system. This system provided a platform for users from different departments to report issues and understand the latest progress in a product. It consolidated and organized information in single system and centralized data repository for the changes and bugs in system. Besides, this system could be accessed by team members concurrently to improve efficiency and they can search particular information in the system easily. It made communication between teams more effective and all the bugs and changes are recorded in web based system and hence the system is scalable.

TABLE OF CONTENTS

COVER PAGE

TITLE PAGE

APPROVAL PAGE

DEDICATION

ACKNOWLEDGEMENT

ABSTRACT

CHAPTER ONE

1.1 INTRODUCTION

1.2 OBJECTIVE OF THE PROJECT

1.3 APPLICATIONS OF THE PROJECT

1.4 SIGNIFICANCE OF THE PROJECT

1.5 DIFFERENT TYPES OF BUG TRACKERS

1.6 ADVANTAGES OF THE PROJECT

1.7 PURPOSE OF THE PROJECT

1.8 APPLICATION OF THE OF THE PROJECT

CHAPTER TWO

LITERATURE REVIEW

2.1 THE HISTORICAL BACKGROUND OF BUG TRACKING SYSTEMS

2.2 OPEN SOURCE BUG TRACKING TOOLS

CHAPTER THREE

METHODOLOGY

3.1 SYSTEM DESIGN ARCHITECTURAL DESIGN

3.2 BASIC DESCRIPTION OF THE SYSTEM

3.3 SOFTWARE REQUIREMENT SPECIFICATION

3.4 FUNCTIONAL REQUIREMENTS MAIN MODULE

CHAPTER FOUR

4.1 HOW BUG TRACKING WORKS

4.2 COMPONENTS

4.3 PART OF INTEGRATED PROJECT MANAGEMENT SYSTEMS

4.4 BUG TRACKING AND TEST MANAGEMENT

CHAPTER FIVE

CONCLUSION
RECOMMENDATION
REFERENCES

CHAPTER ONE

INTRODUCTION

A bug is the common term used to describe an error, flaw[fault], mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. 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.

A bug tracking system is a software applications that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a sort of issue[matter] tracking system. A major component of a bug tracking system is a database that records facts about known bugs. The report of database can consists of several information which can also be called facts.

Facts may include the time a bug was reported, its severity, the erroneous [wrong]program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug.

The prioritized list of pending items (often called backlog) provides valuable input when defining the product roadmap, or maybe just "the next release".[Sub-version]. a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. A local bug tracker (LBT) is usually a computer program used by a team of application support professionals (often a help desk) to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their "own language" and not the "language of the developers.

1.1 OBJECTIVES OF THE PROJECT

This work was introduced in order to keep track of the reported bug in the system. By using this tracking system, every user can report and follow up the issue in the system. This system provided a platform for users from different departments to report issues and understand the latest progress in a product

1.2 SIGNIFICANCE OF THE PROJECT

Bug trackers are designed to be used with distributed revision control software. These distributed bug trackers allow bug reports to be conveniently read, added to the database or updated while a developer is offline. Distributed bug trackers include DisTract and Bugs Everywhere.

The main benefit of a bug-tracking system is to provide a clear centralized overview of development requests (including bugs and improvements, the boundary is often fuzzy), and their state. The prioritized list of pending items (often called backlog) provides valuable input when defining the product road map, or maybe just “the next release”.

In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results because different bugs may have different levels of severity and complexity. The severity of a bug may not be directly related to the complexity of fixing the bug. There may be different opinions among the managers and architects.

A local bug tracker (LBT) is usually a computer program used by a team of application support professionals (often a help desk) to keep track of issues communicated to software developers. Using an LBT allows support professionals to track bugs in their “own language” and not the “language of the developers.” In addition, an LBT allows a team of support professionals to track specific information about users who have called to complain — this information may not always be needed in the actual development queue. Thus, there are two tracking systems when an LBT is in place.

1.3 DIFFERENT TYPES OF BUG TRACKERS

Mantis Bug Tracker is a popular web-based bug tracking system. It is written in PHP works with MySQL, MS SQL, and PostgreSQL databases. Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track of outstanding problems.

A web-based platform independent bug tracking system. Web-based bug tracking, task management, and project management software from IC Soft.

Bug Bugzero is cross-platform and works on Windows, Unix/Linux, and Mac OS operating systems. A bug tracking system for software defect tracking, and a general issue management tool for helpdesk customer support and trouble ticketing Bugzero provides an enterprise-grade cost-effective scalable solution to increase team work efficiency. It is easy to use, yet still flexible and adaptive, and can be configured to accommodate your organization's unique business process and workflow.

Freeware open-source bug tracking tools such as Bugzilla bug tracking system, GNATS problem report database, or Debian defect tracking system usually takes a long time to set up, are not easily customizable (even for simple things like add or remove a field), and are not fully supported. Expensive defect tracking systems may have a million poorly-written never used "features", but they certainly do not worth the cost. They are too complex, rarely configured properly, confusi.ng, and cumbersome to be effectively used.

1.4 ADVANTAGES OF THE PROJECT

Standard technologies, web-based, lightweight, feature-rich, robust, fast, reliable, and exceptional usability Cross platforms, one code base written in Java™ and J2EE™, truely run anywhere and everywhere Cross database systems, standard SQL, scalable, and modular database schema client software, no firewall issue, and accessible from anywhere on the internet through HTTP, HTTPS, or SMTP

1.5 PURPOSE OF THE PROJECT

web- based Bug Tracking System is to test the application for the bugs and report it to the project manager and developer.
The main intention behind the web- based Bug Tracking System is that to track bugs and report them.
Store the bug information with a unique id in the database.

1.6 APPLICATION OF THE OF THE PROJECT

Bug Tracking System is a web-based application that is designed to help quality assurance and programmers keep track of reported software bugs in their work.

Bugs will be assigned to a person with a bug id, flag, description, project name.
Bug can be submitted to the tester with an attachment for the bug detailed report.
Admin can maintain users, projects, organizations, bug categories, bug priorities, status of bug etc