Software reuse by specialization of generic procedures through views

Novak, Jr. Gordon S.

doi:10.1109/32.605759

Cited by 30 publications

(9 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Past research has defined software reuse broadly and has identified several assets associated with software as candidates for reuse: reuse of processes by which software is created and manipulated [1], reuse of technical personnel across projects [2], reuse of design objects [3], [49], [55], reuse of design histories [4], reuse of generic procedures and views [50], reuse of functions [48], and reuse of subroutine implementations [5], among others. Proposed infrastructure for reuse of software assets has been embodied in various approaches [6], [42], [44], [52], [53].…”

Section: Introductionmentioning

confidence: 99%

Enabling reuse-based software development of large-scale systems

Selby

2005

IIEEE Trans. Software Eng.

126

105

View full text Add to dashboard Cite

Abstract-Software reuse enables developers to leverage past accomplishments and facilitates significant improvements in software productivity and quality. Software reuse catalyzes improvements in productivity by avoiding redevelopment and improvements in quality by incorporating components whose reliability has already been established. This study addresses a pivotal research issue that underlies software reuse-what factors characterize successful software reuse in large-scale systems? The research approach is to investigate, analyze, and evaluate software reuse empirically by mining software repositories from a NASA software development environment that actively reuses software. This software environment successfully follows principles of reuse-based software development in order to achieve an average reuse of 32 percent per project, which is the average amount of software either reused or modified from previous systems. We examine the repositories for 25 software systems ranging from 3,000 to 112,000 source lines from this software environment. We analyze four classes of software modules: modules reused without revision, modules reused with slight revision (< 25 percent revision), modules reused with major revision ( 25 percent revision), and newly developed modules. We apply nonparametric statistical models to compare numerous development variables across the 2,954 software modules in the systems. We identify two categories of factors that characterize successful reuse-based software development of large-scale systems: module design factors and module implementation factors. We also evaluate the fault rates of the reused, modified, and newly developed modules. The module design factors that characterize module reuse without revision were (after normalization by size in source lines): few calls to other system modules, many calls to utility functions, few input-output parameters, few reads and writes, and many comments. The module implementation factors that characterize module reuse without revision were small size in source lines and (after normalization by size in source lines): low development effort and many assignment statements. The modules reused without revision had the fewest faults, fewest faults per source line, and lowest fault correction effort. The modules reused with major revision had the highest fault correction effort and highest fault isolation effort as well as the most changes, most changes per source line, and highest change correction effort. In conclusion, we outline future research directions that build on these software reuse ideas and strategies.

show abstract

Section: Introductionmentioning

confidence: 99%

Enabling reuse-based software development of large-scale systems

Selby

2005

IIEEE Trans. Software Eng.

126

105

View full text Add to dashboard Cite

show abstract

“…A candidate consists of the executable binaries, but also the source code and additional documentation 67 The structure of the CBR is coarse grained with respect to equivalent signatures. Signatures are generalized in the sense of the type view technique presented in [8] and are embodied as abstract signatures without implementation details. The library is divided into partitions containing components conforming to a generalized signature Ci.…”

Section: Behavior Based Classificationmentioning

confidence: 99%

Support of semantics recovery during code scavenging using repository classification

Pozewaunig

Rauner-Reithmayer

1999

Proceedings of the 1999 Symposium on Software Reusability

View full text Add to dashboard Cite

One of the hardest tasks to be fulfilled during the analysis of legacy systems is how to determine the precise semantics of program components. Investigating the internal data and control structures is difficult due to the huge number of possible implementation variants for the same problem.To facilitate the task we propose to use components kept and described in a repository of reusable concepts as reference points. This becomes possible when behavior sampling is used as classification/retrieval strategy. In matching the results of isolated components from a legacy system against already executed components in a repository, one can tackle the problem of classifying legacy components without considering there internal structure. As a side effect, the population of the reuse repository is increased.In this paper we propose a model to reuse the knowledge containd in a behavior based reuse repository for analyzing, classifying and understanding isolated executable components from a legacy system. Components not yet classfied will augment the repository. MOTIVATIONOne of the main topics in software reengineering is the task of analyzing parts of the system in order to (re)detect the functionality and meaning of such fragments. A broad range of methods for identifying, understanding, classifyCopyright ACM 11999 I-581 13-lOl-1/99/05...$5.00 65 ing, redocumenting, and reengineering program components in legacy systems has been proposed in the literature. Most of these methods can be applied very successtily, if a-priori knowledge about program structure and programming style is available. As a consequence, if these assumptions do not hold, structure based analysis techniques must fail.In contrast, to classify assets for the purpose of software reuse, extensive documentation is available to fulfill this task. But here the problem of correct interpretation of describing keywords arises. Since interpretation of keywords depends heavily on the cultural, social, and personal context [3, 11, successfiJ classification depends on many human factors. To overcome such obstacles, researchers work on questions such as how to describe software without relying on human interpretation. Many approaches deal with formalizing the properties of component interfaces [6, 191 or using the inherent property of executabilty to directly determine meaning from software attributes.Part of our motivation for the work described in this paper stems from a project to develop a reengineering tool [ 181.Here, we were faced with the problem to perform semantics preserving code transformations. In quite a number of cases, this re-juvenation of code would be better performed by replacing parts of this code (a chunk) by some semantically equivalent component written according to state-ofthe-art programming practices. Linking reengineering techniques with reuse experience seems promising in this situation. Thus, we were looking for domain specific components either as reference points or even as candidates for substitution of pieces of legacy code. As stat...

show abstract

“…Previous model base structures include the OO (ObjectOriented) models (Lenard, 1993;Novak, 1997;Rumbaugh et al, 1991), the frame structure model (Dolk and Konsynski, 1984), the network and relational models (Blanning, 1993), the knowledge-based structure model (Yau and Tsai, 1987), and the modelling language representation model (Hong et al, 1993). The OO models support a class-based inheritance, which facilitates the incremental definition of models and reuse of models.…”

Section: Introductionmentioning

confidence: 99%

Semantic component networking: Toward the synergy of static reuse and dynamic clustering of resources in the knowledge grid

Zhuge

2006

Journal of Systems and Software

View full text Add to dashboard Cite

Software reuse by specialization of generic procedures through views

Cited by 30 publications

References 44 publications

Enabling reuse-based software development of large-scale systems

Enabling reuse-based software development of large-scale systems

Support of semantics recovery during code scavenging using repository classification

Semantic component networking: Toward the synergy of static reuse and dynamic clustering of resources in the knowledge grid

Contact Info

Product

Resources

About