Organisational considerations for software reuse

  • Authors:

  • Andy Lynex;Paul J. Layzell

  • Affiliations:

  • Software Management Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QD, UK E-mail: andy.lynex@umist.ac.uk;Software Management Group, Department of Computation, UMIST, P.O. Box 88, Manchester M60 1QD, UK E-mail: andy.lynex@umist.ac.uk

  • Venue:
  • Annals of Software Engineering
  • Year:
  • 1998

Quantified Score

Hi-index 0.00

Visualization

Abstract

Reuse is widely promoted as one of the most promising methods for increasing productivity and quality within software development. Until recently most research into strategies for systematic reuse has focused on solution of the technical issues. Now as companies (mostly IT focused) implement the strategies developed, they find there are other issues which hold back their success, somewhat unrelated to the technical solutions offered. Reuse processes are not simple technologies and methods slotted into a development, like the transition in design notation from traditional approaches to an object‐orientated method. Whereas technology changes involve retraining developers. Reuse requires the whole organisation and funding of development to be revised. If the magnitude of change involved in transitioning an IT organisation is so encompassing, where does this leave the rest of industry which is increasingly reliant on software to support their business process? This paper looks at organisational and management issues raised by the introduction of software reuse to the development process. We identify inhibitors of reuse adoption, look at causes of these and suggest possible solutions. We aim to concisely present all those non‐technical issues that should be considered when introducing a reuse program. Considered also is how these issues affect companies which have IT in only a business support capacity, making this paper relevant throughout industry.