Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

Whats'the difference between Seviroty and priority ..
Please answer in the follwoing way ?
1) Who will give the priority and Sevirity (ex -
client/users and testers/developers) ?
2) If the client wants to give a high importance to an
issue and for that the QA and developement don't think that
much importance then how would be the situation ?
3) If a high sevirity issue is there but another issues is
there with high priority .. Then which issue will be fixed
first and vice versa ?

Answer Posted / sudipto

Priority is how important is the issue at a perticular
point/duration of time
E.g: Fixing of a bug in balance sheet during year end
Development of a division wise performance report for
chairman of the company
completion of go live critical developments
In most of the cases the priority is defined by the users
or the PM, delivery manager ...
priority may be very high, high, medium and low

Severity is the extent/degree of impact of a problem on the
system/program or other functionalities of the business
Generally defined by the Functional , technical, QA &
testers after conducting a through impact analysis
Severity may be critical (show stopper),major and minor.
E.g: incomplete testing (positive and negative) of the
individual developments is highly severe as they may have
high impact on other functionalities while conducting
integration testing

Priority is associated with an incident and severity is
associated with a problem

Production server down or network failure is both high
priority and high severity as business will stop
functioning and there may be huge financial loss incurred.

Answer to Q-2: Analyze the program to find out the impact
that it will have on the daily transactions and the user
base that will get effected by that. Discuss with the team
and PM and according take the decission.if impact is high
and the risk is high in near future then go and fix it else
convey the message to the client by giving the effort
estimation.

Answer-3: In both the case analyze due to which the the
business process is getting effected highly and for what
duration and then take the call accordingly. All depends on
the type of issue.

Is This Answer Correct ?    1 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What if the project is not big enough to justify extensive testing?

1127


Diffrence b/w compiled module and shared repository?

2112


Can you perform regression testing performed manually?

1081


Define bug leakage and bug release?

1353


Explain the difference between the verification and validation?

1166


Define use case testing.

1139


What is exploratory testing and specification-driven testing?

1228


What if the software is so buggy it ca not really be tested at all?

1164


What is bug?

1103


List out various tools required to support testing during development of the application?

1139


What is Defect Density ? What is the formula? Explain with example

38096


What is binary portability testing?

1100


Explain what should your qa documents include?

1145


In asset accounting we are run depreciation in 10% now we are in 6th period . But now our client says that the depreciation percentage is 12% but we have wrongly calculated on 10%. So what are the process we have calculated actual percentage.

1068


Describe use case testing?

1204