* In addition to the dynamic nature of software while executing, this dynamism extends to the evolution of the software's code itself. The software's evolution is often captured in its entirety by revision-control systems (such as CVS, Subversion, and Git). By utilizing this rich artifact, as well as other historical artifacts (e.g., bug-tracking systems and mailing lists), we can offer a number of techniques for recommending future actions to developers. We have developed techniques that utilize these artifacts to enable developers to view selected code lineage and suggest developer assignments for future and present development tasks.

* Chronos: Visualizing Slices of Source-Code History.
Francisco Servant, James A. Jones. 1st IEEE Working Conference on Software Visualization, Tool Track (VISSOFT-Tool), Eindhoven, Netherlands, September 2013, pp. 1–4.
[Abstract] [BibTex] [Publisher] [PDF]

* History Slicing: Assisting Code-Evolution Tasks.
Francisco Servant, James A. Jones. 20th International Symposium on the Foundations of Software Engineering (FSE), Cary, North Carolina, USA, November 2012, pp. 43:1–43:11.
[Abstract] [BibTex] [Publisher] [PDF]

* WhoseFault: Automatic Developer-to-Fault Assignment Through Fault Localization.
Francisco Servant, James A. Jones. 34th International Conference on Software Engineering (ICSE), Zurich, Switzerland, June 2012, pp. 36–46.
[Abstract] [BibTex] [Publisher] [PDF]

* Trendy Bugs: Topic Trends in the Android Bug Reports.
Lee Martie, Vijay Krishna Palepu, Hitesh Sajnani, Cristina Lopes. 9th IEEE Working Conference on Mining Software Repositories (MSR), Mining Challenge Short Paper Track, Zurich, Switzerland, June 2012, pp. 120–123.
[Abstract] [BibTex] [Publisher] [PDF]

* History Slicing.
Francisco Servant, James A. Jones. Proceedings of the 26th IEEE/ACM International Conference on Automated Software Engineering (ASE), Short paper track, Lawrence, Kansas, USA, November 2011, pp. 452–455.
[Abstract] [BibTex] [PDF]