Tracking dependencies between code changes: ...
Document type :
Communication dans un congrès avec actes
Title :
Tracking dependencies between code changes: An incremental approach
Author(s) :
Godoy, Lucas [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Cassou, Damien [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Cassou, Damien [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Ducasse, Stephane [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Conference title :
IWST 2014
City :
Cambridge
Country :
Royaume-Uni
Start date of the conference :
2014-08-18
English keyword(s) :
software evolution
change propagation
IDE
history
dependency analy-sis
change propagation
IDE
history
dependency analy-sis
HAL domain(s) :
Informatique [cs]/Langage de programmation [cs.PL]
Informatique [cs]/Algorithme et structure de données [cs.DS]
Informatique [cs]/Algorithme et structure de données [cs.DS]
English abstract : [en]
Merging a change often leads to the question of knowing what are the dependencies to other changes that should be merged too to obtain a working system. This question also arises with code history trackers – Code history ...
Show more >Merging a change often leads to the question of knowing what are the dependencies to other changes that should be merged too to obtain a working system. This question also arises with code history trackers – Code history trackers are tools that react to what the developer do by creating first-class objects that represent the change made to the system. In this paper, we evaluate the capacity of different code history trackers to represent, also as first-class objects, the dependencies between those changes. We also present a representation for dependencies that works with the event model of Epicea, a fine-grained and incremental code history tracker.Show less >
Show more >Merging a change often leads to the question of knowing what are the dependencies to other changes that should be merged too to obtain a working system. This question also arises with code history trackers – Code history trackers are tools that react to what the developer do by creating first-class objects that represent the change made to the system. In this paper, we evaluate the capacity of different code history trackers to represent, also as first-class objects, the dependencies between those changes. We also present a representation for dependencies that works with the event model of Epicea, a fine-grained and incremental code history tracker.Show less >
Language :
Anglais
Peer reviewed article :
Oui
Audience :
Internationale
Popular science :
Non
Collections :
Source :
Files
- https://hal.archives-ouvertes.fr/hal-01076238/document
- Open access
- Access the document
- https://hal.archives-ouvertes.fr/hal-01076238/document
- Open access
- Access the document
- document
- Open access
- Access the document
- iwst-tracking.pdf
- Open access
- Access the document
- document
- Open access
- Access the document
- iwst-tracking.pdf
- Open access
- Access the document