This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Scientific Software Testing: Analysis with Four Dimensions
May/June 2011 (vol. 28 no. 3)
pp. 84-90
ASCII Text
x 
 
Diane Kelly, Stefan Thorsteinson, Daniel Hook, "Scientific Software Testing: Analysis with Four Dimensions," IEEE Software, vol. 28, no. 3, pp. 84-90, May/June, 2011.
 
 
BibTex
x
 
@article{ 10.1109/MS.2010.88,
author = {Diane Kelly and Stefan Thorsteinson and Daniel Hook},
title = {Scientific Software Testing: Analysis with Four Dimensions},
journal ={IEEE Software},
volume = {28},
number = {3},
issn = {0740-7459},
year = {2011},
pages = {84-90},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.88},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Scientific Software Testing: Analysis with Four Dimensions
IS - 3
SN - 0740-7459
SP84
EP90
EPD - 84-90
A1 - Diane Kelly,
A1 - Stefan Thorsteinson,
A1 - Daniel Hook,
PY - 2011
KW - scientific software
KW - software testing
KW - multidisciplinary team
VL - 28
JA - IEEE Software
ER -
 
Diane Kelly, Royal Military College
Stefan Thorsteinson, Royal Military College
Daniel Hook, Engineering Seismology Group Solutions
The authors describe a code testing exercise with an example of scientific software. As part of their analysis of the exercise, they examined four dimensions of testing: context, goals, technique, and adequacy. They started the exercise with approaches commonly described in software engineering literature. During the exercise, testing activities shifted to something more suitable for the situation. The authors analyze this shift, using the four dimensions. Goals changed from general to specific for the scientist, and testing techniques shifted to those that more strongly used and supported the scientist's expertise. In the end, the testing exercise made better use of the scientist's dual role of developer and user.

1. J. Segal, "Scientists and Software Engineers: A Tale of Two Cultures," Proc. Psychology of Programming Interest Group (PPIG 08), Lancaster Univ., 2008, pp. 44–51.
2. R. Sanders and D. Kelly, "Scientific Software: Where's the Risk and How Do Scientists Deal with It?" IEEE Software, vol. 25, no. 4, 2008, pp. 21–28.
3. T. Shepard and D. Kelly, Dimensions of Testing, tech. report TR-74.188-13, 2003; https://www-927.ibm.com/ibm/cas/publications/ TR-74.188/13index.pdf.
4. R.L. Glass, "Inspections—Some Surprising Findings," Comm. ACM, vol. 42, no. 4, 1999, pp. 17–19.
5. D. Kelly and T. Shepard, "Task-Directed Software Inspection," J. Systems and Software, vol. 73, no. 2, 2004, pp. 361–368.
6. D. Kelly and T. Shepard, "Task-Directed Software Inspection Technique: An Experiment and Case Study," Proc. IBM Centers for Advanced Studies Conf. (CASCON 2000), IBM Press, 2000; http://portal.acm.orgcitation.cfm?id=782040 .
7. D. Kelly, N. Cote, and T. Shepard, "Software Engineers and Nuclear Engineers: Teaming Up to Do Testing," Proc. Canadian Nuclear Soc. Conf., Canadian Nuclear Soc., June 2007.
8. D.A. Hook, "Using Code Mutation to Study Code Faults in Scientific Software," master's thesis, Queen's Univ., Kingston, Canada, 2009; https://qspace.library.queensu.ca/handle/ 19741765.

Index Terms:
scientific software, software testing, multidisciplinary team
Citation:
Diane Kelly, Stefan Thorsteinson, Daniel Hook, "Scientific Software Testing: Analysis with Four Dimensions," IEEE Software, vol. 28, no. 3, pp. 84-90, May-June 2011, doi:10.1109/MS.2010.88
Usage of this product signifies your acceptance of the Terms of Use.