Coordination mechanisms: towards a conceptual foundation of CSCW systems design
Computer Supported Cooperative Work - Special issue on the design of cooperative systems
The grid: blueprint for a new computing infrastructure
The grid: blueprint for a new computing infrastructure
Infrastructuring for the Long-Term: Ecological Information Management
HICSS '04 Proceedings of the Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04) - Track 1 - Volume 1
Special Issue: Collaboration in e-Research
Computer Supported Cooperative Work
The human infrastructure of cyberinfrastructure
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
Synergizing in Cyberinfrastructure Development
Computer Supported Cooperative Work
Sociotechnical Studies of Cyberinfrastructure and e-Research: Current Themes and Future Trajectories
Computer Supported Cooperative Work
Sustaining the development of cyberinfrastructure: an organization adapting to change
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
A sociotechnical exploration of infrastructural middleware development
Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work
The policy knot: re-integrating policy, practice and design in cscw studies of social computing
Proceedings of the 17th ACM conference on Computer supported cooperative work & social computing
Supporting Scientific Collaboration: Methods, Tools and Concepts
Computer Supported Cooperative Work
| Hi-index | 0.00 |
Middleware software, which provides an abstraction layer between low-level computational services and domain-specific applications, is a key component of cyberinfrastructure. This paper presents a qualitative study of how cyberinfrastructure middleware development is accomplished in two supercomputing centers. Our investigation highlights key development phases in the lives of middleware projects. Middleware development is typically undertaken as part of collaborations between technologists and domain scientists, and middleware developers must balance the pressure to meet specific scientific needs and the desire to explore their own R&D agendas. We explore how developers work to sustain an ongoing development trajectory by aligning their own work with particular domain science projects and funding streams. However, we find that the key transition from being a component in a domain-specific project to a stand-alone system that is useful across domains is particularly challenging for middleware development. We provide organizational and national policy implications for how to better support this transition.