• Publications
  • Influence
Systematic Mapping Studies in Software Engineering
TLDR
This work describes how to conduct a systematic mapping study in software engineering and provides guidelines for conducting systematic maps, and compares systematic maps with systematic reviews by systematically analyzing existing systematic reviews. Expand
Guidelines for conducting systematic mapping studies in software engineering: An update
TLDR
There was a need to provide an update of how to conduct systematic mapping studies and how the guidelines should be updated based on the lessons learned from the existing systematic maps and SLR guidelines. Expand
A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case
TLDR
The principle results are that the case study and literature agree on the benefits while new issues arise when using agile in large-scale and an empirical research framework is needed to make agile studies comparable. Expand
Context in industrial software engineering research
  • K. Petersen, C. Wohlin
  • Computer Science, Engineering
  • 3rd International Symposium on Empirical Software…
  • 15 October 2009
TLDR
This paper structures the context for empirical industrial studies and provides a checklist to aid researchers in making informed decisions concerning which parts of the context to include in the descriptions. Expand
Measuring and predicting software productivity: A systematic map and review
  • K. Petersen
  • Computer Science, Engineering
  • Inf. Softw. Technol.
  • 1 April 2011
TLDR
Data envelopment analysis seems to be a strong approach to capture multivariate productivity measures, and allows to identify reference projects to which inefficient projects should be compared. Expand
The effect of moving from a plan-driven to an incremental software development approach with agile practices
TLDR
It is concluded that the recent introduction of incremental and agile practices brings added values in comparison to the plan- driven approach, which is evident from the absence of critical issues that are encountered in plan-driven development. Expand
On rapid releases and software testing: a case study and a semi-systematic literature review
TLDR
The changes in software testing effort after moving to rapid releases is investigated in the context of a case study on Mozilla Firefox, and a semi-systematic literature review shows that rapid releases are a prevalent industrial practice that are utilized even in some highly critical domains of software engineering. Expand
What is DevOps?: A Systematic Mapping Study on Definitions and Practices
TLDR
A definition for DevOps is proposed which may overcome inconsistencies over the various existing definitions of individual research studies and the practices explicitly proposed for Dev Ops have been presented as well as the relation to other software development methods. Expand
Benefits and limitations of automated software testing: Systematic literature review and practitioner survey
TLDR
The survey showed that benefits of test automation were related to test reusability, repeatability, test coverage and effort saved in test executions, and 80% of the practitioners disagreed with the vision that automated testing would fully replace manual testing. Expand
Considering rigor and relevance when evaluating test driven development: A systematic review
TLDR
Strong indications are obtained that external quality is positively influenced, which has to be further substantiated by industry experiments and longitudinal case studies and in comparison to previous reviews. Expand
...
1
2
3
4
5
...