{"title":"软件工程中反对交叉设计的案例","authors":"B. Kitchenham, J. Fry, S. Linkman","doi":"10.1109/STEP.2003.32","DOIUrl":null,"url":null,"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.","PeriodicalId":260047,"journal":{"name":"Eleventh Annual International Workshop on Software Technology and Engineering Practice","volume":"6 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2003-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"24","resultStr":"{\"title\":\"The case against cross-over designs in software engineering\",\"authors\":\"B. Kitchenham, J. Fry, S. Linkman\",\"doi\":\"10.1109/STEP.2003.32\",\"DOIUrl\":null,\"url\":null,\"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.\",\"PeriodicalId\":260047,\"journal\":{\"name\":\"Eleventh Annual International Workshop on Software Technology and Engineering Practice\",\"volume\":\"6 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2003-09-19\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"24\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Eleventh Annual International Workshop on Software Technology and Engineering Practice\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/STEP.2003.32\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Eleventh Annual International Workshop on Software Technology and Engineering Practice","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/STEP.2003.32","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The case against cross-over designs in software engineering
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.