A survey of controlled experiments in software engineering

By Dag I.K. Sjøberg, Jo Erskine Hannay, Ove Hansen, Vigdis By Kampenes, Amela Karahasanovic, Nils-Kristian Liborg, Anette C. Rekdal. IEEE Transactions on Software Engineering, 2005

759 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/30e741a0330cdcaf6a6466eaca2f09c8bd604b57

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

Empirical studies of agile software development: A systematic review (2008, neutral): “[59].”
Using mapping studies as the basis for further research - A participant-observer case study (2011, background): “[17,18]), or only searching papers published in specific years (e.”
Systematic literature reviews in software engineering - A systematic literature review (2009, background): “A database of cost estimation papers from over 70 journals [16] has been the basis of many of the detailed cost estimation studies authored or co-authored by Jørgensen and the database of 103 software experiments [36] has allowed researchers to assess a number of specific research trends in software”
Security Developer Studies with GitHub Users: Exploring a Convenience Sample (2017, background): “Sjoeberg et al. [29] systematically analyze a decade’s worth of studies performed in Empirical Software Engineering, ﬁnding that eighty-seven percent of all subjects were students and nine percent were professionals.”
A systematic review of statistical power in software engineering experiments (2006, methodology): “Regarding the selection of articles, the main study utilized a multistage process involving several researchers who documented the reasons for inclusion/ exclusion as suggested in [19] (see [40]).”
Scientific research ontology to support systematic review in software engineering (2007, background): “Sjøberg et al. [1] describe the increase of investigation based on experimentation in this area of research.”
Guidelines for conducting and reporting case study research in software engineering (2009, methodology): “This is worth a study on its own, similar to the systematic review on experiments by Sjøberg et al. (2005).”
Experimentation in Software Engineering (2012, background): “However, in practice, many cases are selected based on availability [22], which is similar for experiments [161].”
Systematic Mapping Studies in Software Engineering (2008, methodology): “Therefore, one review study (Sjøberg et al. 2005) applied the classification scheme proposed by Glass et al (Glass et al.”
The Future of Empirical Methods in Software Engineering Research (2007, methodology): “SE experiments are typically used to explore relationships among data points describing one variable or across multiple variables, to evaluate the accuracy of models, or to validate measures [123].”
The New C Standard (Excerpted material) An Economic and Cultural Commentary (2008, neutral): “[361] A study[416] of 5,453 papers published in software engineering journals between 1993 and 2002 found that only 1.”
Reporting Experiments in Software Engineering (2008, background): “It is often difficult to find relevant information because the same type of information is located in different sections of study reports and important information is also often missing (Wohlin et al., 2003; Sjoberg et al., 2005; Dyba et al., 2006; Kampenes et al., 2007).”