Quality metrics and measurement in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Defect Density

What does the metric defect density measure in software quality?

A The total number of defects found during the entire project lifecycle

B The number of defects found per size of the software, such as per thousand lines of code

C The average time taken to fix a defect after it is reported

D The percentage of test cases passed during testing

💡 Hint

Think about how defects relate to the size of the software.

Defect density measures how many defects exist relative to the size of the software, often per thousand lines of code. It helps compare quality across projects of different sizes.

📋 Factual

intermediate

Purpose of Code Coverage Metric

Which of the following best describes what the code coverage metric measures?

A The percentage of code executed during testing

B The number of defects found in the code

C The time taken to write the code

D The number of lines of code written by each developer

💡 Hint

Think about what testing aims to do with the code.

Code coverage measures how much of the code is actually run when tests are executed. Higher coverage means more code has been tested.

🔍 Analysis

advanced

Interpreting Mean Time to Failure (MTTF)

A software system has a Mean Time to Failure (MTTF) of 500 hours. What does this indicate about the system?

A The system is guaranteed to fail exactly every 500 hours

B The system takes 500 hours to recover after a failure

C The system has 500 known defects

D On average, the system operates for 500 hours before experiencing a failure

💡 Hint

Consider what 'mean time to failure' means in terms of operation time.

MTTF is the average time the system runs before a failure occurs. It does not guarantee exact failure times but gives an average expectation.

❓ Comparison

advanced

Difference Between Reliability and Availability

Which statement correctly distinguishes reliability from availability in software quality metrics?

A Reliability and availability are the same and can be used interchangeably

B Reliability measures user satisfaction, while availability measures code complexity

C Reliability measures how often software fails, while availability measures the proportion of time software is operational and accessible

D Reliability measures the number of defects, while availability measures the number of test cases

💡 Hint

Think about uptime versus failure frequency.

Reliability focuses on how often failures occur, while availability focuses on the time the system is ready for use, including downtime and repair time.

❓ Reasoning

expert

Choosing the Best Metric for Early Defect Detection

You want to measure how effective your testing process is at finding defects early in the development cycle. Which metric would best help you assess this?

A Defect Removal Efficiency (DRE)

B Code Complexity

C Mean Time to Repair (MTTR)

D Customer Satisfaction Score

💡 Hint

Consider a metric that compares defects found before release to total defects.

Defect Removal Efficiency measures the percentage of defects found and fixed before the software is released, indicating early defect detection effectiveness.