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

diff --git a/marsrover/document/requirements.tex b/marsrover/document/requirements.tex
index a47aac9..c8beedd 100644
--- a/marsrover/document/requirements.tex
+++ b/marsrover/document/requirements.tex
@@ -1,13 +1,16 @@
 \section{Requirements}
-The requirements are is ordered following the MoSCoW prioritization method. The
-MoSCoW approach originated from the RAD methodology~\cite{clegg_case_1994}.
-MoSCoW is used to sort the MarsRover 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 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 won't get). The first letters are used in the
-first column of \autoref{tab:req} to describe the priority of the 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\\
@@ -40,6 +43,7 @@ first column of \autoref{tab:req} to describe the priority of the requirements.
 	\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.\\