Add citation to intro. Fixes #115

Author: Justin S. Smith

progNav Paper/progNav Paper.tex

@@ -86,6 +86,7 @@ \section{Introduction}
 In general, evaluations have demonstrated the effectiveness of such tools ~\cite{Reacher,Whyline,Relo,Stacksplorer}.
 
 However, these tools rely on cumbersome user interface widgets that new users might struggle to understand and occupy valuable screen real estate.
+In general, the need for better navigation tools has been well-reported~\cite{ko2006seekInfo}.
 We present a tool, Flower (pronounced flow-er), that represents a minimalistic approach to program navigation.
 Flower  leverages program analysis techniques, leans on relatively few cumbersome interface elements, and presents its results integrated within the code.
 %Existing tools feature many cumbersome UI widgets or seem poorly integrated into the IDE.

progNav Paper/progNavPaper.bib

@@ -15,6 +15,19 @@ @inproceedings{Smith2015
 	keywords = {Developer questions, human factors, security, static analysis},
 } 
 
+@ARTICLE{ko2006seekInfo, 
+	author={A. J. Ko and B. A. Myers and M. J. Coblenz and H. H. Aung}, 
+	journal={IEEE Transactions on Software Engineering}, 
+	title={An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks}, 
+	year={2006}, 
+	volume={32}, 
+	number={12}, 
+	pages={971-987}, 
+	keywords={program debugging;software maintenance;Eclipse package explorer;debugging task;file tabs;information foraging;program understanding;scroll bars;search tool;software development environment;software maintenance tasks;source files;Bars;Debugging;Encoding;Navigation;Packaging;Performance gain;Programming;Software engineering;Software maintenance;Software tools;Program investigation;empirical software engineering;information foraging;information scent.;program comprehension;program understanding}, 
+	doi={10.1109/TSE.2006.116}, 
+	ISSN={0098-5589}, 
+	month={Dec},}
+
 
 @inproceedings{latoza2010hard,
 	title={Hard-to-answer questions about code},