This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Evidence-Based Cost Estimation for Better-Quality Software
July/August 2006 (vol. 23 no. 4)
pp. 64-66
Tim Menzies, West Virginia University
Jairus Hihn, Jet Propulsion Laboratory
Evidence-based reasoning is becoming common in many fields. It's widely enshrined in the practice and teaching of medicine, law, and management, for example. Evidence-based approaches demand that, among other things, practitioners systematically track down the best evidence relating to some practice; critically appraise that evidence for validity, impact, and applicability; and carefully document it. One proponent of evidence-based software engineering is David Budgen of Durham University. In the Internet age, he argues, many sources of supposed knowledge--Google, Wikipedia, digg.com, and so on--surround us. At his keynote address at the 2006 Conference on Software Engineering Education and Training, Budgen asks, how should we train students to assess all that information and to separate the sense from the nonsense? In his view, before we can denounce some inaccuracy in, say, Wikipedia, we must first look to our own work and audit our own results.
Index Terms:
evidence-based reasoning, evidence-based software engineering
Citation:
Tim Menzies, Jairus Hihn, "Evidence-Based Cost Estimation for Better-Quality Software," IEEE Software, vol. 23, no. 4, pp. 64-66, July-Aug. 2006, doi:10.1109/MS.2006.99
Usage of this product signifies your acceptance of the Terms of Use.