ABSTRACT

Bug-Tracking mechanism is employed only is some of the large software development houses. Most of the others never bothered with bug tracking at all, and instead simply relied on shared lists and email to monitor the status of defects. This procedure is error-prone and tends to cause those bugs judged least significant by developers to be dropped or ignored. Bug-Tracking System is an ideal solution to track the bugs of a product, solution or an application. Bug Tacking System allows individual or groups of developers to keep track of outstanding bugs in their product effectively. This can also be called as Defect Tracking System. The Bug Tracking System can dramatically increase the productivity and accountability of individual employees by providing a documented work flow and positive feedback for good performance.
Features:
 Product and Component based
 Creating & Changing Bugs at ease
 Query Bug List to any depth
 Reporting & Charting in more comprehensive way
 User Accounts to control the access and maintain security
 Simple Status & Resolutions
 Multi-level Priorities & Severities
 Targets & Milestones for guiding the programmers
 Attachments & Additional Comments for more information
• Robust database back-end
Technology Used
Operating System : Windows XP or above
User Interface : HTML, CSS
Client-side Scripting : PHP
Back End : MySQL
Web Server : Apache Tomcat 7.0.22
IDE : NetBeans 7.1

 

TABLE OF CONTENTS

Title Page

Certification

Dedication

Acknowledgment

Abstract

Table of Contents

 

CHAPTER ONE

1.0     General overview  and introduction

1.1     Introduction

1.2     Statement of Problem

1.3     Aim and Objective         s

1.4              Scope and Limitation

1.5     Significance of the Study

1.6     Definition of Terms

 

CHAPTER TWO        

2.0     Literature Review and System Analysis

2.1     Literature Review

2.2     Feasibility Study

2.2.1 The technical feasibility

2.2.2 the operation feasibility

2.2.3 The Economic feasibility

2.3     System Analysis

2.3.1 Fact Finding

2.4     Analysis of the Existing System

2.5     Problems of the Existing System

2.6     Solution to the Problems of the Existing System

 

CHAPTER THREE

3.0     System Design

3.0.1 Overview of design

3.1     Architectural Design

3.2     Hierarchical Design

3.3    Abstract Specification

3.3.1  Input Specification

3.3.2  Output Specification

3.4     Interface Design

3.5     Data Structure Design

3.6     Algorithm Design

 

CHAPTER FOUR

4.0     System Implementation and Documentation

4.1     System Implementation

4.2     Choice of Programming Language

4.3.0  Installation Requirement

4.3.1  Hardware Requirement

4.3.2 Software Requirement

4.4     Process of Installation

4.5     System Testing

4.6     System Changeover

4.7     System Documentation

 

CHAPTER FIVE

5.0      Summary, Conclusions and Recommendations

5.1      Summary

5.2      Conclusion

5.3       Recommendations

Reference

APA

Bug-Tracking Mechanism. (n.d.). UniTopics. https://www.unitopics.com/project/material/bug-tracking-mechanism/

MLA

“Bug-Tracking Mechanism.” UniTopics, https://www.unitopics.com/project/material/bug-tracking-mechanism/. Accessed 19 September 2024.

Chicago

“Bug-Tracking Mechanism.” UniTopics, Accessed September 19, 2024. https://www.unitopics.com/project/material/bug-tracking-mechanism/

WORK DETAILS

Chapters:
5
Pages:
35
Words:
8124

Here’s a typical structure for Bug-Tracking Mechanism research projects:

  • The title page of Bug-Tracking Mechanism should include the project title, your name, institution, and date.
  • The abstract of Bug-Tracking Mechanism should be a summary of around 150-250 words and should highlight the main objectives, methods, results, and conclusions.
  • The introduction of Bug-Tracking Mechanism should provide the background information, outline the research problem, and state the objectives and significance of the study.
  • Review existing research related to Bug-Tracking Mechanism, identifying gaps the study aims to fill.
  • The methodology section of Bug-Tracking Mechanism should describe the research design, data collection methods, and analytical techniques used.
  • Present the findings of the Bug-Tracking Mechanism research study using tables, charts, and graphs to illustrate key points.
  • Interpret Bug-Tracking Mechanism results, discussing their implications, limitations, and potential areas for future research.
  • Summarize the main findings of the Bug-Tracking Mechanism study and restate its significance.
  • List all the sources you cited in Bug-Tracking Mechanism project, following a specific citation style (e.g., APA, MLA, Chicago).