Does the propagation of artifact changes across tasks reflect work dependencies?

Abstract

Developers commonly define tasks to help coordinate software development efforts---whether they be feature implementation, refactoring, or bug fixes. Developers establish links between tasks to express implicit dependencies that needs explicit handling---dependencies that often require the developers responsible for a given task to assess how changes in a linked task affect their own work and vice versa (i.e., change propagation). While seemingly useful, it is unknown if change propagation indeed coincides with task links.

BibTeX

@inproceedings{MayrDorn-Egyed:ICSE18,
  author    = {Christoph Mayr{-}Dorn and
               Alexander Egyed},
  title     = {Does the propagation of artifact changes across tasks reflect work dependencies?},
  booktitle = {ICSE},
  pages     = {397--407},
  publisher = {{ACM}},
  year      = {2018},
}

Does the propagation of artifact changes across tasks reflect work dependencies?

Abstract

Related papers