The Case Against Cross-Over Designs in Software Engineering

Authors:
Barbara Kitchenham;John Fry;Stephen Linkman
Affiliations:
Keele University and NICTA;P.N. Lee Statistics and Computing Ltd.;Keele University
Venue:
STEP '03 Proceedings of the Eleventh Annual International Workshop on Software Technology and Engineering Practice
Year:
2003

Citing 0
Cited 6

An empirical study of groupware support for distributed software architecture evaluation process

Journal of Systems and Software - Special issue: Selected papers from the 11th Asia Pacific software engineering conference (APSEC 2004)
Distributed versus face-to-face meetings for architecture evalution: a controlled experiment

Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
A systematic review of quasi-experiments in software engineering

Information and Software Technology
Assessing multiview framework (MF) comprehensibility and efficiency: A replicated experiment

Information and Software Technology
An experimental comparison of ER and UML class diagrams for data modelling

Empirical Software Engineering
Effectiveness for detecting faults within and outside the scope of testing techniques: an independent replication

Empirical Software Engineering

Quantified Score

Hi-index	0.01

Visualization

Abstract

We are often encouraged to follow experimental procedures in undertaking software engineering studies, however we should not do so blindly as often assumptions are made as part of that process that software engineering methods artefacts and processes breach. One such example is the use of crossover designs. We consider the case where there are period by treatment interactions,( i.e where the treatments are non-commutative) and demonstrate the hazards in using a cross-over design in these cases.