Added a little bit more about find references and removed analyze dependencies for space. Hopefully will stave off #110

Author: jssmith1

progNav Paper/progNav Paper.tex

@@ -163,23 +163,23 @@ \section{Design Principles}
 \section{Related Work}
 %Summary of related work, including a table evaluating existing %tools on various design principles.
 %Spoiler alert, none of the tools satisfy all of the principles.
-Here we discuss many of the various existing tools that help developers explore and navigate code. We also relate the exiting tools back to Design Principles Described in Section \ref{DesignPrinciples}.
+Here we discuss some of the existing tools that help developers navigate code. We also relate the exiting tools back to Design Principles Described in Section \ref{DesignPrinciples}.
 
-Many modern IDEs provide tools that help developers navigate through their code. 
+Many modern IDEs provide tools that help developers navigate source code. 
 For example, Eclipse~\cite{Eclipse} includes \emph{Call Hierarchy} and \emph{Find References}. 
-When users invoke \emph{Call Hierarchy}, Eclipse opens a new view that displays the callers and callees for a selected method.  
-IntelliJ~\cite{IntelliJ} also provides navigation tools, namely \emph{Analyze Data Flow To/From Here} and \emph{Analyze Dependencies}.
-Much like Eclipse's \emph{Call Hierarchy}, the \emph{Analyze Data Flow} tools display their results in external views. 
-These tools provide \textit{Program Analysis} for users to navigate throughout the entirety of a project. 
+When users invoke either of these tools, Eclipse opens a new view to display the results.
+For \emph{Call Hierarchy}, this view contains a list of the selected method's callers and callees, whereas \emph{Find References} only lists callers.
+Similarly, IntelliJ~\cite{IntelliJ} provides \emph{Analyze Data Flow}, which also displays its results in an external view.
+These tools provide \textit{Program Analysis} for users to navigate throughout their code. 
 However, they generally differ from Flower because they lack \textit{Low Barriers to Invocation} and \textit{In Situ Navigation}.
 
 There are also several tools that reside strictly within the code editor, enabling a form of \textit{In Situ Navigation}.
 Two examples of these tools are Eclipse's \emph{Mark Occurrences} and \emph{Open Declaration}. 
 Eclipse automatically invokes \emph{Mark Occurrences} whenever a user clicks on a variable or method name in the code.
 The tool then highlights occurrences of that element elsewhere in the current file.
 \emph{Mark Occurrences} epitomizes \textit{Low Barriers to Invocation}.
-These approaches are similar to Flower  in that they display the results within the editor rather than a separate view or panel.
-However, they do not provide \textit{Program Analysis} or enable \textit{Full Program Navigation}.
+These approaches are similar to Flower in that they display the results within the editor rather than a separate view or panel.
+However, they do not perform \textit{Program Analysis} or enable \textit{Full Program Navigation}.
 
 
 Many other tools help developers navigate code by representing the code graphically and allowing developers to navigate those graphs~\cite{CodeBubbles,CodeCanvas,CodeSurfer,Dora,Reacher,Relo,Whyline}.