Added range of missions and development evaluation

diff --git a/marsrover/document/evaluation.tex b/marsrover/document/evaluation.tex
index 1554614..ce62ee1 100644 (file)
--- a/marsrover/document/evaluation.tex
+++ b/marsrover/document/evaluation.tex
@@ -73,3 +73,24 @@ and if they are we try to complete as many iterations as possible.
 \end{table}
 
 \subsection{Evaluation}
+
+Because of the action defined in behaviour is atomic, it makes the behaviour can be defined dinamically. It means that we can define some combination of actions to do a specific mission. The example of missions that can be supported by the DSL are the following:
+\begin{enumerate}
+\item Find lakes by color sensor
+\item Find rocks by front ultrasone sensor
+\item Push rocks
+\item Wander on the table forever
+\item Measure rocks
+\item Measure lakes
+\item Avoid rocks
+\item Avoid lakes
+\item Park in the corner of the table
+\end{enumerate}
+However the missions that cannot supported by the DSL are the following:
+\begin{enumerate}
+\item Find lakes and remember where they are after the robot found them
+\item Navigate with the map using SLAM (Simultaneous Locatization and Mapping)
+\end{enumerate}
+
+From our experience, the most important think in the development process was start working from a small functionality and test it. Earlier we know something wrong with the program and earlier we can fix and test it again. That will be good for the development of the next functionality.
+The difficulty in the development was in the testing phase. The reason is sometimes we got an error when running the program in robot (for example: sensor error) and it took so much time for loading all sensor working to test the robot. There was a time when the robot was crashed and need to be restarted which take some time from the development time.
\ No newline at end of file