Problem Tracking
CSSE 376 Software Quality Assurance
Rose-Hulman Institute of Technology
March 14, 2007
1
Outline
States of bugs
Problem tracking systems
Role playing: testing and problem tracking
2
States of Bugs
State
Owner
Description
New
Tester
Problem reported
Fix
Developer Developer assigned to fix
Defer
CCB
Fixing postponed
Trash
CCB
No fix needed
Repaired Developer Developer completed fix
Fix
verified
Tester
Fix has been verified by
tester
3
How Bugs Change States
Fix later
Defer
Code changed
New
Fix now
No fix needed
Trash
Fix
Repaired
Test passes
Fix Verified
Test failed
4
Change Control Board (CCB)
Reviews change requests (bug reports)
Decides whether to:
fix now
defer until later
reject
May bundle collections of changes
together
5
Problem Tracking Systems
 Database of reported problems (bugs)
 ID
 Status (new, fix, defer, repaired, fix verified)
 Severity
 Creator (person reporting problem)
 Date created
 Date last updated
 Description
 ...
 Provide summary reports for project monitoring
6
View All Problems
Note that the table columns are different here.
7
View One Problem
8
Update a Problem Entry
9
Summary Report
10
Cartoon of the Day
11
Role Play!
12