This document provides an overview of a bug tracking system called Bug Zero. It begins with definitions of what a bug is and an introduction to bug tracking systems and their purpose. It then describes some important facts that are typically recorded in a bug tracking system database. The document outlines the benefits of centralized bug tracking and different types of bug trackers. It provides details about Bug Zero, including its advantages, stages of use, and screenshots. It concludes with an estimate of the time required to install Bug Zero and references additional resources.

1. BUG-TRACKING-SYSTEM By:- Abhishek Pasricha

2. What is a Bug ? 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.

3. An Introduction 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.

4. Some important 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 main benefit of a bug-tracking system is to provide a clear centralized overview of development requests and their states.

5. 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]. In 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."

6. Contd… Some 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.

7. Different Types of Bug Trackers Mantis 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 Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track of outstanding problems ...

8. Contd... Fast Bug Track A web-based platform independent bug tracking system. FogBUGZ Web-based bug tracking system icTracker Web-based bug tracking, task management, and project management software from IC Soft, Inc.

9. Bug Zero 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.

10. Stages Involved :-

11. Why Bug Zero ? 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.

12. Advantages :- 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 No client software, no firewall issue, and accessible from anywhere on the internet through HTTP, HTTPS, or SMTP

13. Screenshots of Bug Zero:-

24. Time Consumed for the entire installation:- Download Java SDK 1.4.1 (36.2M, or later version) 8 min. 50 sec. at 256k/s Install Java SDK 5 min. Download Apache Tomcat 4.1.18 (8.3M, or later version) 4 min. 20 sec. at 256k/s Install Apache Tomcat 5 min. Download MySql 3.23 (9.3M, or later version) 4 min. 50 sec. at 256k/s

25. Install MySql 5 min. Download Bugzero (1M) 30 sec. at 256k/s Install Bugzero 5 min.

26. References :- http://www.google.com http://www.websina.com http://www.softpedia.com http://www.apache.org http://www.mysql.com http://www.wikipedia.org http://www.java.sun.com

27. Thank You