Quality metrics and measurement in Software Engineering - Step-by-Step Execution

Concept Flow - Quality metrics and measurement

Define Quality Goals

↓

Select Metrics to Measure

↓

Collect Data

↓

Analyze Metrics

↓

Make Decisions / Improvements

↓

Repeat Measurement Cycle

This flow shows how quality goals lead to selecting metrics, collecting data, analyzing results, and making improvements in a cycle.

Execution Sample

Software Engineering

Metric: Defect Density = Number of Defects / Size of Software
Collect defects found in testing
Calculate defect density
Analyze if defect density meets quality target

This example calculates defect density to measure software quality by counting defects per size unit.

Analysis Table

Step	Action	Data Collected	Calculation	Result/Decision
1	Define quality goal	Goal: Reduce defects	N/A	Focus on defect metrics
2	Select metric	Defect Density	Defect Density = Defects / KLOC	Metric chosen
3	Collect data	Defects found: 50, Size: 10 KLOC	N/A	Ready for calculation
4	Calculate metric	N/A	50 / 10 = 5 defects/KLOC	Defect density = 5
5	Analyze result	Defect density = 5	Compare to target < 3	Quality below target
6	Make decision	Quality below target	Plan improvements	Schedule code review and testing
7	Repeat cycle	After improvements	Measure again	Expect defect density to decrease

💡 Cycle repeats until quality goals are met or adjusted

State Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
Defects	0	50	50	50	50
Size (KLOC)	0	10	10	10	10
Defect Density	N/A	N/A	5	5	Expected to decrease

Key Insights - 3 Insights

Why do we calculate defect density instead of just counting defects?

Because defect density relates defects to software size, giving a fair quality measure regardless of project size, as shown in step 4 of the execution_table.

What happens if defect density is higher than the target?

The analysis step (step 5) shows quality is below target, so decisions are made to improve quality, like extra testing or code reviews (step 6).

Why repeat the measurement cycle?

Quality measurement is ongoing; after improvements, metrics are collected again to check progress, as shown in step 7.

Visual Quiz - 3 Questions

Look at the execution_table, what is the defect density calculated at step 4?

A 5 defects per KLOC

B 50 defects total

C 10 KLOC size

D 3 defects per KLOC

💡 Hint

Check the 'Calculation' and 'Result/Decision' columns at step 4 in the execution_table.

At which step does the team decide to plan improvements due to quality issues?

A Step 3

B Step 5

C Step 6

D Step 7

💡 Hint

Look for the step where 'Make decision' action is taken in the execution_table.

If the number of defects was 20 instead of 50, how would the defect density at step 4 change?

A It would stay the same

B It would decrease

C It would increase

D It would be zero

💡 Hint

Refer to the variable_tracker and formula in execution_sample: Defect Density = Defects / Size.

Concept Snapshot

Quality metrics measure software attributes to track quality.
Common metric: Defect Density = Defects / Size.
Measure data, analyze results, then improve.
Repeat cycle to ensure quality goals are met.
Metrics help make objective decisions.

Full Transcript

Quality metrics and measurement involve defining quality goals, selecting appropriate metrics like defect density, collecting data such as number of defects and software size, calculating the metric, analyzing if it meets targets, making improvement decisions, and repeating the cycle. This process helps teams objectively track and improve software quality over time.

Practice

1. What is the main purpose of quality metrics in software engineering?

easy

A. To manage project budgets

B. To write code faster

C. To measure and improve software quality

D. To design user interfaces

Solution

1. Step 1: Understand what quality metrics measure

   Quality metrics provide numbers that show how good or bad software quality is.

2. Step 2: Identify the main goal of using these metrics

   They help find problems and track improvements in software quality.

3. Final Answer:

   To measure and improve software quality -> Option C

4. Quick Check:

   Quality metrics = measure and improve quality [OK]

Hint: Quality metrics measure software quality, not speed or cost [OK]

Common Mistakes:

• Confusing quality metrics with project management tools
• Thinking metrics speed up coding directly
• Mixing quality metrics with design tasks

2. Which of the following is a correct example of a software quality metric?

easy

A. user interface color

B. number of developers

C. programming language used

D. defect density

Solution

1. Step 1: Identify what counts as a quality metric

   Quality metrics are measurable numbers related to software quality, like defects per size.

2. Step 2: Check each option

   Defect density counts defects per size, so it is a quality metric. Others are not numeric quality measures.

3. Final Answer:

   defect density -> Option D

4. Quick Check:

   Defect density = quality metric [OK]

Hint: Look for measurable numbers related to software quality [OK]

Common Mistakes:

• Choosing non-numeric attributes like color or language
• Confusing team size with quality metric
• Ignoring the need for measurement

3. Given a software module with 50 defects found in 10,000 lines of code, what is the defect density?

medium

A. 0.005 defects per line

B. 0.5 defects per line

C. 5 defects per line

D. 0.05 defects per line

Solution

1. Step 1: Understand defect density formula

   Defect density = Number of defects / Lines of code.

2. Step 2: Calculate defect density

   50 defects / 10,000 lines = 0.005 defects per line. This equals 0.005, which is 0.005 defects per line.

3. Final Answer:

   0.005 defects per line -> Option A

4. Quick Check:

   50 ÷ 10,000 = 0.005 [OK]

Hint: Divide defects by lines of code for defect density [OK]

Common Mistakes:

• Multiplying instead of dividing
• Mixing decimal places
• Confusing defect density with total defects

4. A team tracks test coverage but reports it as 150%. What is the likely error?

medium

A. Test coverage calculation is incorrect or data is wrong

B. Test coverage can exceed 100% if tests overlap

C. Test coverage is not a valid quality metric

D. Test coverage measures defects, not code tested

Solution

1. Step 1: Understand test coverage limits

   Test coverage measures percentage of code tested, max 100%.

2. Step 2: Analyze reported value

   150% is impossible, so calculation or data must be wrong.

3. Final Answer:

   Test coverage calculation is incorrect or data is wrong -> Option A

4. Quick Check:

   Test coverage ≤ 100% [OK]

Hint: Test coverage cannot be more than 100% [OK]

Common Mistakes:

• Believing coverage can exceed 100%
• Confusing coverage with defect count
• Ignoring data errors

5. A project has these metrics: defect density = 0.02, average repair time = 5 hours, test coverage = 80%. Which action best improves overall software quality?

hard

A. Ignore defect density and focus on coding speed

B. Increase test coverage to find more defects early

C. Reduce repair time without changing testing

D. Decrease test coverage to save time

Solution

1. Step 1: Understand the impact of each metric

   Higher test coverage helps find defects early, reducing defect density over time.

2. Step 2: Evaluate options for improving quality

   Increasing test coverage is the best way to improve quality by catching defects early.

3. Final Answer:

   Increase test coverage to find more defects early -> Option B

4. Quick Check:

   More test coverage = better defect detection [OK]

Hint: More test coverage usually improves quality by catching defects early [OK]

Common Mistakes:

• Focusing only on repair time
• Ignoring defect density
• Reducing test coverage to save time