Is there any bug classification matrix or a bug classification guideline available? The idea is to have a methodology in place which helps in clear cut demarcation as to what would be called as a critical or major or minor bug so that the tester follows a methodology rather than perception in classifying a bug.
This classification has been written and re-written probably more times than code to parse a string.
I'm thinking you could:
1) search this site
2) search RUP
3) look in some of the test plan and SQA plan templates.
4) If you are using a commercial defect tracking tool - either the software itself of the accompanying documentation will offer some generic classifications.
Sometimes there are no clear lines of demarcation. I find it is best to allow the test engineer to call it as they see it! However, the key to the latter is that there is a defect management process that allows other perspectives so that a final agreement on both severity and priority can be reached - ultimately trigger the correct repair work at the correct time. The reason I like this is as follows:
Example: A test engineer may encounter an obvious show-stopper and naturally call it a high priority with critical severity. A developer may look at the same bug and say it's a low since it takes only a minute to fix.
The process I suggested usually takes the form of a frequent meeting to review all defects and classify them. This meeting should include the BA perspective, thus representing the customer/end-user.
Wow, that is a wonderful resource. I think I will use some of the ideas contained in that paper to organize my thought when designing tests. I often find things I missed while I am running my test list and have to go back and create more test cases to cover what I missed. If I could cover more possible points of failure the first time it sure would make my life easier.