Plans and situated actions: the problem of human-machine communication
Plans and situated actions: the problem of human-machine communication
Implementing faceted classification for software reuse
Communications of the ACM - Special issue on software engineering
Software reuse: metrics and models
ACM Computing Surveys (CSUR)
Software engineering with reusable components
Software engineering with reusable components
A Classification of CASE Technology
Computer
Reusing Software: Issues and Research Directions
IEEE Transactions on Software Engineering
Recomposition: Coordinating a Web of SoftwareDependencies
Computer Supported Cooperative Work
Using structural context to recommend source code examples
Proceedings of the 27th international conference on Software engineering
Queue - Component Technologies
Audio Mashup Construction Kit (ExtremeTech) (ExtremeTech)
Audio Mashup Construction Kit (ExtremeTech) (ExtremeTech)
Software Process: Improvement and Practice - Advances in Software Process Improvement
Software Engineering: Principles and Practice
Software Engineering: Principles and Practice
Two studies of opportunistic programming: interleaving web foraging, learning, and writing code
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
On The Roles of APIs in the Coordination of Collaborative Software Development
Computer Supported Cooperative Work
How Well Do Search Engines Support Code Retrieval on the Web?
ACM Transactions on Software Engineering and Methodology (TOSEM)
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
Hi-index | 0.00 |
Every method for developing software is a prescriptive model. Applying a deconstructionist analysis to methods reveals that there are two texts, or sets of assumptions and ideals: a set that is privileged by the method and a second set that is left out, or marginalized by the method. We apply this analytical lens to software reuse, a technique in software development that seeks to expedite one's own project by using programming artifacts created by others. By analyzing the methods prescribed by Component-Based Software Engineering (CBSE), we arrive at two texts: Methodical CBSE and Amethodical Remixing. Empirical data from four studies on code search on the web draws attention to four key points of tension: status of component boundaries; provenance of source code; planning and process; and evaluation criteria for candidate code. We conclude the paper with a discussion of the implications of this work for the limits of methods, structure of organizations that reuse software, and the design of search engines for source code.