Context Systematic mapping studies are used to structure a research area, while systematic reviews are focused on gathering and synthesizing evidence. The most recent guidelines for systematic mapping are from 2008. Since that time, many suggestions have been made of how to improve systematic literature reviews (SLRs). There is a need to evaluate how researchers conduct the process of systematic mapping and identify how the guidelines should be updated based on the lessons learned from the existing systematic maps and SLR guidelines. Objective To identify how the systematic mapping process is conducted (including search, study selection, analysis and presentation of data, etc.); to identify improvement potentials in conducting the systematic mapping process and updating the guidelines accordingly. Method We conducted a systematic mapping study of systematic maps, considering some practices of systematic review guidelines as well (in particular in relation to defining the search and to conduct a quality assessment). Results In a large number of studies multiple guidelines are used and combined, which leads to different ways in conducting mapping studies. The reason for combining guidelines was that they differed in the recommendations given. Conclusion The most frequently followed guidelines are not sufficient alone. Hence, there was a need to provide an update of how to conduct systematic mapping studies. New guidelines have been proposed consolidating existing findings.

Guidelines for conducting systematic mapping studies in software engineering : An update

Guide to the Software Engineering Body of Knowledge - SWEBOK

/pdf/the-guide-to-the-software-engineering-body-of-knowledge-2py588n7u7.pdf

The Guide to the Software Engineering Body of Knowledge Reporting on the SWEBOK pr o ject, t he authors—who re pr e sent the pr o ject's editorial team—discuss the thr e e-phase plan to characterize a body of knowledge, a vital step toward developing softwar e engineering as a pr o fession.

Context: In a previous study, we reported on a systematic literature review (SLR), based on a manual search of 13 journals and conferences undertaken in the period 1st January 2004 to 30th June 2007. Objective: The aim of this on-going research is to provide an annotated catalogue of SLRs available to software engineering researchers and practitioners. This study updates our previous study using a broad automated search. Method: We performed a broad automated search to find SLRs published in the time period 1st January 2004 to 30th June 2008. We contrast the number, quality and source of these SLRs with SLRs found in the original study. Results: Our broad search found an additional 35 SLRs corresponding to 33 unique studies. Of these papers, 17 appeared relevant to the undergraduate educational curriculum and 12 appeared of possible interest to practitioners. The number of SLRs being published is increasing. The quality of papers in conferences and workshops has improved as more researchers use SLR guidelines. Conclusion: SLRs appear to have gone past the stage of being used solely by innovators but cannot yet be considered a main stream software engineering research methodology. They are addressing a wide range of topics but still have limitations, such as often failing to assess primary study quality.

https://romisatriawahono.net/wp-content/uploads/2013/01/Kitchenham-Systematic-literature-reviews-in-software-engineering-%E2%80%93-A-tertiary-study-2012.pdf

Systematic literature reviews in software engineering - A tertiary study

data types Sorting and searching parallel and distributed algorithms 3. [AR] Computer Architecture

/pdf/guide-to-the-software-engineering-body-of-knowledge-4x9ajlpq2m.pdf

Guide to the Software Engineering Body of Knowledge

Guide to the software engineering body of knowledge

In the Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Societys responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guides 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK Guide are Pierre Bourque (cole de technologie suprieure (TS), Universit du Qubec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).

Pierre Bourque

Papers

Guide to the Software Engineering Body of Knowledge - SWEBOK

The Guide to the Software Engineering Body of Knowledge Reporting on the SWEBOK pr o ject, t he authors—who re pr e sent the pr o ject's editorial team—discuss the thr e e-phase plan to characterize a body of knowledge, a vital step toward developing softwar e engineering as a pr o fession.

Guide to the software engineering body of knowledge

Guide to the Software Engineering Body of Knowledge (SWEBOK(R)): Version 3.0

Guide to the Software Engineering Body of Knowledge : 2004 Version