Assessing software libraries by browsing similar classes, functions and relationships

Abstract

Comparing and contrasting a set of software libraries is useful for reuse related activities such as selecting a library from among several candidates or porting an application from one library to another. The current state of the art in assessing libraries relies on qualitative methods.To reduce costs and/or assess a large collection of libraries, automation is necessary. Although there are tools that help a developer examine an individual library in terms of architecture, style, etc., we know of no tools that help the developer directly compare several libraries. With existing tools, the user must manually integrate the knowledge learned about each library.Automation to help developers directly compare and contrast libraries requires matching of similar components (such as classes and functions) across libraries. This is different than the traditional component retrieval problem in which components are returned that best match a user's query. Rather, we need to find those components that are similar across the libraries under consideration. In this paper, we show how this kind of matching can be done.

Retrieving Software Components Using Directed Replaceability Distance

“…As conventional methods, we use Spanoudakis's similarity method ([SC94] [7]) and Michail's similarity method ([MN99] [5]). Both methods are similar to our method in that their preparation costs are extremely low.…”

“…This approach is effective in the case that all source codes of the components are available. However, in the case that the source codes are not available, as assumed in this paper, the extracted information is insufficient for the retrieval [5].…”

“…There are two major approaches in the similarity evaluation method: an approach using the class inheritance relation in OO language [7] and an approach using the similarity of element names (names of interfaces, etc.) [5]. The user's queries are given by a prototype of the component which satisfies the user's requirement.…”

“…The retrieval mechanism should be able to consider two or more characteristics simultaneously when retrieving. In addition, not all components circulated over the Internet have additional specification descriptions [5]. Therefore, the retrieval mechanism should not require any additional information other than the components themselves.…”

A Retrieval Technique for Software Components Using Directed Replaceability Similarity

“…When source codes are not available, the extracted information is insufficient for the retrieval [5].…”