|
| This Article | ||
| | ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ASCII Text | x | ||
| "Letters," IEEE Software, vol. 24, no. 6, pp. 6-8, November/December, 2007. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2007.172, author = {}, title = {Letters}, journal ={IEEE Software}, volume = {24}, number = {6}, issn = {0740-7459}, year = {2007}, pages = {6-8}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2007.172}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Letters IS - 6 SN - 0740-7459 SP6 EP8 EPD - 6-8 PY - 2007 VL - 24 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2007.172
[1] I. Vessey, "Problems versus Solutions: The Role of the Application Domain in Software," Proc. 7th Workshop Empirical Studies of Programmers, ACM Press, 1997, pp. 233–240.
[2] G. Wilson, "Where's the Real Bottleneck in Scientific Computing?" Am. Scientist, vol. 94, no. 1, 2006, p. 5; www.americanscientist.org/template/ AssetDetail/assetid48548.
[3] R. Glass, "Matching Methodology to Problem Domain," Comm. ACM, vol. 47, no. 5, 2004, pp. 19–21.
[4] R.F. Boisvert and P.T.P. Tang, eds., The Architecture of Scientific Software, Kluwer Academic, 2001.
Citation:
"Letters," IEEE Software, vol. 24, no. 6, pp. 6-8, Nov.-Dec. 2007, doi:10.1109/MS.2007.172
Usage of this product signifies your acceptance of the Terms of Use.

