Slide 24
Slide 24 text
24 BUILD SOFTWARE TO TEST SOFTWARE
Example 1. Software Defect Prediction
Size: 10 885 modules, 22 attributes
● 5 different lines of code measure
● 3 McCabe metrics (cyclomatic, essential, design complexity)
● 4 base Halstead measures (volume, length, difficulty, intelligence)
● 8 derived Halstead measures, a branch-count
● 1 goal field (module has/has not one or more reported defects)
Hypotheses:
● code with complicated pathways are more error-prone
● code that is hard to read is more likely to be fault prone
● static measures can never be a certain indicator of the presence of a fault
https://www.kaggle.com/datasets/semustafacevik/software-defect-prediction