This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Comments on "Formal Methods Application: An Empirical Tale of Software Development"
June 2003 (vol. 29 no. 6)
pp. 567-571

Abstract—We comment on the experimental design and the result of the paper mentioned in the title. Our purpose is to show interested readers examples of what can go wrong with experiments in software research and how to avoid the attending problems.

[1] D.M. Berry, Formal Methods, the Very Idea, Some Thoughts on Why They Work When They Work Science of Computer Programming, vol. 42, no. 1, pp. 11-27, Jan. 2002.
[2] L.B. Christensen, Experimental Methodology, eighth ed. Allyn and Bacon, 2001.
[3] S.L. Pfleeger and L. Hatton, "Investigating the Influence of Formal Methods," Computer, Feb. 1997, pp. 33-43.
[4] A.E.K. Sobel, Empirical Results of a Software Engineering Curriculum Incorporating Formal Methods ACM Inroads, vol. 32, no. 1, pp. 157-161, Mar. 2000.
[5] A. Sobel and M. Clarkson, "Formal Methods Application: An Empirical Tale of Software Development," IEEE Trans. Software Eng., vol. 28, no. 3, Mar. 2002, pp. 308-320.

Citation:
Daniel M. Berry, Walter F. Tichy, "Comments on "Formal Methods Application: An Empirical Tale of Software Development"," IEEE Transactions on Software Engineering, vol. 29, no. 6, pp. 567-571, June 2003, doi:10.1109/TSE.2003.1205183
Usage of this product signifies your acceptance of the Terms of Use.