ACM Home Page
Please provide us with feedback. Feedback
Evaluating guidelines for empirical software engineering studies
Full text PdfPdf (252 KB)
Source International Symposium on Empirical Software Engineering archive
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering table of contents
Rio de Janeiro, Brazil
SESSION: Research methodology table of contents
Pages: 38 - 47  
Year of Publication: 2006
ISBN:1-59593-218-6
Authors
Barbara Kitchenham  National ICT Australia Ltd, Sydney, Australia
Hiyam Al-Khilidar  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
Muhammad Ali Babar  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
Mike Berry  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
Karl Cox  National ICT Australia Ltd, Sydney, Australia
Jacky Keung  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
Felicia Kurniawati  National ICT Australia Ltd, Sydney, Australia
Mark Staples  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
He Zhang  National ICT Australia Ltd, Sydney, Australia and University of New South Wales, Sydney, Australia
Liming Zhu  National ICT Australia Ltd, Sydney, Australia
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 24,   Downloads (12 Months): 152,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1159733.1159742
What is a DOI?

ABSTRACT

Background. Several researchers have criticized the standards of performing and reporting empirical studies in software engineering. In order to address this problem, Andreas Jedlitschka and Dietmar Pfahl have produced reporting guidelines for controlled experiments in software engineering. They pointed out that their guidelines needed evaluation. We agree that guidelines need to be evaluated before they can be widely adopted. If guidelines are flawed, they will cause more problems that they solve.Aim. The aim of this paper is to present the method we used to evaluate the guidelines and report the results of our evaluation exercise. We suggest our evaluation process may be of more general use if reporting guidelines for other types of empirical study are developed.Method. We used perspective-based inspections to perform a theoretical evaluation of the guidelines. A separate inspection was performed for each perspective. The perspectives used were: Researcher, Practitioner/Consultant, Meta-analyst, Replicator, Reviewer and Author. Apart from the Author perspective, the inspections were based on a set of questions derived by brainstorming. The inspection using the Author perspective reviewed each section of the guidelines sequentially. Results. The question-based perspective inspections detected 42 issues where the guidelines would benefit from amendment or clarification and 8 defects.Conclusions. Reporting guidelines need to specify what information goes into what section and avoid excessive duplication. Software engineering researchers need to be cautious about adopting reporting guidelines that differ from those used by other disciplines. The current guidelines need to be revised and the revised guidelines need to be subjected to further theoretical and empirical validation. Perspective-based inspection is a useful validation method but the practitioner/consultant perspective presents difficulties.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
Tore Dybå, Vigdis By Kampenes, Dag I.K. Sjøberg. A systematic review of statistical power in software engineering experiments. Information and Software Technology, in press.
 
4
Peter Harris. Designing and Reporting Experiments in Psychology. 2nd Edition, Open University Press, 2002.
 
5
James Hartley. Current findings from research on structured abstracts. J. Med. Libr. Assoc. 92(3), July 2004, pp 368--371.
 
6
Andreas Jedlitschka and Dietmar Pfahl. Reporting Guidelines for Controlled Experiments in Software Engineering. IESEReport IESE-035.5/E, 2005.
 
7
 
8
David Moher, Kenneth F Schultz, Douglas Altman. The CONSORT statement: revised recommendations for improving the quality of reports of parallel-group randomized trials. The LANCET, 357, April 14, 2001, pp. 1191--1194.
 
9
Pickard, L.M., Kitchenham, B.A., and Jones, P. (1998) Combining Empirical Results in Software Engineering. Information and Software Technology. Vol 40 No 14, pp 811--821.
 
10
 
11
 
12
 
13
 
14


Collaborative Colleagues:
Barbara Kitchenham: colleagues
Hiyam Al-Khilidar: colleagues
Muhammad Ali Babar: colleagues
Mike Berry: colleagues
Karl Cox: colleagues
Jacky Keung: colleagues
Felicia Kurniawati: colleagues
Mark Staples: colleagues
He Zhang: colleagues
Liming Zhu: colleagues