How Accurate is Scientific Software?
IEEE Transactions on Software Engineering
Software engineering: theory and practice
Software engineering: theory and practice
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Software engineering (2nd ed.): principles and practice
Software engineering (2nd ed.): principles and practice
Software Requirements
Extreme Programming Installed
Test Driven Development: By Example
Test Driven Development: By Example
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
Method engineering for OO systems development
Communications of the ACM - Service-oriented computing
Task-directed software inspection
Journal of Systems and Software - Special issue: Applications of statistics in software engineering
International Journal of High Performance Computing Applications
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
A Study of Design Characteristics in Evolving Software Using Stability as a Criterion
IEEE Transactions on Software Engineering
The Chimera of Software Quality
Computer
Scientific Software Development at a Research Facility
IEEE Software
Configuration Management for Large-Scale Scientific Computing at the UK Met Office
Computing in Science and Engineering
Determining factors that affect long-term evolution in scientific application software
Journal of Systems and Software
Testing for trustworthiness in scientific software
SECSE '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Computational Science and Engineering
| Hi-index | 0.00 |
The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.