HeaderSIS.jpg

Team SG Cares Bug Log

From IS480
Jump to navigation Jump to search

Bug Metric

Metric

  • Goal: Optimize code quality
  • Question: Under what circumstances do we reschedule our project to solve severe bugs?
  • Metric: Severity of bugs found in a metric
  • Use: To decide when do we reschedule our project to solve severe bugs
Level of Severity Description Examples
1 Error has little/no impact to the application, does not need to be fixed unless extra time is available.
  • Cosmetic problems i.e. misalignment
  • Grammatical errors/typo
2 Error causes some minor inconvenience to users, but does not affect application functionality.
  • User has to click on several ‘submit’ buttons before the next page loads
3 Error has substantial amount of impact to the application. May cause application to crash.
  • Application crashes at seemingly random times but at extremely low frequency and no permanent damage
  • Logic errors, functions may not work as planned
4 Error is critical, results in frequent system crashes.
  • Total inability to run the application; crashes upon startup
  • Loss of persistent data

Points Calculation:


Total = (Lvl 1 Errors) * 1 + (Lvl 2 Errors) * 5 + (Lvl 3 Errors) * 10 + (Lvl 4 Errors) * 15


Course of Action

Total Points Course of Action
Points <= 10 Not important – fix problem(s) during the last iteration, unless there is extra time (and nothing else is more important than this)
10 < Points <= 15 Fix the bug(s) during the debugging time until total points is left to 10 and below
15 < Points Halt project development immediately to resolve issues until total points is below 10


Bug Log

Bug Log.png

SG Gives Home Page

Back to Main