From d685c47d4b13cc90ca44d428002773c848f9cf80 Mon Sep 17 00:00:00 2001 From: Natanael Adityasatria Date: Thu, 17 Dec 2015 21:18:02 +0100 Subject: [PATCH] Add moscow explanation --- marsrover/document/requirements.tex | 3 +++ marsrover/document/robot.tex | 4 ++++ 2 files changed, 7 insertions(+) diff --git a/marsrover/document/requirements.tex b/marsrover/document/requirements.tex index 9b518af..70c1d23 100644 --- a/marsrover/document/requirements.tex +++ b/marsrover/document/requirements.tex @@ -1,4 +1,7 @@ \section{Requirements} + +The requirement prioritization 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 to descibe the priority in the following table: + \begin{longtabu}to \linewidth{llX} \toprule \rowfont\bfseries Code & Priority & Description\\ diff --git a/marsrover/document/robot.tex b/marsrover/document/robot.tex index 092f9e9..4fbaf5b 100644 --- a/marsrover/document/robot.tex +++ b/marsrover/document/robot.tex @@ -71,3 +71,7 @@ mapping is described in \autoref{tab:mapping}. \caption{Proposed mapping of the sensors and actuators}\label{tab:mapping} \end{table} +\subsection{Domain Specific Language} + + +\subsection{Code Structure} \ No newline at end of file -- 2.20.1