HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T1 TheTalkies Bug Tracker"

From IS480
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
== Bug Tracker ==
 +
 
Goals:  
 
Goals:  
 
* To keep track of unsolved bugs
 
* To keep track of unsolved bugs
Line 12: Line 14:
 
<b>Bug Tracker</b>
 
<b>Bug Tracker</b>
 
<br/><br/>
 
<br/><br/>
<center>[[Image:Bug_tracker.png]]</center>
+
<center>[[Image:Bug_tracker(final).png]]</center>
 
<br/>
 
<br/>
In the graph, we show how many bugs found in a particular iteration and how many bugs fixed in which iteration. For some bugs, we could not solve in the assigned iteration. Later iteration, therefore, the number of bugs fixed is higher than the number of bugs found. For example, in iteration 3, actually bugs found is only 2 but because of the leftover bugs from iteration 2 we have to solve 3 bugs instead.
+
In the graph, we show how many bugs found in a particular iteration and how many bugs fixed in which iteration. For some bugs, we could not solve in the assigned iteration. In later iteration, therefore, the outstanding bugs is combined with the leftover bugs from previous iteration and the found bugs in particular iteration. For example, in iteration 6, the leftover bug from iteration 5 is one and number of bugs found in iteration 6 is 11 so the outstanding bugs in iteration 6 is 12. But we can solve only 6 bugs in that iteration. So the other 6 bugs are postponed to next iteration 7.

Latest revision as of 19:09, 24 November 2011

Bug Tracker

Goals:

  • To keep track of unsolved bugs
  • To ensure quality of the Web Application
  • To let the team knows which function has more bugs.

Severity Level

Severity levl.png

In our bug tracker sheet, we assign each bug with its calculated severity level so that the debugger knows which bugs is more urgent to be solved so that it will not affect the other features.

Bug Tracker

Bug tracker(final).png


In the graph, we show how many bugs found in a particular iteration and how many bugs fixed in which iteration. For some bugs, we could not solve in the assigned iteration. In later iteration, therefore, the outstanding bugs is combined with the leftover bugs from previous iteration and the found bugs in particular iteration. For example, in iteration 6, the leftover bug from iteration 5 is one and number of bugs found in iteration 6 is 11 so the outstanding bugs in iteration 6 is 12. But we can solve only 6 bugs in that iteration. So the other 6 bugs are postponed to next iteration 7.