ISEB-SWTINT1 practice question 8 of 10

What is the MAIN objective when reviewing a software deliverable?

Full set: 43 questions
Answer options
A: To identify potential application failures by use of a test specification.
B: To identify defects in any software work product. Correct answer
C: To identify spelling mistakes in a requirements specification.
D: To identify standards inconsistencies in the code.
Correct Answer:
B. To identify defects in any software work product.
Explanation

The main objective of a review, as a primary static testing activity, is to find defects in any software work product. This process is applied to various deliverables throughout the software development lifecycle, such as requirements specifications, design documents, code, and test plans. By examining these documents before dynamic testing, reviews help in the early detection and removal of errors, omissions, and ambiguities. This proactive approach improves the overall quality of the final product and reduces the cost of fixing defects, which is the central goal of the review process.

Why Incorrect

A. This describes dynamic testing, which involves executing the software to find failures, not the static examination of a deliverable.
C. While spelling mistakes are defects, this is too specific. The main objective is to find all types of defects, including major logical or functional errors.
D. This is a valid objective for a code review specifically, but not the main objective for reviewing any software deliverable, such as a requirements document.

References

1. ISTQB® Certified Tester Foundation Level Syllabus (Version 2018 V3.1): Section 3.2.2, "Benefits of Reviews," states, "The main purpose of reviews is to find defects." It further clarifies that reviews contribute to "early defect detection and correction" and can be applied to any work product.

2. Black, R., van Veenendaal, E., & Greaves, D. (2019). Foundations of Software Testing: ISTQB Certification (4th ed.). Cengage Learning. Chapter 3, Section "Objectives of the review process," explicitly lists "finding defects" as the primary objective of any formal review.

3. Pressman, R. S., & Maxim, B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill. In Chapter 17, "Review Techniques," the text states, "The primary objective [of a formal technical review] is to find errors during the process so that they do not become defects after release of the software." This applies to any work product being reviewed.

Scroll to Top