Index: dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex =================================================================== diff -u -r369 -r861 --- dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex (.../DAM Engine - Functional Design.tex) (revision 369) +++ dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.tex (.../DAM Engine - Functional Design.tex) (revision 861) @@ -2,6 +2,7 @@ \usepackage[titletoc]{appendix} \usepackage{lipsum} \usepackage{multirow} +\usepackage{enumerate} %----------------------------------------------- \begin{document} @@ -47,7 +48,6 @@ %------------------------------------------------------------------------------ \appendix\chapter*{Appendix} \addcontentsline{toc}{chapter}{Appendix} -\include{DataCombination} \include{REQDataGenerationWater} \include{RRDScenarioSelection} \include{DesignGeometryAdaption} Fisheye: Tag 861 refers to a dead (removed) revision in file `dam engine/trunk/doc/Dam Engine - Functional Design/DataCombination.tex'. Fisheye: No comparison available. Pass `N' to diff? Index: dam engine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.pdf =================================================================== diff -u -r370 -r861 Binary files differ Index: dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex =================================================================== diff -u -r368 -r861 --- dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex (.../FO.tex) (revision 368) +++ dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex (.../FO.tex) (revision 861) @@ -54,54 +54,57 @@ \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. +Main purpose of the \ProgramName is to get data from DAM Clients, uses this data as calculation input and make serially calculations with one ore more kernels and generates output. Therefor this chapter is diveded in requirements concerning data, calculation and output. -\section{REQ Data.Format}\label{sec:REQDataFormat} +\section{Data} + +\subsection{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} +\subsection{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:REQDataCombi} -The \ProgramName combines data per location when data is provide in GIS-files. Locations are defined by RD-coordinates. The design of this functionality is described in \autoref{sec:DataCombination}. - -\section{REQ Data.Generation.Geometry}\label{sec:REQDataGenerationGeometry} -The \ProgramName can combine a surface line with a subsoil scenario. The result is a geometry, usable for the failure mechanism Macrostability. - -\section{REQ Data.Generation.Porepressures}\label{sec:REQDataGenerationPorepressures} -The \ProgramName can combine the hydraulic data with a subsoil scenario. The result is a schematization of the pore pressures, usable for the failure mechanisms Piping and Macrostability. The design of this generation is mentioned in \autoref{sec:GenerationPorePressures}. - -\section{REQ Calc.Type}\label{sec:REQCalcType} -The \ProgramName provides three types of calculations: -\begin{enumerate} +\section{Calculation} +The \ProgramName provides three types of major calculations: +\begin{enumerate}[A.] \item One-fold calculation: the input goes 'through' the kernel(s) 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 + \item Assessment general (type A) + \item Assessment regional dikes (type A) + \item Design of geometry, given required safety factor: Design-Geometry (type B) + \item Design of geometry, given dimensions of excavation and required safety factor: Design-Excavation (type B) + \item Operational calculation from sensor data (type C) \end{itemize} +Next to the major calculations the DAM engine must provide the following supporting calculations: +\begin{itemize} + \item generate waternet + \item generate excavations in geometries +\end{itemize} -\section{REQ Calc.Assess.General}\label{sec:REQCalcAssessGeneral} -The DAM engine provides a Factor of safety. This may be one calculation or several. More than one calculation becames available when using several locations and/or several scenarios. +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 Calc.Assess.Loadscenarios}\label{sec:REQCalcAssessLoadscenarios} -The DAM engine must be able to calculate several load scenarios with different input data per location. -\section{REQ Calc.Assess.Regional}\label{sec:REQCalcAssessRegional} + +\subsection{REQ Calc.Assess.General}\label{sec:REQCalcAssessGeneral} +The DAM engine provides a factor of safety. This may be one calculation or several calculations in batch. More than one calculation becomes available when using several locations and/or several subsoilcenarios. + +\subsection{REQ Calc.Assess.Regional}\label{sec:REQCalcAssessRegional} For the assessment of regional dikes, \ProgramName must calculate several assessment scenarios (RRD-scenario). The design of this scenario selection is descriped in \autoref{sec:RRDScenarioSelection}. -\section{REQ Calc.Operational.Sensor}\label{sec:REQOperationalSensor} +\subsection{REQ Calc.Operational.Sensor}\label{sec:REQOperationalSensor} The DAM Engine must be able to use sensor data as input for the generation of water pressures. -\section{REQ Calc.Design.Geometry}\label{sec:REQDesignGeometry} +\subsection{REQ Calc.Design.Geometry}\label{sec:REQDesignGeometry} The DAM engine must be able to generate new profiles (surfacelines) based on desired Factor of safety. This can be done by: \begin{enumerate} \item Raising the crest @@ -111,18 +114,22 @@ The design of this geometry adeption is worked out in \autoref{sec:DesignGeometryAdaption} -\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 +\subsection{REQ Calc.Design.Excavation}\label{sec:REQDesignExcavation} +This will not be part of the implementation of DAM Engine and therefor this paragraph has not yet been written. -\section{REQ Failuremechanism}\label{sec:REQFailuremechanism} +\subsection{Failuremechanisms}\label{sec:Failuremechanism} 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; + \item Macrostability inwards; REQ Mac.Inwards + \item Macrostability outwards; REQ Mac.Outwards + \item Piping; REQPiping \end{enumerate} +\section{REQ Data.Generation.Porepressures}\label{sec:REQDataGenerationPorepressures} +The \ProgramName can combine the hydraulic data with a subsoil scenario. The result is a schematization of the pore pressures, usable for the failure mechanisms Piping and Macrostability. The design of this generation is mentioned in \autoref{sec:GenerationPorePressures}. + + \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.