issues practitioners face in practice1 Systematic reviews (SRs) were presented as a way to integrate the best research evidence with practice2 However... some argue that there is a lack of connection between SRs and software engineering (SE) practice3,4 2 1. Mamykina, et al. Design lessons from the fastest q&a site in the west, CHI, 2011 2. Kitchenham et al. Evidence-Based Software Engineering, ICSE 2004 3. Hassler et al. Outcomes of a community workshop to identify and rank barriers to the systematic literature review process, EASE 2014 4. Santos and Da Silva. Motivation to perform systematic reviews and their impact on software engineering practice, ESEM 2013
posted on Q&A websites? Operational Definition of Coverage When at least one finding of a SR offers knowledge that helps to solve a question posted in SE related StackExchange websites 3
Project Management (PM) Quality Assurance & Testing (SQA) Reverse Engineering (RE) Software Recommendations (SREC) 5 120 SRs of a tertiary study1 32 SRs with guidelines1 24 SRs with search string 4 SRs about agile Practitioners guildelines filter 1. Da Silva et al. Six years of systematic literature reviews in software engineering: An updated tertiary study, IST, 2011 Search string filter Agile filter
research topic is demanded in practice Limitations The SRs came from a tertiary study published in 2011 Future Work Expand this analysis to SRs published till nowadays 10