About: Reusability is a research topic. Over the lifetime, 2908 publications have been published within this topic receiving 34626 citations.
Papers published on a yearly basis
16 May 1999
TL;DR: A new paradigm for modeling and implementing software artifacts is described, one that permits separation of overlapping concerns along multiple dimensions of composition and decomposition, which addresses numerous problems throughout the software lifecycle.
Abstract: Done well, separation of concerns can provide many software engineering benefits, including reduced complexity, improved reusability, and simpler evolution. The choice of boundaries for separate concerns depends on both requirements on the system and on the kind(s) of decomposition and composition a given formalism supports. The predominant methodologies and formalisms available, however, support only orthogonal separations of concerns, along single dimensions of composition and decomposition. These characteristics lead to a number of well-known and difficult problems. The paper describes a new paradigm for modeling and implementing software artifacts, one that permits separation of overlapping concerns along multiple dimensions of composition and decomposition. This approach addresses numerous problems throughout the software lifecycle in achieving well-engineered, evolvable, flexible software artifacts and traceability across artifacts.
TL;DR: The faceted scheme described here is a partial solution to the classification and retrieval problem of software component reuse.
Abstract: To reuse a software component, you first have to find it. The faceted scheme described here is a partial solution to this classification and retrieval problem.
••21 May 1994
TL;DR: A five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method) is proposed and illustrated by analyzing three separate user interface architectures with respect to the quality of modifiability.
Abstract: While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns -software quality concerns such as maintainability portability, modularity, reusability, and so forth. We address these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability. >
•15 Nov 2001
TL;DR: The KobrA method is described, which supports a model-driven, UML-based representation of components, and a product line approach to their development and evolution, and allows the reusability of components to be significantly enhanced.
Abstract: Component-based development promises to revolutionize the way in which software is developed and maintained. However, contemporary component technologies, such as COM+/.NET, EJB/J2EE and CORBA, only support components in the final, implementation-oriented stages of development, leaving the earlier stages of analysis and design to be organized in largely traditional, non-component oriented ways. This book describes the KobrA method, which supports a model-driven, UML-based representation of components, and a product line approach to their development and evolution. This enables the benefits of component-based development to be realized throughout the software life-cycle, and allows the reusability of components to be significantly enhanced.
03 Jan 1988
TL;DR: In this article, the authors discuss some answers and possibilities for the reusability of the Internet and discuss the challenges involved in finding the solution to the problem of reusabilities.
Abstract: Reusability remains a puzzle despite its promise. Why? What can be done? The authors discuss some answers and possibilities.
Trending Questions (10)