Project Management

Software Bugs

last edited by: Anupam on Sep 10, 2016 2:00 AM login/register to edit this page
Contents
1 Bug Severity
2 Bug Priority
3 References

Appearance of an error on expectation of software is called a bug. Bugs are neither good or bad. Some bugs are important and have high priority while other are dangerous and have high severity. For example -runtime errors, compilation errors.

Bug Impact can be categorized as -

  1. Low
  2. Medium
  3. High
  4. Urgent

Bug Severity

Severity of a bug is impact of the bug on the software. Severity Levels can be defined as :

  1. Urgent/Showstopper (S1)
  2. Medium/Workaround (S2)
  3. Low (S3)

Bug Priority

Priority of the bug describes the importance and order in which the bug should be fixed.

Example:

  1. Fix immediately
  2. Fix as soon as possible
  3. Must fix before next milestone
  4. Must fix before final
  5. Fix if possible
  6. Optional - use your own judgment

References

  1. Debug It!: Find, Repair, and Prevent Bugs in Your Code. Paul Butcher. Pragmatic Bookshelf, 2009.
  2. The Software Bug Book: Thoughts on Software Quality. Bill Marjerison. CreateSpace Independent Publishing Platform, 2013.
last edited by: Anupam on Sep 10, 2016 2:00 AM login/register to edit this page

ADVERTISEMENTS

"Whenever you find that you are on the side of the majority, it is time to reform."

- Mark Twain

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters