Journal ArticleDOI
Code Conjurer: Pulling Reusable Software out of Thin Air
Reads0
Chats0
TLDR
This paper discusses how component-based reuse of the form Douglas Mcllroy envisaged in the 1960s is still the exception rather than the rule, and most of the systematic software reuse practiced today uses heavyweight approaches such as product-line engineering or domain-specific frameworks.Abstract:
For many years, the IT industry has sought to accelerate the software development process by assembling new applications from existing software assets. However, true component-based reuse of the form Douglas Mcllroy envisaged in the 1960s is still the exception rather than the rule, and most of the systematic software reuse practiced today uses heavyweight approaches such as product-line engineering or domain-specific frameworks. By component, we mean any cohesive and compact unit of software functionality with a well-defined interface - from simple programming language classes to more complex artifacts such as Web services and Enterprise JavaBeans.read more
Citations
More filters
Journal ArticleDOI
Adoption of open source software in software-intensive organizations - A systematic literature review
TL;DR: It is shown that adopting OSS involves more than simply using OSS products, and a framework consisting of six distinctly different ways in which organizations adopt OSS is provided, used to illustrate some of the opportunities and challenges organizations meet when approaching OSS.
Proceedings ArticleDOI
How do developers react to API deprecation?: the case of a smalltalk ecosystem
TL;DR: This paper reports on an empirical study of API deprecations that led to ripple effects across an entire ecosystem: the development community gravitating around the Squeak and Pharo software ecosystems.
Proceedings ArticleDOI
Asking and answering questions about unfamiliar APIs: an exploratory study
TL;DR: Twenty different types of questions programmers ask when working with unfamiliar APIs are identified, and new insights are provided to the cause of the difficulties programmers encounter when answering questions about the use of APIs.
Proceedings ArticleDOI
Codewebs: scalable homework search for massive open online programming courses
TL;DR: A method for decomposing online homework submissions into a vocabulary of "code phrases", and based on this vocabulary, a queryable index that allows for fast searches into the massive dataset of student homework submissions is designed.
Journal ArticleDOI
How Well Do Search Engines Support Code Retrieval on the Web
TL;DR: It was easier to find reference examples than components for as-is reuse and that participants obtained the best results using a general-purpose information retrieval site, and an interaction effect: code-specific search engines worked better in searches for subsystems, but Google worked better on searches for blocks.
References
More filters
Book
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
TL;DR: An entertaining and often enlightening text that defines what seasoned developers have long suspected: despite advances in software engineering, most software projects still fail to meet expectations--and about a third are cancelled altogether.
Journal ArticleDOI
Jungloid mining: helping to navigate the API jungle
TL;DR: Prospector as mentioned in this paper synthesizes jungloid code fragments automatically given a simple query that describes the desired code in terms of input and output types, which can be used to help programmers write client code more easily.
Proceedings ArticleDOI
Parseweb: a programmer assistant for reusing open source code on the web
Suresh Thummalapenta,Tao Xie +1 more
TL;DR: An approach that takes queries of the form "Source object type → Destination object type" as input, and suggests relevant method-invocation sequences that can serve as solutions that yield the destination object from the source object given in the query is developed.
Journal ArticleDOI
A survey of software reuse libraries
TL;DR: A survey of methods of storage and retrieval of software assets in software libraries finds that most existing solutions are either too ineffective to be useful or too intractable to be usable.
Journal ArticleDOI
Approximate Structural Context Matching: An Approach to Recommend Relevant Examples
TL;DR: The structural context needed to query the repository is extracted automatically from the code, freeing the developer from learning a query language or from writing their code in a particular style, avoiding the need for handcrafted examples.