R. Balzer. International Workshop on Principles of Software Evolution, page 57--58. (2003)
Abstract
Rather than being a major (and uncontrollable) source of instability
to a COTS extension, upgrades of COTS products - over a ten year
period - have produced little or no impact on our extensions. We
hypothesize that this evolution stability is not an accident, but
rather the result of the architectures in which those extensions
were developed.
International Workshop on Principles of Software Evolution
year
2003
journal
Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of
pages
57--58
comment
- suggests that COTS integration isn't that bad for managing evolution,
since most evolution happens at the edges of an application model
(e.g. new features don't affect previous ones)
%0 Conference Paper
%1 baltzer03c
%A Balzer, R.
%B International Workshop on Principles of Software Evolution
%D 2003
%J Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of
%K evolution software
%P 57--58
%T Evolution stability through COTS integration
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1231210
%X Rather than being a major (and uncontrollable) source of instability
to a COTS extension, upgrades of COTS products - over a ten year
period - have produced little or no impact on our extensions. We
hypothesize that this evolution stability is not an accident, but
rather the result of the architectures in which those extensions
were developed.
@inproceedings{baltzer03c,
abstract = {Rather than being a major (and uncontrollable) source of instability
to a COTS extension, upgrades of COTS products - over a ten year
period - have produced little or no impact on our extensions. We
hypothesize that this evolution stability is not an accident, but
rather the result of the architectures in which those extensions
were developed.},
added-at = {2006-09-18T06:26:07.000+0200},
author = {Balzer, R.},
biburl = {https://www.bibsonomy.org/bibtex/2af2b83b9bb998bbf6c30147252e55744/neilernst},
booktitle = {International Workshop on Principles of Software Evolution},
citeulike-article-id = {638224},
comment = {- suggests that COTS integration isn't that bad for managing evolution,
since most evolution happens at the edges of an application model
(e.g. new features don't affect previous ones)},
description = {Not previously uploaded},
interhash = {08ba4f6fb27eec19b60f63a4572dfa67},
intrahash = {af2b83b9bb998bbf6c30147252e55744},
journal = {Software Evolution, 2003. Proceedings. Sixth International Workshop
on Principles of},
keywords = {evolution software},
pages = {57--58},
priority = {0},
timestamp = {2006-09-18T06:26:07.000+0200},
title = {Evolution stability through COTS integration},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1231210},
year = 2003
}