default search action
1st SE-CSE@ICSE 2009: Vancouver, BC, Canada
- ICSE Workshop on Software Engineering for Computational Science and Engineering, SE-CSE 2009, Vancouver, BC, Canada, May 23, 2009. IEEE Computer Society 2009, ISBN 978-1-4244-3737-5
Software Development Processes for Computational Science and Engineering
- Jo Erskine Hannay, Hans Petter Langtangen, Carolyn MacLeod, Dietmar Pfahl, Janice Singer, Greg Wilson:
How do scientists develop and use scientific software? 1-8 - Judith Segal:
Some challenges facing software engineers developing software for scientists. 9-14 - Michael A. Heroux, James M. Willenbring:
Barely sufficient software engineering: 10 practices to improve your CSE software. 15-21 - Carlton A. Crabtree, Akif Günes Koru, Carolyn B. Seaman, Hakan Erdogmus:
An empirical characterization of scientific software development projects according to the Boehm and Turner model: A progress report. 22-27
Specific Techniques for Computational Science and Engineering Software Development I
- Jeffrey L. Overbey, Stas Negara, Ralph E. Johnson:
Refactoring and the evolution of Fortran. 28-34 - Roscoe A. Bartlett:
Integration strategies for Computational Science & Engineering software. 35-42 - Wen Yu, Spencer Smith:
Reusability of FEA software: A program family approach. 43-50 - Ritu Arora, Purushotham V. Bangalore, Marjan Mernik:
Developing scientific applications using Generative Programming. 51-58
Specific Techniques for Computational Science and Engineering Software Development II
- Daniel Hook, Diane Kelly:
Testing for trustworthiness in scientific software. 59-64 - David Woollard, Chris Mattmann, Nenad Medvidovic:
Injecting software architectural constraints into legacy scientific applications. 65-71 - Parmit K. Chilana, Carole L. Palmer, Amy J. Ko:
Comparing bioinformatics software development by computer scientists and biologists: An exploratory study. 72-79 - Valerie Maxville:
Preparing scientists for scalable software development. 80-85
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.