Which techniques are used for performing reviews?

Question

Options

• AInspection, formal walkthrough, desk check
• BMind mapping, decision analysis, interviews
• CBrainstorming, functional decomposition, lessons learned
• DSWOT analysis, workshop, cost analysis

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

Explanation

Option A is correct because Inspection, formal walkthrough, and desk check are all established software review techniques used to examine work products (code, documents, designs) for defects without executing them - these are classic static testing/review methods recognized in standards like IEEE and ISTQB.

Why the distractors are wrong:

• B (Mind mapping, decision analysis, interviews) - these are elicitation and analysis techniques used in requirements gathering, not review techniques.
• C (Brainstorming, functional decomposition, lessons learned) - brainstorming and lessons learned are retrospective/ideation techniques; functional decomposition is an analysis approach, not a review type.
• D (SWOT analysis, workshop, cost analysis) - these are business/planning techniques; while workshops can support reviews, they aren't review techniques themselves.

Memory tip: Think of reviews as something you do alone or in a group, reading a document - a desk check is solo, a walkthrough is author-led with a group, and an inspection is the most formal/structured of the three. If the technique sounds like "thinking up ideas" or "analyzing business value," it's not a review technique.

No community discussion yet for this question.