This Article 
 Bibliographic References 
 Add to: 
I Believe! (HTML)
January/February 2012 (vol. 29 no. 1)
pp. 4-7
Forrest Shull, Fraunhofer Center for Experimental Software Engineering
Many studies have shown that important factors and key relationships often don't hold up well when transferred from one project to another. To deal with this seeming lack of global truisms in software engineering, it helps to develop a healthy skepticism and find ways to test our beliefs in key development practices against measures collected within the project context.

1. C. Passos et al., "Analyzing the Impact of Beliefs in Software Project Practices," Proc. ACM/IEEE Int'l Symp. Empirical Software Eng. and Measurement (ESEM '11), to be published in IEEE CS Press, 2011;
2. Tim Menzies et al., "Simple Software Cost Analysis: Safe or Unsafe?" ACM SIGSOFT Software Eng. Notes, vol. 30, no. 4, 2005, pp. 1–6;
3. T. Zimmermann et al., "Cross-Project Defect Prediction," Proc. 7th Joint Meeting European Software Eng. Conf. and ACM SIGSOFT Symp. Foundations of Software Eng. (ESEC/FSE '09), ACM Press, 2009, pp. 91–100.
4. F. Shull et al., "What Do We Know about Test-Driven Development?" IEEE Software, vol. 27, no. 6, 2010, pp. 16–19.

Index Terms:
effort prediction, defect prediction, empirical software engineering
Forrest Shull, "I Believe!," IEEE Software, vol. 29, no. 1, pp. 4-7, Jan.-Feb. 2012, doi:10.1109/MS.2012.10
Usage of this product signifies your acceptance of the Terms of Use.