HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 4: Line 4:
  
 
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.
 
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.
 +
 +
Goals:
 +
* To keep track of unsolved bugs
 +
* To ensure quality of the Web Application
 +
* To let the team knows which function has more bugs.
 +
  
 
<b>Bug Tracker</b>
 
<b>Bug Tracker</b>
Line 9: Line 15:
 
<center>[[Image:Bug_tracker.png]]</center>
 
<center>[[Image:Bug_tracker.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. According to that graph, we can keep track of unsolved bugs, ensure quality of the Web Application and let the team knows which function has more bugs.
+
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.

Revision as of 17:24, 21 November 2011

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.

Goals:

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


Bug Tracker

Bug tracker.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. 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.