A reuse triplet for systematic software reuse

Authors:
Ezra K. Mugisa
Affiliations:
Department of Computing, Imperial College of Science, Technology and Medicine, London SW7 2BZ, UK
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
1997

Citing 10
Cited 0

Life with UNIX: a guide for everyone

Life with UNIX: a guide for everyone
Draco: a method for engineering reusable software systems

Software reusability: vol. 1, concepts and models
Reusable software components

Advances in computers
Software reuse

ACM Computing Surveys (CSUR)
Confessions of a used program salesman: institutionalizing software reuse

Confessions of a used program salesman: institutionalizing software reuse
Architectural issues in software reuse: it's not just the functionality, it's the packaging

SSR '95 Proceedings of the 1995 Symposium on Software reusability
The UNIX time-sharing system

Communications of the ACM
Domain analysis: an introduction

ACM SIGSOFT Software Engineering Notes
Domain Analysis and Software Systems Modeling

Domain Analysis and Software Systems Modeling
Status Report: Software Reusability

IEEE Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

We present the view that for systematic software reuse (SSR) to happen we need a reuse software architecture (RSA) as the invariant base and a collection of reuse software components (RSCs) as the pluggable variant part of a family of architecturally similar software systems. We shall identify a reuse situation with a RSA, RSCs and a plugging operator. SSR is then presented as a case of plugging a collection of RSCs into the appropriate RSA. We apply this view of reuse to a number of reuse cases and find evidence that for reuse to be successful we need simple, clear and easily pluggable RSAs and RSCs.