The papers on this list are available online, but I downloaded them to the course website for the use of students in this course only. GMU students can access many papers from off-campus through the university's digital subscriptions.

I. Empirical Methods Overview

1. Per Runeson and Martin Höst, “Guidelines for conducting and reporting case study research in software engineering,” Empirical Software Engineering, 14(2):131-164, April 2009. local copy
2. Steve Easterbrook, Janice Singer, Margaret-Anne Storey, and Daniela Damian, “Selecting Empirical Methods for Software Engineering Research,” Guide to advanced empirical software engineering, 2008. local copy
3. Ko, LaToza, and Burnett, “A practical guide to controlled experiments of software engineering tools with human participants,” Empirical Software Engineering, 20(1), February 2015. Springer
4. Forrest Shull, Manoel G. Mendoncça, Victor Basili, Carver, Jose Maldonado, Sandra Fabbri, Guilherme Horta Travassos, and Maria Cristinia Ferreira, “Knowledge-Sharing Issues in Experimental Software Engineering,” Empirical Software Engineering, 9(1-2):111-137, March 2004. local copy
5. Stephen M. Blackburn, Amer Diwan, Matthias Hauswirth, Peter F. Sweeney, José Nelson Amaral, Tim Brecht, Lubomír Bulej, Cliff Click, Lieven Eeckhout, Sebastian Fischmeister, Daniel Frampton, Laurie J. Hendren, Michael Hind, Antony L. Hosking, Richard E. Jones, Tomas Kalibera, Nathan Keynes, Nathaniel Nystrom, and Andreas Zeller, “The Truth, The Whole Truth, and Nothing But the Truth: A Pragmatic Guide to Assessing Empirical Evaluations,” Journal ACM Transactions on Programming Languages and Systems (TOPLAS), 38(4) October 2016. ACM
6. Forrest Shull, Jeffrey Carver, Sira Vegas, and Natalia Juristo, “The role of replications in Empirical Software Engineering,” Empirical Software Engineering, 13(2):211-218, April 2008. local copy

II. Reviewing & Dissemination

1. Walter F. Tichy, “Hints for Reviewing Empirical Work in Software Engineering,” Empirical Software Engineering, 5(4):309-312, December 2000. local copy
2. Jeff Offutt, “Editorial: Standards for reviewing papers,” Journal of Software Testing, Verification, and Reliability, 17(3):135-136, September 2007. local copy
3. Jeff Offutt, “Editorial: Plagiarism Is For Losers,” Journal of Software Testing, Verification, and Reliability, 25(1), January 2015. local copy
4. Jeff Offutt, “Editorial: Who Is An Author?,” Journal of Software Testing, Verification, and Reliability, 25(2), January 2015. local copy

How science really works: Interesting website

III. Technical Papers

Week 4. Metrics & maintainability

1. Mikhail Perepletchikov and Caspar Ryan, “A controlled experiment for evaluating the impact of coupling on the maintainability of service-oriented software,” IEEE Transactions on Software Engineering, 37(4):449-465, (2011). local copy
2. Richard J. Miara, Joyce A. Musselman, Juan A. Navarro, and Ben Shneiderman, “Program Indentation and Comprehensibility,” Communications of the ACM, 26(11):861-867, November 1983. local copy

   Week 5. Project

   Week 6. Automatic program repair & Machine learning

3. Yi, Tan, Mechtaev, Bohme, and Roychoudhury, “A correlation study between automated program repair and test-suite metrics,” Empirical Software Engineering, October 2018, 23(5). Springer
4. Srivastava, Greff, and Schmidhuber, “Training Very Deep Networks,” Neural Information Processing Systems (NIPS) conference, 2015. NIPS

   Week 7. Test automation

5. Karhu, Repo, Taipale, and Smolander, Empirical Observations on Software Testing Automation, 2nd International Conference on Software Testing, 2009. IEEE
6. Wiklund, Eldh, Sundmark, and Lundqvist, “Impediments for software test automation: A systematic literature review,” Software Testing, Verification, and Reliability, 27(8), December 2017. local copy

   Week 8. Project

   Week 9. Test generation

7. Jeff Offutt and Chandra Alluri, “An industrial study of applying input space partitioning to test financial calculation engines,” Empirical Software Engineering, June 2014, 19(3):558-581. local copy
8. Mats Grindal, Birgitta Lindstrom, Jeff Offutt, and Sten F. Andler, “An Evaluation of Combination Strategies for Test Case Selection,” Empirical Software Engineering, 11(4):583-611, December 2006. local copy

   Week 10. Mutation

9. Rene Just and Franz Schweiggert, “Higher Accuracy and Lower Run Time: Effcient Mutation Analysis Using Non-Redundant Mutation Operators,” Journal of Software Testing, Verification, and Reliability, Published online December 2014. local copy
10. Paul Ammann, Marcio E. Delamaro, and Jeff Offutt, “Establishing Theoretical Minimal Sets of Mutants,” 7th IEEE International Conference on Software Testing, Verification, and Validation (ICST 2014), March 2014, Cleveland Ohio, USA. local copy

    Week 11. Cloud computing

11. Anton Beloglazov, Jemal Abawajyb, and Rajkumar Buyyaa, “Energy-aware resource allocation heuristics for efficient management of data centers for Cloud computing,” Future Generation Computer Systems, 28 (2012) 755-768. local copy
12. Ismail Ari and Nitel Muhtaroglu, “Design and implementation of a cloud computing service for finite element analysis,” Advances in Engineering Software, 60-61:122-135, 2013. local copy

    Week 12. Process

13. Hans-Christian Estler, Martin Nordio, Carlo A. Furia, Bertrand Meyer, and Johannes Schneider, “Agile vs. Structured Distributed Software Development: A Case Study,” IEEE Seventh International Conference on Global Software Engineering (ICGSE), August 2012, pages 11-20. (Also Empirical Software Engineering, October 2014, 19(5):1197-1224.) local copy
14. Oscar Dieste, Natalia Juristo, and Mauro Danilo Martinc, “Software Industry Experiments: A Systematic Literature Review,” IEEE 1st International Workshop on Conducting Empirical Studies in Industry (CESI), 2013. local copy