WIP - Progress Report

progress_report/progress_report.tex

@@ -125,25 +125,61 @@ causing problems later down the line. If we only found these bugs by using
 the frontend, they would have been much harder to debug, as there would have
 been much more code to work through.
 \section{Progress}
-\section{Recommendations}
+We are nearing completion on the virtual machine upon which the debugger will
+run. Moving forward, the front end team will polish the existing interface, and
+expand it to control the debugger. The back end team will work on the core
+functionality of the debugger and continue to fix bugs with the virtual machine.
+This places us two weeks behind schedule over all, as we planned to have the
+virtual machine finished by April 1\textsuperscript{st}.
+\subsection*{Front End: Status}
+The front end team is keeping pace with the back end team, but is still two
+weeks behind schedule. We have a working interface where users can input,
+compile, and run C0 programs, but there are no debugging features.
+\subsection*{Front End: Projections}
+We will modify our schedule to allow more time for the work on the debugger.
+This time will come from a shortened user testing and revision period. That
+said, because of our thorough work on the virtual machine, implementing the
+debugger should progress more rapidly than originally planned. The modified
+schedule is depicted in our updated Gannt chart (Figure \ref{fig:new-gantt}).
+\subsection*{Back End: Status}
+The back end team is also two weeks behind schedule. The virtual machine, along
+with most library functions needed to run programs, is complete and working
+well. The team has started working on stepping through program execution, but
+those features have not yet been incorporated with the rest of the application.
+\subsection*{Back End: Projections}
+In the coming time, the back end team will implement the remaining library
+functions, then transition all of their efforts to the debugging features. Like
+the front end team, this transition was originally scheduled for
+April\textsuperscript{st}, but will now occur in the next week.
 \begin{figure}[h]
   \centering
-  \includegraphics[width=\linewidth]{old-gantt.jpg}
+  \includegraphics[width=\linewidth]{old-gantt.png}
   \caption{Old Project Gantt Chart}
   \label{fig:old-gantt}
 \end{figure}
 \begin{figure}[h]
   \centering
-  \includegraphics[width=\linewidth]{new-gantt.jpg}
+  \includegraphics[width=\linewidth]{new-gantt.png}
   \caption{New Project Gantt Chart}
   \label{fig:new-gantt}
 \end{figure}
+Our revised Gannt chart features two key changes. The back end and front end
+sections were modified such that the transition of effort from the virtual
+machine to the debugger aligns with where that actually happened. As a result,
+the testing and revision section was push back. We are now aiming to start
+testing and revision the week of April 20\textsuperscript{th}.
+\subsection*{Quantification of Progress}
+Currently, we have over 50 test files that we use to check for correctness of
+our virtual machine. We currently pass 44 test cases, and are working to have
+the rest functioning correctly soon. Once the debugger is more feature complete,
+we will focus more on user feedback to assess progress.
+\section{Recommendations}
 There are three major changes to the project plan: the frontend and backend
 deadlines have moved back several days, the user testing and revisions period
-have shifted back accordingly and have shortened, the frontend goal categories
-have been redefined. These changes can be identified in the above Gantt charts
-by in shifts in the bars of the Gantt chart. The development bars have
-increased in relative size while the testing and revising bars have shrunk.
+have shifted back accordingly and have shortened, and the frontend goal
+categories have been redefined. These changes can be identified in the above
+Gantt charts by in shifts in the bars of the Gantt chart. The development bars
+have increased in relative size while the testing and revising bars have shrunk.
 \par
 The frontend and backend periods needed to shift backwards simply due to the
 group’s initial underestimation of the amount of time required to create a