<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Matthews, Jeanna Neefe</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">The case for repeated research in operating systems</style></title><secondary-title><style face="normal" font="default" size="100%">SIGOPS Oper. Syst. Rev.</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2004</style></year><pub-dates><date><style  face="normal" font="default" size="100%">April</style></date></pub-dates></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/991130.991131</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><volume><style face="normal" font="default" size="100%">38</style></volume><pages><style face="normal" font="default" size="100%">5–7</style></pages><abstract><style face="normal" font="default" size="100%">Repeated research is a well-respected model of investigation in many sciences. Independent tests of published research are valued because they document the general applicability of results. In addition, repeated research often sheds new light on aspects of a work not fully explored in the original publication and exposes unreported limitations. In computer science, researchers typically report results from testing software that they themselves have implemented. It is natural to wonder why independent tests of published results are so rare. 

[...]

In the sections that follow, I describe a model for repeated research in computer science. I also discuss my experiences using this model in more detail.

[...]</style></abstract></record></records></xml>