How do scientists develop and use scientific software?
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
Some challenges facing software engineers developing software for scientists
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
Testing for trustworthiness in scientific software
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
A document driven methodology for developing a high quality Parallel Mesh Generation Toolbox
Advances in Engineering Software
Computer Supported Cooperative Work
A survey of scientific software development
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Scientific software production: incentives and collaboration
Proceedings of the ACM 2011 conference on Computer supported cooperative work
A literature review of agile practices and their effects in scientific software development
Proceedings of the 4th International Workshop on Software Engineering for Computational Science and Engineering
A domain specific requirements model for scientific computing (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Meanings and boundaries of scientific software sharing
Proceedings of the 2013 conference on Computer supported cooperative work
Restructuring Fortran legacy applications for parallel computing in multiprocessors
The Journal of Supercomputing
Industrial scientific software: a set of interviews on software development
CASCON '13 Proceedings of the 2013 Conference of the Center for Advanced Studies on Collaborative Research
| Hi-index | 0.00 |
The development of scientific software involves risk in the underlying theory, its implementation, and its use. Through a series of interviews, the authors explored how research scientists at two Canadian universities developed their software. These interviews indicated that the scientists used a set of strategies to address risk. They also suggested where the software engineering community could perform research focused on specific problems faced by scientific software developers.