The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

Systematic Mapping Studies in Software Engineering

The work

AuthorsKai Petersen; ROBERT H. FELDT; Shahid Mujtaba; Michael Mattsson
Editors
Typemisc
Year2008
Citekeypetersen2008systematic

Where it appeared

Published inElectronic workshops in computing
PublisherBritish Computer Society

Identifiers

DOI10.14236/ewic/ease2008.8
OpenAlexW4214443

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

BACKGROUND: A software engineering systematic map is a defined method to build a classification scheme and structure a software engineering field of interest. The analysis of results focuses on frequencies of publications for categories within the scheme. Thereby, the coverage of the research field can be determined. Different facets of the scheme can also be combined to answer more specific research questions. OBJECTIVE: We describe how to conduct a systematic mapping study in software engineering and provide guidelines. We also compare systematic maps and systematic reviews to clarify how to chose between them. This comparison leads to a set of guidelines for systematic maps. METHOD: We have defined a systematic mapping process and applied it to complete a systematic mapping study. Furthermore, we compare systematic maps with systematic reviews by systematically analyzing existing systematic reviews. RESULTS: We describe a process for software engineering systematic mapping studies and compare it to systematic reviews. Based on this, guidelines for conducting systematic maps are defined. CONCLUSIONS: Systematic maps and reviews are different in terms of goals, breadth, validity issues and implications. Thus, they should be used complementarily and require different methods (e.g., for analysis).

How it got here

How it got hereagent via openalex
Added2026-10-24 18:58 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@misc{petersen2008systematic,
  title        = {Systematic Mapping Studies in Software Engineering},
  author       = {Kai Petersen and ROBERT H. FELDT and Shahid Mujtaba and Michael Mattsson},
  year         = {2008},
  journal      = {Electronic workshops in computing},
  publisher    = {British Computer Society},
  doi          = {10.14236/ewic/ease2008.8},
}

This record lives at https://refs.drheap.org/petersen2008systematic/ and will keep doing so.