1. Predicting Faults Using
the Complexity of Code Changes
Every Battle is Won Before It is Fought
Julian Mason - China 12.04.11
S. LaokokP. Chongpakdee N. Uaphoemkiat
2. Published in: IEEE 31st International Conference on
Software Engineering, 2009 ICSE
Date: 16 ~ 24 May 2009
DOI: 10.1109/ICSE.2009.5070510
Cited by: 77* Citations,
IEEE Publication ~ 72
Other publication ~ 4
Patent ~ 1
Ahmed E. Hassan
Queen’s University
Retrieved at 21 Feb. 2016 at http://ieeexplore.ieee.org/xpl/abstractCitations.jsp?arnumber=5070510
3. If you know the enemy and know yourself, you
need not fear the result of a hundred battles. If
you know yourself but not the enemy, for every
victory gained you will also suffer a defeat. If you
know neither the enemy nor yourself, you will
succumb in every battle
—Sun Tzu, The Art of War
49. • Modifications Vs Faults
• Modifications Vs Entropy
• Faults Vs. Entropy
50. Application name Application Type Start Date
Subsystem Count
(low level directories)
Prog. Lang.
NetBSD OS March 1993 235 C
FreeBSD OS June 1993 152 C
OpenBSD OS Oct 1995 265 C
Postgres DBMS July 1996 280 C
KDE
Windowing
System
April 1997 108 C++
KOffice
Productivity
Suite
April 1998 158 C++
51. y = 0 + 1x
Statistical Linear Regression
(SLR Model)dependent
independent