Evidence-based software engineering

By Barbara A. Kitchenham, Tore Dybå, Magne Jørgensen. Proceedings. 26th International Conference on Software Engineering, 2004

992 citations recorded by the source corpus.

Subfields: Health Information Management, Information Systems and Management, Statistics and Probability

View Paper: https://www.semanticscholar.org/paper/c9382574e6a868fe45aa9cc09d19c0f5fadbd652

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Health Information Management

In Information Systems and Management

In Statistics and Probability

Citations in the corpus

Software development in startup companies: A systematic mapping study (2014, background): “The prospects of evidence-based software engineering [39] have motivated researchers to conduct systematic literature reviews and mapping studies.”
Guidelines for snowballing in systematic literature studies and a replication in software engineering (2014, background): “Based on the original EBSE ideas [1], research related to systematic literature studies has subsequently evolved.”
Reporting Experiments in Software Engineering (2008, background): “…results from controlled experiments is expected to support a systematic, standardized presentation of empirical research, thus improving reporting in order to support readers in (1) finding the information they are looking for, (2) understanding how an experiment is conducted, and (3) assessing…”
Guidelines for including the grey literature and conducting multivocal literature reviews in software engineering (2017, methodology): “Systematic Literature Reviews (SLR) and Systematic Mapping (SM)1 studies were adopted from medical sciences in mid2000’s [1], and since then numerous SLRs studies have been published in software engineering [2, 3].”
Reporting guidelines for controlled experiments in software engineering (2005, methodology): “The evidence-based software engineering (EBSE) paradigm [ 2 ] promises to solve parts of these issues by providing a framework for goal-oriented research, leading to a common body of knowledge (BoK) and, based on that, comprehensive problem-oriented decision support regarding SE technology selection”
Systematic Mapping Studies in Software Engineering (2008, background): “However, a general trend toward more evidence based software engineering (Kitchenham et al. 2004) has lead to an increased focus on new, empirical and systematic research methods.”
Performing systematic literature reviews in software engineering (2006, background): “Firstly, as a means of obtaining an objective summary of research evidence concerning a topic or phenomenon [6].”
Using mapping studies as the basis for further research - A participant-observer case study (2011, background): “…three papers suggesting that the concept of evidence-based practice, (as initially developed in medicine, and subsequently adopted by many different disciplines including economics, psychology, social science and most health care disciplines) should be adopted in software engineering [1] [2] [3].”
Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices (2017, methodology): “EBSE Technical Report Ver.”
A Systematic Review of the Application and Empirical Investigation of Search-Based Test Case Generation (2010, background): “[19], [31] make the case for evidence-based software engineering that seeks to help practitioners make informed decisions related to software development and maintenance by integrating current best evidence from research with practical experience.”
Evidence-Based Software Engineering for Practitioners (2005, background): “The aim of EBSE is to provide the means by which current best evidence from research can be integrated with practical experience and human values in the decision making process regarding the development and maintenance of software (Kitchenham et al., 2004).”
Systematic literature reviews in software engineering - A tertiary study (2010, methodology): “Whether the study positioned itself explicitly as an EBSE study by citing any of the EBSE papers [2,1] or the SLR guidelines [7,8].”
Lessons from applying the systematic literature review process within the software engineering domain (2007, positive): “The possibility of applying the evidence-based paradigm to the software engineering field was raised, discussed and enthusiastically supported at ICSE 2004 (Kitchenham et al., 2004).”
Systematic literature reviews in software engineering - A systematic literature review (2009, methodology): “Thus, although we would not expect papers published in 2004 to have been directly influenced by the EBSE papers [23,5] or the guidelines for systematic reviews [22], we thought it was important to have some idea of the extent of systematic approaches to literature reviews before the guidelines were ”
A Map of Threats to Validity of Systematic Literature Reviews in Software Engineering (2016, methodology): “We used Google Scholar to check the papers with reference to the three EBSE seminal papers [1][13][14] and two versions of the guidelines on SLRs in SE [2][12].”
Recommended Steps for Thematic Synthesis in Software Engineering (2011, methodology): “After the initial reading of the papers, reviewers can also update the systematic review protocol, which among other things contains the data extraction strategy and synthesis strategy [33][34].”
Systematic literature studies: Database searches vs. backward snowballing (2012, background): “[7] introduced the concept of evidence-based software engineering (EBSE).”