Extreme programming explained: embrace change
Extreme programming explained: embrace change
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
Whither or whether HCI: requirements analysis for multi-sited, multi-user cyberinfrastructures
CHI '06 Extended Abstracts on Human Factors in Computing Systems
Some Problems of Professional End User Developers
VLHCC '07 Proceedings of the IEEE Symposium on Visual Languages and Human-Centric Computing
Growing an infrastructure: the role of gateway organizations in cultivating new communities of users
Proceedings of the 2007 international ACM conference on Supporting group work
Moving beyond user participation to achieve successful IS design
Communications of the ACM
Developing Scientific Software
IEEE Software
Software Design for Empowering Scientists
IEEE Software
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
Computer Supported Cooperative Work
Some Challenges Facing Scientific Software Developers: The Case of Molecular Biology
E-SCIENCE '09 Proceedings of the 2009 Fifth IEEE International Conference on e-Science
Engineering the Software for Understanding Climate Change
Computing in Science and Engineering
Hi-index | 0.00 |
When software supports the complex and poorly understood application domain of cutting-edge science, effective engagement between its users/customers and developers is crucial. Drawing on recent literature, the authors examine barriers to such engagement. Significant among these barriers is the effects of the experience that many research scientists have of local scientific end-user development. Through a case study, the authors demonstrate that involving such scientists in a team developing software for a widely distributed group of scientists can have a positive impact on establishing requirements and promoting adoption of the software. However, barriers to effective engagement exist, which scientific end-user developers can do little to address. Such barriers stem from the essential nature of scientific practice.