| 
|
QuoteRef: eickSG1_2001
topics >
all references >
ThesaHelp:
references e-f
Topic:
software change management
Topic:
the effect of scale
Topic:
software metrics
Group:
software maintenance
Topic:
identifying program modules
Topic:
sensitivity of software to change
Topic:
program module as encapsulation
Topic:
change
Topic:
bugs
Reference
Eick, S.G., Graves, T.L., Karr, A.F., Marron, J.S., Mockus, A., "Does code decay? Assessing the evidence from change management data", IEEE Transactions on Software Engineering, 27, 1, January 2001, pp. 1-12. Google
1 ;;Quote: study of 15-year change management history of telephone switch software; 100 million lines organized into 5000 directories by 10,000 developers
6 ;;Quote: code size is effectively synonymous with complexity; high correlation between complexity metrics and NCSL (non-comment and non-header source lines)
7 ;;Quote: in 1989, less than 2% of changes touched multiple files; by 1996, over 5% touched multiple files
9 ;;Quote: modularity decays; in 1989, the change history clearly separated two clusters of modules; by 1996, these clusters had broken down
10 ;;Quote: change is the primary agent of faults; large, recent changes are the most likely to fail; frequency of change is a better predictor of faults than size of module or number of developers
10 ;;Quote: while not serious, the number of files touched by a change is a symptom of error-proneness
ThesaHelp: references e-f (168 items)
Topic: software change management (48 items)
Topic: the effect of scale (15 items)
Topic: software metrics (32 items)
Group: software maintenance (14 topics, 355 quotes)
Topic: identifying program modules (26 items)
Topic: sensitivity of software to change (44 items)
Topic: program module as encapsulation (28 items)
Topic: change (28 items)
Topic: bugs (65 items)