1 / 12

Problem Tracking

Explore bug states, problem tracking systems, fix methods, and role-playing techniques in software quality assurance. Learn the importance of a Change Control Board and how to manage reported problems effectively. Dive into project monitoring and problem resolution.

sflowers
Download Presentation

Problem Tracking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Problem Tracking CSSE 376 Software Quality Assurance Rose-Hulman Institute of Technology March 14, 2007

  2. Outline • States of bugs • Problem tracking systems • Role playing: testing and problem tracking

  3. States of Bugs

  4. Defer New Fix Repaired Fix Verified Trash How Bugs Change States Fix later Code changed Test passes Fix now Test failed No fix needed

  5. Change Control Board (CCB) • Reviews change requests (bug reports) • Decides whether to: • fix now • defer until later • reject • May bundle collections of changes together

  6. 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

  7. View All ProblemsNote that the table columns are different here.

  8. View One Problem

  9. Update a Problem Entry

  10. Summary Report

  11. Cartoon of the Day

  12. Role Play!

More Related