case-based reasoning for reducing software development effort减少软件开发工作的案例推理.pdfVIP

J. Software Engineering Applications, 2010, 3, 1005-1014 doi:10.4236/jsea.2010.311118 Published Online November 2010 (http://www.SciRP.org/journal/jsea) Case-Based Reasoning for Reducing Software Development Effort 1 1 1 1 2 Adam Brady , Tim Menzies , Oussama El-Rawas , Ekrem Kocaguneli , Jacky W. Keung 1Lane Department of CSEE, West Virginia University, Morgantown, USA; 2Department of Computing, The Hong Kong Polytech- nic University, Hong Kong, China. Email: adam.m.brady@, tim@menzies.us, orawas@, kocaguneli@, jacky.keung@.hk Received June 24th, 2010; revised July 15th, 2010; accepted July 19th, 2010. ABSTRACT How can we best find project changes that most improve project estimates? Prior solutions to this problem required the use of standard software process models that may not be relevant to some new project. Also, those prior solutions suf- fered from limited verification (the only way to assess the results of those studies was to run the recommendations back through the standard process models). Combining case-based reasoning and contrast set learning, the W system re- quires no underlying model. Hence, it is widely applicable (since there is no need for data to conform to some software process models ). Also, W’s results can be verified (using holdout sets). For example, in the experiments reported here, W found changes to projects that greatly reduced estimate median and variance by up to 95% and 83% (respectively). Keywords : Software Effort Estimation, Case Based Reasoning, Effort Estimation 1. Introduction more data sets since there is no requirement for the data sets to be in the format required by the standard Existing research in