Classification of reusable modules
Software reusability: vol. 1, concepts and models
Program understanding: challenge for the 1990's
IBM Systems Journal
Object-oriented software engineering
Object-oriented software engineering
An Information Retrieval Approach for Automatically Constructing Software Libraries
IEEE Transactions on Software Engineering
Making software reuse work: an implementation model
ACM SIGSOFT Software Engineering Notes
The REBOOT approach to software reuse
Journal of Systems and Software - Special issue on software reuse
Retrieval of reusable components using functional similarity
Software—Practice & Experience
A Query Algebra for Program Databases
IEEE Transactions on Software Engineering
Integrating Independently-Developed Components in Object-Oriented Languages
ECOOP '93 Proceedings of the 7th European Conference on Object-Oriented Programming
SQLf: a relational database language for fuzzy querying
IEEE Transactions on Fuzzy Systems
User opinions and rewards in a reuse-based development system
SSR '99 Proceedings of the 1999 symposium on Software reusability
An execution-based retrieval of object-oriented components
ACM-SE 37 Proceedings of the 37th annual Southeast regional conference (CD-ROM)
Organizing and retrieving class components based on types for reuse
ACM-SE 37 Proceedings of the 37th annual Southeast regional conference (CD-ROM)
A hierarchy-aware approach to faceted classification of objected-oriented components
ACM Transactions on Software Engineering and Methodology (TOSEM)
Corrigenda: a hierarchy-aware approach to faceted classification of object-oriented components
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 4.10 |
The COOR environment (Classification of Object-Oriented Code for Reuse) is based on an abstraction method that represents code behavior in terms of software descriptors. Descriptors constitute a classification and retrieval unit and are constructed from source code and other documentation as lists of term pairs, called features, that describe component functionalities. The protocol for efficiently extracting features from OO code interfaces assumes that methods have consistent and coherent names with respect to the concepts they represent. COOR extracts features from code semiautomatically, because it is not feasible to completely automate the information-extraction process (the process of deriving higher abstractions from lower ones). In our approach, a human expert, or application engineer, maintains the system for an audience of users, or application developers. COOR provides tools for the classification and search for reuse candidates. Our experience with COOR suggests that descriptors can provide several advantages over class interfaces. COOR descriptors support different levels of component classification granularity (like application frameworks rather than single classes). Moreover, in COOR, component behavior description is enhanced due to filtering out linguistic noise by means of a controlled vocabulary.