Software Development and Project Management

During testing, a reliability growth curve was plotted with the test time (or the number of test cases executed) on the horizontal axis and the cumulative number of defects found on the vertical axis. The curve is still rising, with no sign of saturating (leveling off). Which judgment is most appropriate?

  1. ADefects are being found steadily and testing is efficient, so testing can end as scheduled
  2. BThe shape of the curve has nothing to do with quality, so testing ends once all planned test cases have been executed
  3. CMany undiscovered defects are probably still present, so testing should continue and the defect trends should also be analyzed
Show answer and explanation

Answer: C. Many undiscovered defects are probably still present, so testing should continue and the defect trends should also be analyzed

As testing progresses, defects are found one after another at first, and fewer are found as the remaining ones decrease, so the cumulative curve becomes S-shaped (approximated by a Gompertz or logistic curve) and eventually saturates. A curve approaching saturation is a sign that quality is stabilizing, but while it keeps rising, many defects are probably still present. Having executed the planned test cases is not, by itself, a reason to end testing. The curve is fitted to estimate the number of remaining defects, which is used to add or focus tests.

  • A. Defects still being found shows that many remain, which is no reason to end testing.
  • B. How close the curve is to saturating is an important indicator of whether quality is stabilizing.
  • C. Correct. While the curve has not saturated, many defects are assumed to remain, so testing continues.
Practice this topic Back to topic

Related calculators

Books on Software Development and Project Management Ad

As an Amazon Associate I earn from qualifying purchases.

More Software Development and Project Management questions

  1. In the integration testing of firmware with 25 KLOC (25,000 lines), 30 defects were found. Based on the organization's past results, the guideline for defects found in this phase is 2 to 4 per KLOC. Which is the most appropriate evaluation of this result?
  2. In Git, two developers changed the same line of the same file on different branches, and one branch was then merged into the other. Which describes what happens?
  3. Which method of reviewing design documents or source code is led by a moderator, assigns roles to the participants, is carried out formally using checklists and the like, and records the defects found and confirms their correction?
  4. After a firmware version known to work correctly there are 1,000 commits, and the latest commit has a bug. The bug was introduced by one commit and occurs in every commit after it. When the culprit commit is identified by binary search, as with git bisect, what is the maximum number of times the firmware must be built and tested?
  5. In a WBS, which breaks down a project's deliverables and work hierarchically, what is the element at the lowest level, used as the unit for estimating duration and cost and assigning people?