The vocabulary problem in human-system communication
Communications of the ACM
The Ada Generic Library linear list processing packages
The Ada Generic Library linear list processing packages
The case for case studies of programming problems
Communications of the ACM
Communications of the ACM
Populating software repositories: incentives and domain-specific software
Journal of Systems and Software - Special issue on software reuse
CLASSLIB — class management and reuse support on a MVS mainframe
SAC '94 Proceedings of the 1994 ACM symposium on Applied computing
Developing reusable Java components
Proceedings of the 1997 symposium on Software reusability
Design Wizards and Visual Programming Environments for GenVoca Generators
IEEE Transactions on Software Engineering
A survey of software reuse libraries
Annals of Software Engineering
Browsing a Component Library Using Non-functional Information
Ada-Europe '99 Proceedings of the 1999 Ada-Europe International Conference on Reliable Software Technologies
An Internet-based Information System for Cooperative Software Reuse
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
Design Wizards and Visual Programming Environments for Generators
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
COMPSAC '96 Proceedings of the 20th Conference on Computer Software and Applications
Ranking Significance of Software Components Based on Use Relations
IEEE Transactions on Software Engineering
| Hi-index | 0.01 |
Reusable Software Libraries (RSLs) often suffer from poor interfaces, too many formal standards, high levels of training required for their use, and most of all, a high cost to build and maintain. Hence, RSLs have largely failed to return the reuse benefits promised by their developers. This paper first describes an RSL implementation using the World Wide Web (WWW) browser Mosaic and shows how it meets most RSL needs, avoids most RSL pitfalls, and costs only a fraction of the cost for the average commercial RSL. Second, the paper describes a way to quickly assess the important aspects of a piece of software so programmers can decide whether or not to reuse it. Using the observation that when programmers discuss software they tend to convey the same key information in a somewhat predictable order, this paper describes a method to automatically mimic this activity using a Structured Abstract of reusable components. Structured Abstracts provide a natural, easy to use way for developers to (1) search for components, (2) quickly assess the component for use, and (3) submit components to the RSL.