Empirical studies of software engineering: a roadmap

By Dewayne E. Perry, Adam A. Porter, L. Votta. International Conference on Software Engineering, 2000

465 citations recorded by the source corpus.

In this article we summarize the strengths and weaknesses of empirical research in software engineering. We argue that in order to improve the current situation we must create better studies and draw more credible interpretations from them. We finally present a roadmap for this improvement, which includes a general structure for software empirical studies and concrete steps for achieving these goals: designing better studies, collecting data more effectively, and involving others in our empirical enterprises.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/b2f8ea4b7195153124c9c099c45cb1e9054674ea

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

Citations in the corpus

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review (2012, unknown): “Description Remedy”
The Future of Empirical Methods in Software Engineering Research (2007, background): “Since then, there has been an increased focus on the need for, and approaches to, applying empirical methods in SE research [10, 11, 101, 113, 129, 130, 136].”
Software defect prediction using Bayesian networks (2012, methodology): “We briefly explain the methodology we follow to alleviate these threats (Perry et al. 2000).”
Fair and balanced?: bias in bug-fix datasets (2009, unknown): “Perry et al. [40] echo the sentiment and outline concrete steps that can be taken to overcome the biggest challenge facing empirical researchers: defining and executing studies that change how software development is done.”