Following last three years' RAM-SE (Reflection, AOP and Meta-Data for Software Evolution) workshop at the ECOOP conference, the RAM-SE'07 workshop was a successful and po...
Manuel Oriol, Walter Cazzola, Shigeru Chiba, Gunte...
Software evolution is usually considered in terms of corrections, improvements and enhancements. While helpful, this approach does not take into account the fundamental dimensions...
Huge size and high complexity of legacy software are the main sources of today's software evolution problems. While we can ease software evolution with re-engineering tools, ...
Industrial software projects are not based on a top-down development process relying on refinement but use a more iterative and incremental approach with respect to changing requ...
It has long been accepted that requirements analysis should precede architectural design and implementation, but in software evolution and reverse engineering this concern with bl...
Software systems evolve over time. Currently we do not do a good job of documenting this evolution. This essay discusses the need to better document software evolution and introdu...
During software evolution, several different facets of the system need to be related to one another at multiple levbstraction. Current software evolution tools have limited capabi...
A number of interesting phenomena can be observed when lifelong processes of object-oriented software are analyzed from the viewpoint of software evolution. This paper proposes a ...
It is shown how software metrics and architectural patterns can be used for the management of software evolution. In the presented architecture-centric software evolutionmethod th...
Juha Gustafsson, Jukka Paakki, Lilli Nenonen, A. I...
Automating software evolution requires both identifying precisely the affected program points and selecting the appropriate modification at each point. This task is particularly ...