Thursday, January 12, 2006

Severity and Priority

 
High Severity with High Priority --- If "Login" is required in Application and not able to login in the application. If logic of the Application is wrong and it is affecting complete Application or it is a base of the application, like Masters in the Software.

High Severity with Medium Priority --- If Functionality is working but not 100% Accurate than we take that is in Medium Priority.

High Severity with Low Priority --- If Design of the Page is not as per the requirement, say, Client want Advertisement on the top and we have not included in design than Severity is High but Priority might be low if it can be added easily. It depends on the Design of the application.
 
 Medium Severity with High Priority – If there is an error in calculation, than it will be Medium Severity and High Pririty.

Medium Severity with Medium Priority --- If there is an error in programming that it is storing all the /p and O/p Values in the database but we can’t see these records as per the requirement. And thiis can be easily debug and not affecting on the system

Medium Severity with Low Priority --- Currency should be 2 decimal points but programmer showing that in integer or whole value. Than priority will be low, because it is float in program but he/she showing its whole value in reports.
 
Low Severity with High Priority --- In Designing, Image is Distorting.

Low Severity with Medium Priority --- spelling mistakes, etc

Low Severity with Low Priority --- Minor Designing issues,

2 comments:

Unknown said...

Hi Venkat,

Really it is very useful and helpful document.

Thanks

Anonymous said...

Hey was tryin to find this for a long time n i found it here. good examples but if you could put some more light on medium severity & high ,medium, low priority with examples of Black box testing then it would have been more clear