Part 7 "Test Process & Incident Management" As a technical test analyst, you are involved in a risk analysis session using the Failure Mode and Effect Analysis technique. You are calculating risk…

Question

Options

• ASeverity and priority
• BFunctionality, reliability, usability, maintainability, efficiency and portability
• CLikelihood and impact
• DFinancial damage, frequency of use and external visibility

• A
  6% (3)
• B
  2% (1)
• C
  90% (46)
• D
  2% (1)

Explanation

In FMEA (Failure Mode and Effect Analysis), risk is fundamentally assessed by combining likelihood (how probable a failure is to occur) and impact (how severe the consequences are), which together produce a risk priority value - making C the correct answer.

Why the distractors are wrong:

• A (Severity and priority): Severity is relevant, but priority is an output of risk analysis, not an input factor. Likelihood is the missing piece here.
• B (Functionality, reliability, usability, maintainability, efficiency, portability): These are the ISO/IEC 9126 software quality characteristics - a completely different framework unrelated to FMEA risk calculation.
• D (Financial damage, frequency of use, external visibility): These are factors from a different risk model (sometimes used in product/business risk analysis), not the core FMEA formula.

Memory tip: Think of risk as a simple equation - Risk = Likelihood × Impact. If something is very likely but has no impact, or has huge impact but can never happen, it's not truly high-risk. FMEA forces you to weight both dimensions together before assigning a priority.

No community discussion yet for this question.