Index: dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.pdf
===================================================================
diff -u -r297 -r310
Binary files differ
Index: dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex
===================================================================
diff -u -r297 -r310
--- dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex	(.../DAM Engine - Functional Design.tex)	(revision 297)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex	(.../DAM Engine - Functional Design.tex)	(revision 310)
@@ -99,8 +99,132 @@
 
 \chapter{Functional requirements}
 
+Main purpose of the \ProgramName
+The \ProgramName gets data from DAM Clients, combines this data to calculation input and make serially calculations with one ore more kernels and generates output.
 
+\section{REQ Data.Format}\label{sec:REQDataFormat}
+The \ProgramName has a defined format for the data input, so DAM Clients know how to arrange the input data.
 
+\section{REQ Data.Content}\label{sec:REQDataContent}
+The \ProgramName has a defined content for the data input, so DAM Clients know how to arrange the input data.
+
+\section{REQ Data.Combination}\label{sec:REQDataCombination}
+The \ProgramName combines data per location. Locations are defined with RD-coordinates
+
+
+
+\section{REQ Calc.Type}\label{sec:REQCalcType}
+The \ProgramName provides three types of calculations:
+\begin{enumerate}
+	\item One-fold calculation: the input goes 'through' the kernel and generates one main calculation answer (assessment);
+	\item Goal-seeking calculation: the input contains one variable and a desired outcome, the answer is the variable sufficient for the goal (design);
+	\item Time-lapsed calculation; calculations are made as time serie (operational).
+\end{enumerate}
+
+More specified; the \ProgramName provides the following calculation types, so the DAM Clients can provide this functionality.
+\begin{itemize}
+	\item Assessment general
+	\item Assessment regional dikes
+	\item Operational calculation from sensor data
+	\item Design of geometry, given required safety factor: Design-Geometry
+	\item Design of normative NWO-location, given dimensions of NWO and required safety factor: Design-NWO
+\end{itemize}
+
+
+\section{REQ Calc.Assess.General}\label{sec:REQCalcAssessGeneral}
+
+
+\section{REQ Calc.Assess.Regional}\label{sec:REQCalcAssessRegional}
+For the assessment of regional dikes, \ProgramName must calculate several assessment scenarios (RRD-scenario), depending on:
+ 
+ \begin{itemize}
+	\item the type embankment (peat/other); green block in \autoref{fig:RRDPeat.png} and \autoref{fig:RRDClay.png)
+	\item the hydraulic shortcut (yes/no); brown block in \autoref{fig:RRDPeat.png} and \autoref{fig:RRDClay.png) and in detail in \autoref{fig:HydraulicShortcut}
+	\item the uplift situation (yes/no); blue block in \autoref{fig:RRDPeat.png} and \autoref{fig:RRDClay.png)
+\end{itemize}
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/RRDClay.png}
+  \end{center}
+  \caption{Flowchart of embankements other than peat}
+  \label{fig:RRDClay}
+\end{figure}
+
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/RRDPeat.png}
+  \end{center}
+  \caption{Flowchart of embankements of peat}
+  \label{fig:RRDPeat}
+\end{figure}
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/HydraulicShortcut.png}
+  \end{center}
+  \caption{FlowcharHydraulicShortcut}
+\end{figure}
+
+
+\begin{table}[H]
+\centering
+\begin{tabular}{|p{18mm}|p{37mm}|p{20mm}|p{20mm}|p{\textwidth-105mm-36pt}|}
+\hline
+\textbf{RRD Scenario} & \textbf{Condition} & \textbf{Hydraulic Shortcut} & \textbf{Uplift} & \textbf{Model} \\ \hline
+1 & Dry	& yes & yes & Uplift \\ \hline
+2 & Dry & no & yes & Uplift \\ \hline
+3 & Wet	& yes & yes & Uplift \\ \hline
+4 & Wet	& no & yes & Bishop \\ \hline
+5 & Dry	& yes & yes & Bishop \\ \hline
+6 & Dry & no & yes & Bishop \\ \hline
+7 & Wet	& yes & yes & Bishop \\ \hline
+8 & Wet	& no & yes & Bishop \\ \hline
+9 & Dry	& yes/no & yes & Horizontal equilibrium \\ \hline
+10 & Wet & yes/no & yes & Piping \\ \hline
+11 & Dry & yes/no & yes & Piping \\ \hline
+\end{tabular}
+\caption{RRD scenarios}
+\label{RRDScenarios}
+\end{table}
+
+
+
+\subsection{The condition (dry/wet)
+For embankements made of peat is it ne
+
+
+
+
+
+\section{REQ Calc.Operational.Sensor}\label{sec:REQOperationalSensor}
+
+
+\section{REQ Calc.Design.Geometry}\label{sec:REQDesignGeometry}
+
+\section{REQ Calc.Design.NWO}\label{sec:REQDesignNWO}
+This will not be part of the first implementation of DAM Engine and therefor this paragraph has
+not yet been written.
+
+
+\section{REQ Failuremechanism}\label{sec:REQFailuremechanism}
+
+The \ProgramName provides calculations for following failure mechanisms, so the DAM Clients can provide this functionality.
+\begin{enumerate}
+	\item Macrostability inwards
+	\item Macrostability outwards
+	\item Piping
+\end{enumerate}
+
+
+\section{REQ Output.format}\label{sec:REQOutputFormat}
+The \ProgramName has a defined format for the data output, so DAM Clients know how to present the output data.
+
+\section{REQ Data.Content}\label{sec:REQDataContent}
+The \ProgramName has a defined content for the data output, so DAM Clients know how to present the input data.
+
+
 %------------------------------------------------------------------------------
 %\chapter{System Architecture} \label{chapterSystemArchitecture}
 %