Progress Report done

progress_report/progress_report.tex

@@ -125,40 +125,40 @@ 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}
-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.png}
   \caption{Old Project Gantt Chart}
   \label{fig:old-gantt}
 \end{figure}
+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 2, below).
+\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.
+\par
 \begin{figure}[h]
-  \centering
   \includegraphics[width=\linewidth]{new-gantt.png}
   \caption{New Project Gantt Chart}
   \label{fig:new-gantt}
@@ -168,19 +168,20 @@ 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}
+\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}
+\subsection{Changes}
 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, 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
+\subsection{New Timeline}
 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
 reasonable product. The team believes additional development time on the
@@ -190,7 +191,7 @@ Without this pushback the team currently has a working prototype with a basic
 user interface and native function calls implemented, but the project has yet
 to include several important features considered necessary for useful
 application by students.
-\par
+\subsection{Future Phases}
 The user testing and adjustments periods have shrunk due to the increased
 development time. The team decided to avoid user testing and adjustments during
 the main development phase, but due to the time pressure this caused the
@@ -198,7 +199,7 @@ testing and adjustment phases to shrink by several days each and overlap
 significantly. The team hopes to consistently implement changes as students
 provide feedback so that the overlap still provides time to implement
 suggestions.
-\par
+\subsection{Redefined Goals}
 The redefined goals within the frontend category reflect altered priorities of
 the project as a whole. Rather than having the project work to explain topics
 to the user, the project will be designed to simply run user code and step
@@ -210,4 +211,15 @@ team to focus more on providing user interface features which will more
 directly aid in student code development. These features include code stepping
 and highlighting as well as annotated bytecode as listed in the Gantt chart
 above.
+\section{Discussion}
+These changes provide for a more accurate description of the timeline and the
+remaining work to be accomplished before the deatline. The team believes that
+this project still has a high likelihood of being completed, and this will
+allow for the Fall 2015 students of 15-122 being able to better understand
+and use C0. We also feel that these changes, in the long run, will lead to a
+better, more polished product. While our deliverables do not change, the focus
+of the product team has changed to avoid user testing and adjustments during
+the development phase and consistently implement changes as students provide
+feedback. In the long run, the team believes that we will accomplish the final
+product in the timeline specified.
 \end{document}