Home > Research > Publications & Outputs > Software reclamation

Research

Links

Text available via DOI:

Keywords

View graph of relations

Software reclamation

Research output: Contribution to Journal/Magazine › Journal article › peer-review

Published

Standard

Software reclamation. / Garnett, E. S.; Mariani, J. A.
In: Software Engineering Journal, Vol. 5, No. 3, 05.1990, p. 185-191.

Research output: Contribution to Journal/Magazine › Journal article › peer-review

Harvard

Garnett, ES & Mariani, JA 1990, 'Software reclamation', Software Engineering Journal, vol. 5, no. 3, pp. 185-191. https://doi.org/10.1049/sej.1990.0021

APA

Garnett, E. S., & Mariani, J. A. (1990). Software reclamation. Software Engineering Journal, 5(3), 185-191. https://doi.org/10.1049/sej.1990.0021

Vancouver

Garnett ES, Mariani JA. Software reclamation. Software Engineering Journal. 1990 May;5(3):185-191. doi: 10.1049/sej.1990.0021

Author

Garnett, E. S. ; Mariani, J. A. / Software reclamation. In: Software Engineering Journal. 1990 ; Vol. 5, No. 3. pp. 185-191.

Bibtex

@article{c36b5ea9b4594bfc897650c0d3706c8c,
title = "Software reclamation",
abstract = "One of the major barriers to the introduction of reuse technology into the software development process is the absence of large repositories of reusable components from which manufacturers can build new generations of systems [1,2]. Owing to the tremendous investment that has been made in developing systems, companies use an evolutionary approach to software development whereby the old software development whereby the old version becomes the basis of the next generation. Owing to such costs, companies are understandably reluctant to develop completely new versions from scratch. If software reusability is to emerge as a discipline, then some mechanism whereby components are reclaimed from existing systems and transformed according to reuse cirteria must be found. This paper discusses an approach designed to reclaim software components from existing systems and transform them into objects, which we contend are inherently more reusable.",
keywords = "software reusability, reusable components , software reclamation , reuse criteria , reuse technology , evolutionary approach , software development process , old version",
author = "Garnett, {E. S.} and Mariani, {J. A.}",
year = "1990",
month = may,
doi = "10.1049/sej.1990.0021",
language = "English",
volume = "5",
pages = "185--191",
journal = "Software Engineering Journal",
issn = "0268-6961",
publisher = "Institute of Electrical Engineers",
number = "3",

}

RIS

TY - JOUR

T1 - Software reclamation

AU - Garnett, E. S.

AU - Mariani, J. A.

PY - 1990/5

Y1 - 1990/5

N2 - One of the major barriers to the introduction of reuse technology into the software development process is the absence of large repositories of reusable components from which manufacturers can build new generations of systems [1,2]. Owing to the tremendous investment that has been made in developing systems, companies use an evolutionary approach to software development whereby the old software development whereby the old version becomes the basis of the next generation. Owing to such costs, companies are understandably reluctant to develop completely new versions from scratch. If software reusability is to emerge as a discipline, then some mechanism whereby components are reclaimed from existing systems and transformed according to reuse cirteria must be found. This paper discusses an approach designed to reclaim software components from existing systems and transform them into objects, which we contend are inherently more reusable.

AB - One of the major barriers to the introduction of reuse technology into the software development process is the absence of large repositories of reusable components from which manufacturers can build new generations of systems [1,2]. Owing to the tremendous investment that has been made in developing systems, companies use an evolutionary approach to software development whereby the old software development whereby the old version becomes the basis of the next generation. Owing to such costs, companies are understandably reluctant to develop completely new versions from scratch. If software reusability is to emerge as a discipline, then some mechanism whereby components are reclaimed from existing systems and transformed according to reuse cirteria must be found. This paper discusses an approach designed to reclaim software components from existing systems and transform them into objects, which we contend are inherently more reusable.

KW - software reusability

KW - reusable components

KW - software reclamation

KW - reuse criteria

KW - reuse technology

KW - evolutionary approach

KW - software development process

KW - old version

U2 - 10.1049/sej.1990.0021

DO - 10.1049/sej.1990.0021

M3 - Journal article

VL - 5

SP - 185

EP - 191

JO - Software Engineering Journal

JF - Software Engineering Journal

SN - 0268-6961

IS - 3

ER -