Index: doc/System/DSoilModel - Test Plan/DSoilModel - Test Plan.pdf
===================================================================
diff -u -r65 -r75
Binary files differ
Index: doc/System/DSoilModel - Test Plan/DSoilModel - Test Plan.tex
===================================================================
diff -u -r65 -r75
--- doc/System/DSoilModel - Test Plan/DSoilModel - Test Plan.tex	(.../DSoilModel - Test Plan.tex)	(revision 65)
+++ doc/System/DSoilModel - Test Plan/DSoilModel - Test Plan.tex	(.../DSoilModel - Test Plan.tex)	(revision 75)
@@ -93,9 +93,8 @@
 
 The document will not give any background on the context of the WTI project. For this purpose the reader is referred to the WTI2017 and to its supporting technical reports and their background reports underneath (paragraph 1.3). 
 
-This document will not describe how the requirements and functional design are implemented in the program. 
+This document will not describe how the requirements of the functional design are implemented in the program but described how the requirements of the functional design are tested.
 
-This document describes the different regression and acceptation tests, including target values.
 
 \section{Other system documents}
 
@@ -143,9 +142,9 @@
 \subsection*{System Testing (Benchmarks and test scripts)}
 System Testing is testing the functioning of the complete system: 
 \begin{itemize}%[no separator]
-	\item The main calculator must provide the correct answers to confirm its performance according to the functional design;
-	\item All possible errors must be handled and reported properly;
-	\item The \textit{User Interface} must function properly.
+	\item The \textit{User Interface} must function properly: this testing must proved that the functional and non-functional requirements are met;
+	\item All possible errors must be handled and reported properly (including the minimum and maximum values of input).
+	
 \end{itemize}	
 Refer to \Cref{chapter4} for more information.
 
@@ -199,10 +198,10 @@
 
 A Test Script will be provided to the tester, describing a sequence of actions and the expected outcome. An overview of the Test Scripts is listed below:
 \begin{itemize}
-	\item \textbf{Language:} \\
+	\item \textbf{Language:} \newline
 	The test must be done only for Dutch language.
 	\\
-	\item \textbf{Layout:} \\
+	\item \textbf{Layout:}\newline
 	The layout must be identical to the layout described in the Technical Design \citep{TechnicalDesign}:
 	\begin{itemize}
 		\item Menu items
@@ -212,8 +211,8 @@
 		\item Tabs
 		\item Icon bar of tabs
 	\end{itemize}
-	\\
-	\item \textbf{Menu:} \\
+	
+	\item \textbf{Menu:} \newline
 	All available options under the different items of the menu must be tested. \\
 	This includes the importation of data's via the \textit{Import} option under the \textit{File} menu: all the possibilities supported by \DSOILMODEL must be tested by checking that the data's are correctly and completely imported.	
 	%\begin{itemize}
@@ -231,10 +230,10 @@
 	%\end{itemize}
 	Each importation of a file will have at least one test script. The files to be tested will be provided to the tester.
 	\\
-	\item \textbf{Menu bar:} \\
+	\item \textbf{Menu bar:} \newline
 	All icons of the menu bar must be tested.
 	\\
-	\item \textbf{Tables toolbar:} \\
+	\item \textbf{Tables toolbar:} \newline
 	All icons of the Tables toolbar (when available) must be tested:
 	\begin{itemize}
 		\item Add
@@ -247,8 +246,8 @@
 		\item Edit Unit
 		\item Export (all available formats must be tested)
 	\end{itemize}
-	\\
-	\item \textbf{Map / Length Profile toolbar:} \\
+	
+	\item \textbf{Map / Length Profile toolbar:} \newline
 	All icons of the Map and Length Profile toolbar (when available) must be tested:
 	\begin{itemize}
 		\item Selection
@@ -266,15 +265,15 @@
 		\item Selection	
 		\item Add location for split
 	\end{itemize}
-	\\
-	\item \textbf{Property Editors:} \\
+	
+	\item \textbf{Property Editors:} \newline
 	The content of the property editor must be check for all selected objects. \\
 	The coupling between the content of the Property Editors and the Tables component must also be tested: changing a property in the Property Editors should affect the Tables component.
 	\\
 	\item \textbf{Default/Min/Max:} \newline
 	The default, minimum and maximum values  of all properties (as given in the Functional Design) must be tested.
 	\\
-	\item \textbf{Filters:}
+	\item \textbf{Filters:} \newline
 	All possible filters must be tested, by checking that the resulting list of is as expected (no more, no less). All possible combination of filters must also be tested.
 \end{itemize}
 
@@ -292,7 +291,8 @@
   \item Remarks and details on the test results can be put at the end of the test.
 \end{itemize}
 
-If a test step fails, just add ``failed'' in the column ``Result''. 
+If a test step fails, just add ``failed'' in the column ``Result''. \\
+The test script also needs to describe which functional and non functional requirements are tested.
 
 \begin{table}[H]
 %\caption{xxx}