Implementing faceted classification for software reuse
Communications of the ACM - Special issue on software engineering
An Information Retrieval Approach for Automatically Constructing Software Libraries
IEEE Transactions on Software Engineering
Computing similarity in a reuse library system: an AI-based approach
ACM Transactions on Software Engineering and Methodology (TOSEM)
A translation approach to portable ontology specifications
Knowledge Acquisition - Special issue: Current issues in knowledge modeling
Signature matching: a tool for using software libraries
ACM Transactions on Software Engineering and Methodology (TOSEM)
Location-independent naming for virtual distributed software repositories
SSR '95 Proceedings of the 1995 Symposium on Software reusability
Software engineering with reusable components
Software engineering with reusable components
Storing and Retrieving Software Components: A Refinement Based System
IEEE Transactions on Software Engineering
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Neural Networks and Structured Knowledge: Knowledge Representation and Reasoning
Applied Intelligence
A software classification scheme (reusability, libraries, development)
A software classification scheme (reusability, libraries, development)
A methodology for component-based system integration
A methodology for component-based system integration
| Hi-index | 0.00 |
The construction of large software systems from existing components requires efficient access to possibly large collections of such components. In this paper, we present a content-based framework to organize this large collection of components in a semi-automatic fashion, according to an extensible user-defined ontology. Neural associative memories are used for fast, similarity-based access. Relevant characteristics of components are extracted and stored as a "signature" in such an associative memory, and during retrieval the closest matches to the query are indicated in very short time. In addition to content-based characteristics such as keywords, function and variable names, comments, and the location of the component in the class hierarchy, this method can be easily expanded to include usage characteristics, resource requirements, or other task- or customer-specific criteria.