A Change-based Approach to Software Evolution
MetadataShow full item record
Software evolution research is limited by the amount of information available to researchers: Current version control tools do not store all the information generated by developers. They do not record every intermediate version of the system issued, but only snapshots taken when a developer commits source code into the repository. Additionally, most software evolution analysis tools are not a part of the day-to-day programming activities, because analysis tools are resource intensive and not integrated in development environments. We propose to model development information as change operations that we retrieve directly from the programming environment the developers are using, while they are effecting changes to the system. This accurate and incremental information opens new ways for both developers and researchers to explore and evolve complex systems.
Showing items related by title, author, creator and subject.
Jermakovics, A; Moser, R; Sillitti, A; Succi, G (ACM Press, 2008)Lagrein is a tool that allows exploring how a software system has been developed. It supports visualization of multiple metrics, it links requirements to code expected to implement them and cou-ples code with the effort ...
Jamshidi, P; Ghafari, M; Aakash, A; Pahl, C (IEEE, 2013)Architecture-centric software evolution (ACSE) supports frequent business and technical change cycles in software at higher abstraction levels. This requires evolution in system structure and behavior that could be modeled, ...
Ahmad, A; Jamshidi, P; Pahl, C (2013)Software systems continuously evolve as a consequence of frequent changes in their functional requirements and the environment surrounding them. Architecture-centric software evolution (ACSE) enables changes in software ...