Static analysis tools as early indicators of pre-release defect density
By N. Nagappan, Thomas Ball. Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005., 2005
313 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/4e582bd1f4a175abc142ad005bae6bba6b3b53e8
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
- Romain Robbes
- Marco D'Ambros
- Michele Lanza
- Tim Menzies
- Burak Turhan
- Ayse Basar Bener
- Justin S. Di Stefano
- Laurie A. Williams
In Information Systems
- Romain Robbes
- Marco D'Ambros
- Michele Lanza
- Burak Turhan
- Ayse Basar Bener
- Tim Menzies
- Laurie A. Williams
- Justin S. Di Stefano
In Software
- Romain Robbes
- Marco D'Ambros
- Michele Lanza
- Burak Turhan
- Ayse Basar Bener
- Tim Menzies
- Laurie A. Williams
- Justin S. Di Stefano
Citations in the corpus
- Why don't software developers use static analysis tools to find bugs? (2013, background): “Software defects, or bugs, can cost companies significant amounts of money, especially when they lead to software failure [1], [2].”
- Predicting Vulnerable Software Components via Text Mining (2014, background): “Nagappan and Ball [23] reported similar correlations in the area of software defect prediction, i.e., defect density discovered via static analysis is related to pre-release defects determined by testing.”
- Improving the reliability of commodity operating systems (2005, background): “Microsoft, for example, runs static analysis tools regularly and forces developers to fix the bugs they find [154].”
- Evaluating defect prediction approaches: a benchmark and an extensive comparison (2011, methodology): “Many approaches have been proposed to tackle the problem, relying on diverse information, such as code metrics (e.g., lines of code, complexity) (Basili et al. 1996; Ohlsson and Alberg 1996 ;B riand et al.1999 ;E l Emam et al.2001; Subramanyam and Krishnan 2003 ;G yimothy et al.2005; Nagappan and B”
- On the relative value of cross-company and within-company data for defect prediction (2009, methodology): “The standard defect prediction task is different to standard SRE.”
- Data Mining Static Code Attributes to Learn Defect Predictors (2007, unknown): “Many researchers use static attributes to guide software quality predictions (see [1], [2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14], [15], [16], [17], [18], [19], [20]).”
- On the value of static analysis for fault detection in software (2006, methodology): “Static analysis defects were used to predict the prerelease defect density of Windows Server 2003 [31].”
- An extensive comparison of bug prediction approaches (2010, methodology): “Nagappan and Ball estimated the pre-release defect density of Windows Server 2003 with a static analysis tool [7].”