Buyer behavior · Systematic mapping study

Software Productivity in Practice: A Systematic Mapping Study

Software · 2022

Carlos Henrique C. Duarte

Original paper ↗

Summary

Maps how software productivity is defined, measured, and studied in practice.

For your marketing

Possible founder application

Use the map to build a balanced measurement model rather than adopting a single productivity proxy.

Reported result

What the study found

Maps how software productivity is defined, measured, and studied in practice.

Research question

What the authors investigated

How does the study’s stated design explain its reported outcome in this setting?

Design

Systematic mapping study

Sample and setting

Research literature on software productivity; abstract-only

Scope and transfer

Limitations to keep in view

Mapping results inherit heterogeneity and quality limits of the underlying literature.

Research sources

abstract_only

Study strength

3.5/5 Abstract-level evidence is useful for framing questions; verify full methods before transfer.

How this was assessed

The 1–5 evidence-check score is a practical reading aid, not a formal peer review or a probability that a conclusion is true. It combines design strength (2 points), sample reporting (1), comparison/control clarity (1), and how much of the paper could be checked (1). Access affects how confidently this directory can assess a study, not the study's underlying quality. Blinding is reported separately because it is not relevant to every design.

Design transparency · 2/2

Based on the reported study design in the retrieved source.

Sample and setting · 1/1

The sample context is stated; a numerical count is preserved only when reported.

Outcome clarity · 1/1

The finding is summarized from publisher or article metadata.

Access for checking · 0.5/1

Only abstract or bibliographic access was confirmed.

Double-blind? The retrieved publisher record does not establish whether participants or outcome assessors were blinded.

Read the paper