Friday, November 6, 2015

Software Defects - The relation between Priority and severity


Priority

Severity

Results/Suggested solution

High
High

This combination, is created when a critical component/function is broken in the tested application (All blocker bugs that cause major delays, Loss of critical data Etc.), and will affect the Engineering progress, Business reputation or the end clients.



Examples :
-          Credential window that failed to transfer the log in command.
-          An Application that failed to be installed on a supported platform.
-          Functionality that creates memory leaks.
-          Etc.

High
Low

This combination, is created when the bug doesn’t have any major effect on the tested software, in most cases, it’s a minor issue or cosmetic bug, that will severely affect the company reputation.


Examples:
-          Company logo that displayed with the wrong colors.
-          Spelling mistakes on major locations in the software.

Low
High

This combination, is created when a bug will affect a specific functionality that doesn’t affect the testing effort, the bug will occur in rare situations that in many cases are not reproducible.



Examples:
-          Error notification that occurs when the user press two times on the same button.
-          Log In operation that will fail if the user insert a user name with 20 chars.


Low
Low

This combination, is created when a minor bug is found and doesn’t affect the functionality or any related aspects that may arm the company reputation.



Examples:
-          Wrong Font size on specific location/error notification.
-          Minor notification that displayed with delay of 0.5 Sec.

No comments:

Post a Comment

My Presentations