Experimentation in software engineering: an introduction

By Claes Wohlin, Per Runeson, Martin Höst, Magnus C. Ohlsson, B. Regnell, Anders Wesslén. 2000

3,208 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/947b29eb3cde8ccb8df9342bb2384ec480ea3964

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

Citations in the corpus

A Controlled Experiment for Program Comprehension through Trace Visualization (2011, background): “[53] suggest the removal of outliers in case of extraordinary situations, such as external events that are unlikely to reoccur.”
On the Use of Mutation Faults in Empirical Assessments of Test Case Prioritization Techniques (2006, background): “Any controlled experiment is subject to threats to validity , and these must be considered in order to assess the meaning and impact of results (see [39] for a general discussion of va lidity evaluation and a threats classification).”
Scientific research ontology to support systematic review in software engineering (2007, background): “Some proposals to support the accomplishing of these studies can be found in the technical literature [5,7].”
Guidelines for conducting and reporting case study research in software engineering (2009, methodology): “There exist guidelines for experiments’ conduct (Kitchenham et al. 2002; Wohlin et al. 2000 ) and reporting (Jedlitschka and Pfahl 2005), measurements (Basili and Weiss 1984; Fenton and Pfleeger 1996; van Solingen and Berghout 1999), and systematic reviews (Kitchenham 2007), while only little is wr”
Is mutation an appropriate tool for testing experiments? [software testing] (2005, background): “More details will be presented in the next section as we report on the results.”
A Hitchhiker's guide to statistical tests for assessing randomized algorithms in software engineering (2014, background): “The re are also guidelines for running 70 experiment with human subjects in software engineering [120].”
A Systematic Review of the Application and Empirical Investigation of Search-Based Test Case Generation (2010, methodology): “Empirical studies are usually divided into three different types: surveys, case studies, or experiments [52].”
The Future of Empirical Methods in Software Engineering Research (2007, background): “Experiments are conducted when the investigator wants control over the situation, with direct, precise, and systematic manipulation of the behavior of the phenomenon to be studied [133].”
A systematic review of search-based testing for non-functional system properties (2009, neutral): “Internal validity refers to a causal relationship between treatment and outcome [63].”
An Empirical Study of the Impact of Two Antipatterns, Blob and Spaghetti Code, on Program Comprehension (2011, background): “We take care of the groups to ensure their homogeneity and avoid bias in the results, for example we ensure that no group entirely contains male or female subjects.”
Supporting Controlled Experimentation with Testing Techniques: An Infrastructure and its Potential Impact (2005, methodology): “When performing a replication, researchers duplicate the experimental design of an experiment on a different sample to increase the confidence in the findings [47] or on an extended hypothesis to evaluate additional variables [5].”
Using Students as Subjects—A Comparative Study of Students and Professionals in Lead-Time Impact Assessment (2000, background): “Often, four different types of validity are discussed (Cook and Campbell 1979, and Wohlin et al., 2000): internal, external, construct, and conclusion.”