Interested to Buy Any Domain ? << Click Here >> for more details...
Pls give examples for
1. High severity and high priority.
2. High severity and low priority.
3. Low severity and high priority.
4. Low severity and low priority
- 5 Answers
- 43214 Views
- TCS, I also Faced
- E-Mail Answers
Answer Posted / mike k.
A good way to clarify this may come from the so-called
"Failure Mode Effects Analysis" process in quality Management.
A triad of Severity (S), Occurrence (O) and Detectability
(D) produces a so-called "risk priority number" (P).
"S" - "How much money do we lose if this happens".
"O" - "What ratio of business processes are affected?"
"D" - "Can we find out in time if the defect occurred?"
If S is high, but O + D are low, then P is low.
If S is high and O + D are high, then P is high.
If S is low and O + D are low, then P is low.
If S is low and O + D are high, then P is high.
Examples:
S high, O + D low:
Once a year, the database must undergo housekeeping or
tablespaces will one day overflow, crashing the entire
system, denying every business process until the tablespace
is freed and the application restored. Unfortunately, the
script does not work.
This is a very high severity defect.
This is very easy to detect (monitor tablespaces) and will
not occur quickly (a year down the line) so the priority is low.
S high, O + D high:
The corporate SOA "swallows up" fire-and-forget requests for
a certain constellation of parameters.
As you cannot know when a request got lost, you do not know
when or which business processes may fail.
As such, the priority is very high.
S low, O + D low:
The "undo" functionality of an application produces a
warning message when no change has been made prior to
execution. This irritates the user as "no action" or a
grayed-out button would be preferred.
Other than that, there is no business impact.
As such, there is a low priority: The developer might fix it
when by chance they are updating the module, otherwise no
sane project manager would waste budget on a fix.
S low, O + D high:
This is the typical scenario of "Defect with Business
processes unaffected".
The "Help" function from a portal sporadically causes the
servers to crash.
(There is a very easy workaround: just don't use the "Help",
and therefore people can still commence every business process.)
Something, however, still needs to be done, and that
quickly. An easy fix may be to disable "Help" - but you just
can't go live with that thing!
| Is This Answer Correct ? | 4 Yes | 2 No |
Post New Answer View All Answers
How do you perform configuration management with typical revision control systems?
what is the difference between website and web based application ?
how will you test transfer funds module...explain in detail
How can data caching have a negative effect on load testing results?
hi every one can you send me ISTQB Course material on my Email id deeptimundra997@gmail.com
how we write test cases to brs,srs,hlds,llds
Explain the advantages of automation over manual testing?
how mapp the defect id in quality center?
How does quality control differ from quality assurance?
What is pesticide paradox? How to overcome it?
what are the risk factors in the project? what is the base for testplan and entry criteria ,exit criteria for test plan?
what are the typical problems in web testing?
How do you test a web application for dump and deaf??
Is compatabilitytestig and port testing are same
aplitue questions will be based on wich type ?
