how do we assign priority and seviority levels

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Answer by sarma
Submitted on 1/3/2004
Rating:	Rate this answer:
seviority is assigned based on the impact on the risk.The risk may be human life or huge amount of money business specific. example If a bug in financial application wrong calculation of interest which may cause the bank to suffer huge financial losses(legal and may need the bank to close) then sevority is given as 1 (highest) and need to be fixed.the bug may be related to printing first name first and last name second.which willl have less impact on the business seviority is less say 4. Priority comes when we are fixing the bug which one needs to be taken first for fixing.This decision is taken by the schedule of the project. If you take the above case if additional information is required for interest calculation and the delivery got enough time then priority can be given to less seviority bug then high seviority bug.

Answer by Buddha Apparao
Submitted on 10/13/2005
Rating: Not yet rated	Rate this answer:
seveority is the effect of a defect on the application. Priority is the order in which the defect has to be resolved. the different combinations of seveority and priority are 1. high seveority and low priority 2. High seveority and high priority 3. Low severioty and high priority 4. low severioty and low priority. in case of 1. the application is crashing but will be used very rarely (i.e yearly or monthly) in case of 2. the application crashes or misbehaves and is used frequently. in case of 3. the application misbehave but the system does not crash and effects the other parts of the application. in case of 4.the application functions but the display or order and user convenence is not provided.

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home | FAQ-Related Q&As | General Q&As | Answered Questions ]

Question by narendra
Submitted on 8/5/2003
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating:	Rate this question:
how do we assign priority and seviority levels

Answer by jagan
Submitted on 3/24/2004
Rating:	Rate this answer:
based on priority we have to classify the severity

Answer by KrishnaKishore
Submitted on 5/18/2004
Rating:	Rate this answer:
Based on the severity we can assign the priority. severity means like a bug,bug's like a Critical ,Major,Minor,cosmetic,suggestion etc... Based on to the bug we can assign the priority. priority like Immediately,at the early stage,normal, later. if Bug is Critical we can assign priority like Immediately

Answer by sangi
Submitted on 3/4/2005
Rating: Not yet rated	Rate this answer:
Based on the severity, priority should be given. high severity: if the defect iss how stopper priority: urgrnt severity level 2: missing functionality priority: high low severity: cosmetic or typo error

Answer by Piyush Sharma
Submitted on 11/24/2005
Rating: Not yet rated	Rate this answer:
Severity : Impact of defect on system. Priority : Priority of fixing defect. I disagree with Kishor and Jagan that based on severity we should decide priority. consider a scenario: Client visit your office and you want to give them a demo. In such case a UI defect might be low in severity but should have high priority so its not always that hi severity defects should be fixed first. If such wud have been the case Priority of defect would have not been required. Best Regards, Piyush Sharma

Answer by eeeShara
Submitted on 4/24/2006
Rating: Not yet rated	Rate this answer:
Priority - How Prioir the Bug is to be fixed, this had to be analysed by the tester based on the complete understanding of the SWS SRS SFS etc.. Sevior - The rating of Sevior has to be analysed either it is High / Medium/ low - based on the Bug which was identified in the application.

Answer by Sheba
Submitted on 6/7/2006
Rating: Not yet rated	Rate this answer:
Priority is Business Priority reflects the project manager's assessment of how soon the bug should be fixed. How important is it to the business that we fix the bug Severity is Technical Severity reflects the customer's or tester's perception of how bad the bug is, how nasty is the bug from a technical perspective

Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer: