Previous taxonomies of software change have focused on the purpose
of the change (i.e., the why) rather than the underlying mechanisms.
This paper proposes a taxonomy of software change based on characterizing
the mechanisms of change and the factors that influence these mechanisms.
The ultimate goal of this taxonomy is to provide a framework that
positions concrete tools, formalisms and methods within the domain
of software evolution. Such a framework would considerably ease
comparison between the various mechanisms of change. It would also
allow practitioners to identify and evaluate the relevant tools,
methods and formalisms for a particular change scenario. As an initial
step towards this taxonomy, the paper presents a framework that
can be used to characterize software change support tools and to
identify the factors that impact on the use of these tools. The
framework is evaluated by applying it to three different change
support tools and by comparing these tools based on this analysis.
- important overview and classification, prompts thinking on many
topics - neat idea of defining semantics-preserving changes - the
change many preserve semantics relative to one aspect, e.g. functional,
but not to certain NFRs e.g readability, speed, etc. This would
be cool to visualize or define in a tool
%0 Journal Article
%1 buckley05
%A Buckley, Jim
%A Mens, Tom
%A Zenger, Matthias
%A Rashid, Awais
%A Kniesel, Günter
%B Unanticipated Software Evolution
%D 2005
%E Kniesel, Günter E.
%E Filman, Robert E.
%I Wiley
%J Journal of Software Maintenance and Evolution: Research and Practice
%K evolution software
%N 5
%P 309--332
%R 10.1002/smr.319
%T Towards a taxonomy of software change
%U http://dx.doi.org/10.1002/smr.319
%V 17
%X Previous taxonomies of software change have focused on the purpose
of the change (i.e., the why) rather than the underlying mechanisms.
This paper proposes a taxonomy of software change based on characterizing
the mechanisms of change and the factors that influence these mechanisms.
The ultimate goal of this taxonomy is to provide a framework that
positions concrete tools, formalisms and methods within the domain
of software evolution. Such a framework would considerably ease
comparison between the various mechanisms of change. It would also
allow practitioners to identify and evaluate the relevant tools,
methods and formalisms for a particular change scenario. As an initial
step towards this taxonomy, the paper presents a framework that
can be used to characterize software change support tools and to
identify the factors that impact on the use of these tools. The
framework is evaluated by applying it to three different change
support tools and by comparing these tools based on this analysis.
@article{buckley05,
abstract = {Previous taxonomies of software change have focused on the purpose
of the change (i.e., the why) rather than the underlying mechanisms.
This paper proposes a taxonomy of software change based on characterizing
the mechanisms of change and the factors that influence these mechanisms.
The ultimate goal of this taxonomy is to provide a framework that
positions concrete tools, formalisms and methods within the domain
of software evolution. Such a framework would considerably ease
comparison between the various mechanisms of change. It would also
allow practitioners to identify and evaluate the relevant tools,
methods and formalisms for a particular change scenario. As an initial
step towards this taxonomy, the paper presents a framework that
can be used to characterize software change support tools and to
identify the factors that impact on the use of these tools. The
framework is evaluated by applying it to three different change
support tools and by comparing these tools based on this analysis.},
added-at = {2006-09-18T06:26:07.000+0200},
author = {Buckley, Jim and Mens, Tom and Zenger, Matthias and Rashid, Awais and Kniesel, Günter},
biburl = {https://www.bibsonomy.org/bibtex/240df9b18970860af99306fbe2ca3a1f6/neilernst},
citeulike-article-id = {599030},
comment = {- important overview and classification, prompts thinking on many
topics - neat idea of defining semantics-preserving changes - the
change many preserve semantics relative to one aspect, e.g. functional,
but not to certain NFRs e.g readability, speed, etc. This would
be cool to visualize or define in a tool},
description = {Not previously uploaded},
doi = {10.1002/smr.319},
editor = {Kniesel, Günter E. and Filman, Robert E.},
interhash = {c8dd01b9c3e06abd524a5f622a91f509},
intrahash = {40df9b18970860af99306fbe2ca3a1f6},
journal = {Journal of Software Maintenance and Evolution: Research and Practice},
keywords = {evolution software},
month = {September},
number = 5,
pages = {309--332},
priority = {0},
publisher = {Wiley},
series = {Unanticipated Software Evolution},
timestamp = {2006-09-18T06:26:07.000+0200},
title = {Towards a taxonomy of software change},
url = {http://dx.doi.org/10.1002/smr.319},
volume = 17,
year = 2005
}