Hi

Pls send me this answer.

regards

Rajesh.

Hi All

Pls find the answer

High seviority and low priority.

When the application has critical problem and it has to be solved after a month then we can say it as high seviority and low priority.

low seviority and high priority

When the application has trivial problem ie (less affected) and it has to be solved within a day then we can say it as low seviority and high priority

correctness(high severity)

dependent outputs are wrong(high priority)

final output wrong(low priority)

Following is an example for high severity and low priority:

High severity: Affecting end user

Low priority: Typos

High Priority Low Severity Bug:-

Home Page in web application has misspelled client name and found at the time of delivering the product.

Low priority High Severity Bug:-

Crash in some any module that is too be delivered later.

1]High Severity And Low Priority----If there is an application if that application crashes after mulple use of any functionality (exa--save Button use 200 times then that application will crash)

Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days.

2]High Priority And Low Severity---- If any Web site say Yahoo now if the logo of site Yahoo spell s Yho ----Than Priority is high but severity is low.

Because it effect the name of site so important to do quick ---Priority

but it is not going to crash because of spell chage so severity low.

Amit Hambarde

if u are able to launch an application 100 time but after that appliation gets crashed or any other defects arise like 'Data Lose data carsh etc..' the Severity will be high always as it affacts the application functionality and priority will be decided low beacuse till 100 time application is working perfectly.

Hi

can u describe eaborately about the question.

Q:- high severity & low priority

Q:- high priority & low severity...

waiting for ur mail