Austen Rainer
ABSTRACT
In this paper, we review four examples in software engineering practice of the lack of use of empirical evidence. We use these examples to support our claims that practitioners and researchers appear to have different values with regards to empirical evidence, and appear to use different criteria when evaluating the credibility of evidence. From our examples, it seems that practitioners need to be persuaded to adopt evidence-based software engineering practices. Consequently, the research community needs to consider strategies for persuading practitioners. Paradoxically for software engineering research, the more effective persuasion strategies may be ones that, initially at least, do not rely on empirical evidence.
- Basili, V. R. and Rombach, H. D. The TAME Project: Towards Improvement-Oriented Software Environments. IEEE Transactions on Software Engineering, 14 (6). 758--773, 1988.Google Scholar
Digital Library
- Bhattacherjee, A. and Sanford, C. Persuasion strategies for information technology usage: an elaboration likelihood model. MIS Quarterly, In review. Google ScholarDigital Library
- DTI, DTI's Office of Science and Technology's Public Engagement with Science and Technology, Department of Trade and Industry (DTI), http://www.dti.gov.uk/ost/ostbusiness/puset/puset.htm, 18th February 2005, 2005Google Scholar
- Dybå, T., Kitchenham, B. and Jorgensen Evidence-Based Software Engineering for Practitioners. IEEE Software, 22 (1). 58--65, 2005. Google ScholarDigital Library
- Fenton, N. and Ohlsson, N. Quantitative Analysis of Faults and Failures in a Complex Software System. IEEE Transactions on Software Engineering, 26 (8). 797--814, 2000. Google ScholarDigital Library
- Fisher, A. The Logic of Real Arguments. Cambridge University Press, 1988.Google Scholar
- Kitchenham, B., Pfleeger, S. L., Pickard, L., Jones, P., Hoaglin, D. C. and Rosenberg, J. Preliminary guidelines for empirical research in software engineering. IEEE Transactions on Software Engineering, 28 (8). 721--734, 2002. Google ScholarDigital Library
- McCroskey, J. C. An introduction to rhetorical communication. Allyn and Bacon, Boston, 1997.Google Scholar
- Paulk, M. C., Curtis, B., Chrissis, M. B. and Weber, C. V. Capability Maturity Model, Version 1.1. IEEE Software, 10 (4). 18--27, 1993. Google ScholarDigital Library
- Paulk, M. C., Goldenson, D. and White, D. M. The 1999 Survey of High Maturity Organizations, Software Engineering Institute, Carnegie Mellon University, 2000.Google Scholar
- Perloff The dynamics of persuasion: Communication and attitudes in the 21st Century. Lawrence Erlbaum Associates, Mahwah, N.J., 2003.Google Scholar
- Petty, R. E. and Cacioppo, J. T. The elaboration liklehood model of persuasion. Advances in experimental social psychology, 19, 1986.Google Scholar
- Petty, R. E., Cacioppo, J. T., Strathman, A. J. and Priester, J. R. To think or not to think: exploring two routes to persuasion. In Shavitt, S. and Brock, T. C. eds. Persuasion: psychological insight and perspectives, 1994.Google Scholar
- Petty, R. E. and Wegener, D. T. The elaboration liklihood model: current status and controversies. In Chaiken, S. and Trope, Y. eds. Dua-process theories in social psychology, The Guildford Press, New York, 1999, 41--72.Google Scholar
- Rainer, A. and Hall, T., Identifying the causes of poor progress in software projects. In 10th International Symposium on Software Metrics (METRICS'04), (2004). Google ScholarDigital Library
- Rainer, A. W. An Empirical Investigation of Software Schedule Behaviour. PhD Thesis, Department of Computing, Bournemouth UniversityGoogle Scholar
- Rainer, A. W., Hall, T. and Baddoo, N., Persuading developers to 'buy into' software process improvement: an exploratory analysis. In ACM-IEEE International Symposium on Empirical Software Engineering (ISESE), (University of Rome 'Tor Vergata', Italy, September 30th - October 1st 2003, 2003). Google ScholarDigital Library
- Rogers, E. M. Diffusion of innovations. Free Press, New York, 1995.Google Scholar
- Williams, L. On the need for a process for making reliable quality comparisons with industrial data. ACM SIGSOFT Software Engineering Notes, 29 (5), 2004. Google ScholarDigital Library
Index Terms
- Software engineering practice versus evidence-based software engineering research
Recommendations
Software engineering practice versus evidence-based software engineering research
In this paper, we review four examples in software engineering practice of the lack of use of empirical evidence. We use these examples to support our claims that practitioners and researchers appear to have different values with regards to empirical ...
Evidence-Based Software Engineering for Practitioners
Software engineers might make incorrect decisions about adopting new techniques if they donýt consider scientific evidence about the techniquesý efficacy. Procedures used for evidence-based medicine can also apply to software engineering. Such evidence-...
Software engineering research versus software development
Engineering research differs greatly, both in its aims and in its methods, from traditional "scientific" research. While Sciences deal with the study of existing objects and phenomena, be it physically, metaphysically or conceptually, Engineering is ...
Comments