@inproceedings{rowe98,
title = {Defining Systems Evolvability - A Taxonomy of Change},
address = {Maale Hachamisha, Israel},
author = {David Rowe and John Leaney and David Lowe},
booktitle = {International Conference and Workshop: Engineering of Computer-Based
Systems},
month = {April},
pages = {45+},
publisher = {IEEE Computer Society},
url = {http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/proceedings/ecbs/\&toc=comp/proceedings/ecbs/1998/0001/00/0001toc.xml\&DOI=10.1109/ECBS.1998.10027},
year = {1998},
description = {Not previously uploaded},
abstract = {Evolvability is part of the alchemy of systems engineering. Designing
a system that is evolvable is considered best practice in many industry
domains. However, what does 'evolvable' mean? And in what context
does a system evolve? Reviewing the many factors of system change
and their associated definitions, we conclude that a single definition
for 'evolvability' is not adequate. We assert that evolvability
is a composite quality which allows a system's architecture to accommodate
change in a cost effective manner while maintaining the integrity
of the architecture. In order to define evolvability as a composite,
we propose a taxonomy which classifies the different aspects of
evolvability. Using this taxonomy to select relevant systems architecting
and design approaches, a systems architect can be confident in including
those aspects of evolution most suitable to a particular application.
The concepts introduced in this paper are applied to the Ericsson
AXE telecommunications switching system for illustration and justification},
comment = {- TA168 I197 1998 -
---
- evolution in computer-based systems - architectures must be explictly
designed for change (little evidence for this claim) - notes that
biol. concepts not that applicable. - individuals aren't members
of families - remainder in lit-review document}, citeulike-article-id = {762023}, priority = {0},
keywords = {evolution system taxonomy }
}
::