Evidence-Based Software Engineering for Practitioners

By Tore Dybå, Barbara A. Kitchenham, Magne Jørgensen. IEEE Software, 2005

519 citations recorded by the source corpus.

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

View Paper: https://www.semanticscholar.org/paper/40f08c6412a287e6708496d8ae1a10c2f9e72a21

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 Information Systems and Management

In Statistics and Probability

Citations in the corpus

Research synthesis in software engineering: A tertiary study (2011, methodology): “We restricted the start of our search to the beginning of 2005 because we would not expect earlier papers to be influenced by the seminal papers on EBSE [18,32] or the procedures for undertaking systematic reviews [30].”
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].”
Experimentation in Software Engineering (2012, background): “Joint research provides an excellent opportunity to improve industrial software development based on concrete evidence, and hence being a good example of evidence-based software engineering [48, 100].”
Lessons from applying the systematic literature review process within the software engineering domain (2007, unknown): “Withinthe medical domain, the steps that need to be followed to practise evidence-based medicine have been iden-tiﬁed and documented (Sackett et al., 2000), and these have subsequently been re-formulated to address evidence-based software engineering (Dyba˚ et al., 2005; Kitchenham et al., 2004).”
Knowledge management in software engineering: A systematic review of studied concepts, findings and research methods used (2008, background): “A recent trend in software engineering is an increased focus on evidence-based software engineering, EBSE [43, 67].”
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.”
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].”
Software development in startup companies: A systematic mapping study (2014, background): “One of the most important factors contributing to academic results being applied in the industry is the provision of strong scientific evidence [101, 102].”
Software Architecture Optimization Methods: A Systematic Literature Review (2013, methodology): “In line with the idea of evidence-based software engineering [78], this 674 IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL.”
The Future of Empirical Methods in Software Engineering Research (2007, background): “SE reviewers should consider using multiple digital libraries that include reports from both SE and related disciplines [41].”
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].”
Systematic literature studies: Database searches vs. backward snowballing (2012, unknown): “However, a practitioner-oriented view was formulated based on the EBSE ideas [6], and researchers also suggested guidelines for conducting systematic literature reviews [7].”
Systematic literature reviews in software engineering - A systematic literature review (2009, methodology): “The ICSE paper was followed-up by an article in IEEE Software [5] and a paper at Metrics05 [17].”
Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review (2006, background): “As mentioned in [52],[29] a systematic review should answer a clearly stated research question.”