Making offline analyses continuous

Kivanç Muslu, Yuriy Brun, Michael D. Ernst, David Notkin

Abstract

Developers use analysis tools to help write, debug, and understand software systems under development. A developer's change to the system source code may affect analysis results. Typically, to learn those effects, the developer must explicitly initiate the analysis. This may interrupt the developer's workflow and/or the delay until the developer learns the implications of the change. The situation is even worse for impure analyses — ones that modify the code on which it runs — because such analyses block the developer from working on the code.

BibTeX

@inproceedings{Muslu-al:FSE13,
  author    = {Kivan{\c{c}} Muslu and
               Yuriy Brun and
               Michael D. Ernst and
               David Notkin},
  title     = {Making offline analyses continuous},
  booktitle = {{ESEC/SIGSOFT} {FSE}},
  pages     = {323--333},
  publisher = {{ACM}},
  year      = {2013},
}

Making offline analyses continuous

Abstract

Related papers