X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=marsrover%2Fdocument%2Frequirements.tex;h=c8beedda259400f51bceb260c0de0c4ee77b05d5;hb=HEAD;hp=9b518af2f4517e5566464ad565d3f12e37bb699f;hpb=e82a01b574592ef0ba8e2fcddf71a60db4c5c096;p=des2015.git

diff --git a/marsrover/document/requirements.tex b/marsrover/document/requirements.tex
index 9b518af..c8beedd 100644
--- a/marsrover/document/requirements.tex
+++ b/marsrover/document/requirements.tex
@@ -1,14 +1,26 @@
 \section{Requirements}
+\subsection{\emph{MoSCoW}}
+The requirements are ordered following the \emph{MoSCoW} prioritization method.
+The \emph{MoSCoW} approach originated from the RAD
+methodology~\cite{clegg_case_1994}.  \emph{MoSCoW} is used to sort the features
+into priority order based on the importance. In this way, the developers are
+able to understand what feature is essential to be done. The term \emph{MoSCoW}
+itself is an acronym derived from the first letter of each of four
+prioritization categories (Must have, Should have, Could have, and Would like
+but will not get). The first letters are used in the first column of
+\autoref{tab:req} to describe the priority of the requirements.
+
+\subsection{Requirements}
 \begin{longtabu}to \linewidth{llX}
 	\toprule 
 	\rowfont\bfseries Code & Priority & Description\\
 	\midrule
 	\endhead%
-	\\\midrule
+	\midrule
 	\multicolumn{3}{c}{\ldots}\\
 	\bottomrule
 	\endfoot%
-	\\ \bottomrule
+	\bottomrule\\\caption{Requirements list}\label{tab:req}
 	\endlastfoot%
 
 	\multicolumn{3}{l}{Functional requirements}\\
@@ -31,6 +43,7 @@
 	\midrule\midrule
 
 	\multicolumn{3}{l}{Non-functional requirements}\\
+	\midrule\midrule
 	NR1 & \textsc{M} & The code should be generated by a DSL.\\
 	NR2 & \textsc{S} & Finish the entire mission set within the
 		demonstration time.\\
@@ -38,5 +51,4 @@
 	NR4 & \textsc{S} & Be able to cope with lesser sensor data.\\
 	NR5 & \textsc{C} & If due bugs the sensors do not boot up the robot
 		should restart the program.\\
-	\midrule\midrule
 \end{longtabu}