The DOI matches its Crossref record; 27 of the 27 references it cites were found in a registry or an index.
Reporting guidelines for controlled experiments in software engineering
Open accessAbstract
One major problem for integrating study results into a common body of knowledge is the heterogeneity of reporting styles: (1) it is difficult to locate relevant information and (2) important information is often missing. Reporting guidelines are expected to support a systematic, standardized presentation of empirical research, thus improving reporting in order to support readers in (1) finding the information they are looking for, (2) understanding how an experiment is conducted, and (3) assessing the validity of its results. The objective of this paper is to survey the most prominent published proposals for reporting guidelines, and to derive a unified standard that which can serve as a starting point for further discussion. We provide detailed guidance on the expected content of the sections and subsections for reporting a specific type of empirical studies, i.e., controlled experiments. Before the guidelines can be evaluated, feedback from the research community is required. For this purpose, we propose to adapt guideline development processes from other disciplines.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Moher, D., Schulz, K. F., & Altman, D. G. (2001) · The Lancet · doi:10.1016/s0140-6736(00)04337-3 · Cited by 5,373
(2004) · Cited by 5,198
The Revised CONSORT Statement for Reporting Randomized Trials: Explanation and Elaboration
Altman, D. G., Schulz, K. F., Moher, D., Egger, M., Davidoff, F., Elbourne, D., Gøtzsche, P. C., Lang, T., & for the CONSORT Group (2001) · Annals of Internal Medicine · doi:10.7326/0003-4819-134-8-200104170-00012 · Cited by 3,835
Moher, D. (2001) · JAMA · doi:10.1001/jama.285.15.1987 · Cited by 2,545
Experimentation in Software Engineering: An Introduction
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2011) · Lund University Publications (Lund University) · Cited by 2,214
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000) · The Kluwer International Series in Software Engineering · doi:10.1007/978-1-4615-4625-2 · Cited by 1,776
Preliminary guidelines for empirical research in software engineering
Kitchenham, B. A., Pfleeger, S. L., Pickard, L. M., Jones, P. W., Hoaglin, D. C., El Emam, K., & Rosenberg, J. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1027796 · Cited by 1,510
Basics of Software Engineering Experimentation
Juristo, N., & Moreno, A. M. (2001) · Springer eBooks · doi:10.1007/978-1-4757-3304-4 · Cited by 753
Evidence-based software engineering
Kitchenham, B. A., Dyba, T., & Jorgensen, M. (2004) · Proceedings. 26th International Conference on Software Engineering · doi:10.1109/icse.2004.1317449 · Cited by 455
Writing good software engineering research papers
Shaw, M. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201262 · Cited by 213
Cited by
Guidelines for conducting and reporting case study research in software engineering
Runeson, P., & Höst, M. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9102-8 · Cited by 3,862
“…2) its conclusions are based on a clear chain of evidence, whether qualitative or quantitative, collected from multiple sources in a planned and consistent manner, and 3) it adds to existing knowledge by being based on previously established theory, if such exist, or by building theory.”
BackgroundGuide to Advanced Empirical Software Engineering
(2008) · Springer eBooks · doi:10.1007/978-1-84800-044-5 · Cited by 1,003
Matcha, W., Uzir, N. A., Gasevic, D., & Pardo, A. (2020) · IEEE Transactions on Learning Technologies · doi:10.1109/tlt.2019.2916802 · Cited by 399
Salleh, N., Mendes, E., & Grundy, J. (2011) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2010.59 · Cited by 356
Reporting Experiments in Software Engineering
Jedlitschka, A., Ciolkowski, M., & Pfahl, D. (2008) · Guide to Advanced Empirical Software Engineering · doi:10.1007/978-1-84800-044-5_8 · Cited by 331
Self-citationA systematic review on regression test selection techniques
Engström, E., Runeson, P., & Skoglund, M. (2010) · Information and Software Technology · doi:10.1016/j.infsof.2009.07.001 · Cited by 311
Ampatzoglou, A., Bibi, S., Avgeriou, P., Verbeek, M., & Chatzigeorgiou, A. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.10.006 · Cited by 305
Strength of evidence in systematic reviews in software engineering
Dybå, T., & Dingsøyr, T. (2008) · Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement · doi:10.1145/1414004.1414034 · Cited by 261
Empirical software engineering experts on the use of students and professionals in experiments
Falessi, D., Juristo, N., Wohlin, C., Turhan, B., Münch, J., Jedlitschka, A., & Oivo, M. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9523-3 · Cited by 257
Self-citationA systematic review of comparative evidence of aspect-oriented programming
Ali, M. S., Ali Babar, M., Chen, L., & Stol, K.-J. (2010) · Information and Software Technology · doi:10.1016/j.infsof.2010.05.003 · Cited by 89
Enriching software architecture documentation
Jansen, A., Avgeriou, P., & van der Ven, J. S. (2009) · Journal of Systems and Software · doi:10.1016/j.jss.2009.04.052 · Cited by 85
Tosun, A., Dieste, O., Fucci, D., Vegas, S., Turhan, B., Erdogmus, H., Santos, A., Oivo, M., Toro, K., Jarvinen, J., et al. (2017) · Empirical Software Engineering · doi:10.1007/s10664-016-9490-0 · Cited by 50
Metadata
- Authors
- Jedlitschka, A., & Pfahl, D.
- Venue
- 2005 International Symposium on Empirical Software Engineering, 2005.
- Publisher
- IEEE
- Published
- 2005
- Pages
- 10 pp.
- OpenAlex
- W1876404477
- Cited by
- 295
- References
- 27
- FWCI
- 9.33
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.