What is the MAIN objective when reviewing a software deliverable?

Question

Options

• ATo identify potential application failures by use of a test specification.
• BTo identify defects in any software work product.
• CTo identify spelling mistakes in a requirements specification.
• DTo identify standards inconsistencies in the code.

• A
  10% (4)
• B
  82% (32)
• C
  3% (1)
• D
  5% (2)

Explanation

Reviewing a software deliverable is a static testing technique whose primary purpose is to find defects in any work product - requirements, design documents, code, test plans, or any other artifact - without executing the software, making B the correct and broadest answer.

• A is wrong because using a test specification to find application failures describes dynamic testing (actually running the software), not a review.
• C is wrong because catching spelling mistakes is a valid but narrow byproduct of reviewing requirements, not the main objective.
• D is wrong because checking standards compliance in code is one specific purpose of a code inspection, not the overarching goal of all reviews.

Memory tip: Think of reviews as a "defect net" cast over any document at any stage - the net's job is always to catch defects. The other options each describe only one thread of that net.

No community discussion yet for this question.