Inferencing into the void: problems with implicit populations Comments on `Empirical software engineering experts on the use of students and professionals in experiments'
arXiv:1810.07392 · doi:10.1007/s10664-018-9655-0
Abstract
I welcome the contribution from Falessi et al. [1] hereafter referred to as F++ , and the ensuing debate. Experimentation is an important tool within empirical software engineering, so how we select participants is clearly a relevant question. Moreover as F++ point out, the question is considerably more nuanced than the simple dichotomy it might appear to be at first sight. This commentary is structured as follows. In Section 2 I briefly summarise the arguments of F++ and comment on their approach. Next, in Section 3, I take a step back to consider the nature of representativeness in inferential arguments and the need for careful definition. Then I give three examples of using different types of participant to consider impact. I conclude by arguing, largely in agreement with F++, that the question of whether student participants are representative or not depends on the target population. However, we need to give careful consideration to defining that population and, in particular, not to overlook the representativeness of tasks and environment. This is facilitated by explicit description of the target populations.
arXiv commentThis is a commentary on the article in Empirical Software Engineering entitled `Empirical software engineering experts on the use of students and professionals in experiments' by Falessi et al. It will form part of an accepted an article for EMSE (Dec 2018) comprising commentary and a response from the original authors
References in corpus (1)
Cited by in corpus (11)
- Evolution of statistical analysis in empirical software engineering research: Current state and steps forward
- 40 Years of Designing Code Comprehension Experiments: A Systematic Mapping Study
- The Mind Is a Powerful Place: How Showing Code Comprehensibility Metrics Influences Code Understanding
- Crowdsmelling: The use of collective knowledge in code smells detection
- Why Research on Test-Driven Development is Inconclusive?
- Unveiling process insights from refactoring practices
- Towards a Methodology for Participant Selection in Software Engineering Experiments. A Vision of the Future
- Evidence Tetris in the Pixelated World of Validity Threats
- Anchoring Code Understandability Evaluations Through Task Descriptions
- Automating App Review Response Generation
- Empirical Assessment of the Code Comprehension Effort Needed to Attack Programs Protected with Obfuscation