Software Development and Project Management

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?

  1. AThe defect density is within the guideline, so quality is judged to be as planned
  2. BThe defect density is 1.2 per KLOC, below the guideline, so rather than assuming the quality is good, check whether testing was insufficient (missing test cases)
  3. CThe defect density is 1.2 per KLOC, below the guideline, so the quality is judged to be excellent and the remaining tests are skipped
Show answer and explanation

Answer: B. The defect density is 1.2 per KLOC, below the guideline, so rather than assuming the quality is good, check whether testing was insufficient (missing test cases)

The defect density is 30 defects ÷ 25 KLOC = 1.2 per KLOC, below the guideline of 2 to 4. When it is below the guideline, the code may indeed be well made, but defects may also have been missed because testing was insufficient, for example because the test cases do not cover the specification well enough or the test viewpoints are biased. Therefore the result is evaluated after analyzing the test coverage and the nature of the defects. When the density is above the guideline, the quality of the design and implementation is examined.

  • A. At 1.2 per KLOC, it is outside the guideline of 2 to 4.
  • B. Correct. When the density is below the guideline, insufficient testing is suspected and checked.
  • C. The low count may be due to insufficient testing, so skipping tests without checking is dangerous.
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 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?
  2. 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?
  3. 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?
  4. 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?
  5. In an arrow diagram with nodes ① to ⑥, the activities, written as 'name: start node → end node, duration', are A: ① → ②, 6 days; B: ① → ③, 4 days; C: ② → ④, 4 days; D: ③ → ⑤, 4 days; E: ④ → ⑥, 2 days; F: ⑤ → ⑥, 3 days; and a dummy activity: ② → ③ (duration 0). What is the shortest duration of the whole project?