The histories of software systems hold useful information when reasoning about the systems at hand or about general laws of software evolution. Yet, the approaches developed so far, do not rely on an explicit meta-model and do not facilitate the comparison of different evolutions. We argue for the need to define history as a first class entity and propose a meta-model centered around the notion of history. We show the usefulness of our a meta-model by discussing the different analysis it enables
Abstract. The analysis of the evolution of software systems is a useful source of information for a ...
Previous taxonomies of software evolution have focused on the purpose of the change rather than the ...
Software change histories are results of incremental updates made by developers. As a byproduct of t...
AbstractThe histories of software systems hold useful information when reasoning about the systems a...
The histories of software systems hold useful information when reasoning about the systems at hand o...
The histories of software systems hold useful information when reasoning about the systems at hand o...
Over the past three decades, more and more research has been spent on understanding software evoluti...
Understanding how software systems evolve is useful from different perspectives: reverse engineering...
AbstractUnderstanding how software systems evolve is useful from different perspectives: reverse eng...
Analyzing historical information can show how a software system evolved into its current state, whic...
During a software project's lifetime, the software goes through many changes, as components are adde...
Analyzing historical information can show how a software system evolved into its current state, whic...
Legacy software systems correspond to the wealth of the companies. They often exist for dozens of ye...
Software analysis and its diachronic sibling, software evolution analysis, rely heavily on data comp...
Analyzing historical information can show how a software system evolved into its current state, but ...
Abstract. The analysis of the evolution of software systems is a useful source of information for a ...
Previous taxonomies of software evolution have focused on the purpose of the change rather than the ...
Software change histories are results of incremental updates made by developers. As a byproduct of t...
AbstractThe histories of software systems hold useful information when reasoning about the systems a...
The histories of software systems hold useful information when reasoning about the systems at hand o...
The histories of software systems hold useful information when reasoning about the systems at hand o...
Over the past three decades, more and more research has been spent on understanding software evoluti...
Understanding how software systems evolve is useful from different perspectives: reverse engineering...
AbstractUnderstanding how software systems evolve is useful from different perspectives: reverse eng...
Analyzing historical information can show how a software system evolved into its current state, whic...
During a software project's lifetime, the software goes through many changes, as components are adde...
Analyzing historical information can show how a software system evolved into its current state, whic...
Legacy software systems correspond to the wealth of the companies. They often exist for dozens of ye...
Software analysis and its diachronic sibling, software evolution analysis, rely heavily on data comp...
Analyzing historical information can show how a software system evolved into its current state, but ...
Abstract. The analysis of the evolution of software systems is a useful source of information for a ...
Previous taxonomies of software evolution have focused on the purpose of the change rather than the ...
Software change histories are results of incremental updates made by developers. As a byproduct of t...