Index: DamClients/DamUI/trunk/doc/DAM UI - Technical Design/DAM UI - Technical Design.tex
===================================================================
diff -u -r3584 -r3679
--- DamClients/DamUI/trunk/doc/DAM UI - Technical Design/DAM UI - Technical Design.tex	(.../DAM UI - Technical Design.tex)	(revision 3584)
+++ DamClients/DamUI/trunk/doc/DAM UI - Technical Design/DAM UI - Technical Design.tex	(.../DAM UI - Technical Design.tex)	(revision 3679)
@@ -42,8 +42,8 @@
 \versionii{0.2}
 \dateii{April 2022}
 \authorii{Tom The, John Bokma}
-\reviewerii{Tom The}
-\approvalii{Hans van Putten}
+\reviewerii{Walter Austmann}
+\approvalii{Arthur Baart}
 
 \status{draft}
 \disclaimer{This is a draft report, intended for discussion purposes only. No part of this report may be relied upon by either principals or third parties.}
@@ -122,16 +122,18 @@
 \end{figure}
 
 In case the DAM Engine is used to calculate the macro stability, 
-additional output is available in the form of input files and a picture of the results (wmf).
-The input files can be used to check/redo the calculation using the UI suitable for the   used kernel.
+additional output is available in the form of an output file per calculation. 
+This file (.stix) holds the resulting slip plan besides to the input and can be used to review the result using D-Stability.
+The input files can be used to check/redo the calculation using the UI suitable for the used kernel.
 
-Note that instead of Sti files (as were produced for D-GeoStability 18.1 kernel), 
-the new version produces Stix-files based on the input needed for the Macro Stability kernel. 
-This required input is specified via the MacroStabilityInput object as defined in the C \# wrapper module for that kernel. 
-In the communication between Engine and UI, the name of this stix file is part of the Design Results of the XML output of the Engine. This name of course has to unique and will be created based on the names of the location, scenario and profile combined with the number of the iteration in case of design.
+The required input is specified via the MacroStabilityInput object as defined in the C \# wrapper module for the Macro Stability kernel. 
+In the communication between Engine and UI, 
+the name of the resulting stix file is part of the Design Results of the XML output of the Engine. 
+This name of course has to unique and will be created based on the names of the location, scenario and profile combined with the number of the iteration in case of design. 
+To indicate its purpose, it ends on "\_result".
 
-Future developments foreseen for the stability calculations include the addition of the kernel results to the stix files and the possibility to create an output picture (wmf/png)
-based on these results.
+Future developments foreseen for the stability calculations include the addition of the bare input for the Macro Stability kernel in order to be able to check the position of the input grid(s).
+
 %------------------------------------------------------------------------------
 \chapter{Architectural Choices} \label{chapterArchitecturalChoices}
 
@@ -165,9 +167,9 @@
 Some calculations may be performed but cause warnings.
 Using a log manager, 
 all these cases are reported back to the user via a log that is to be displayed at the end of the calculation process.
-This log is cleared at the start of each new calculation process.
-When the project is saved, the existing log is saved too with a time stamp.
+This log is then also saved automatically with a time stamp.
 Note that the saved log will not be loaded again in the program itself.  
+Finally, the log is cleared at the start of each new calculation process.
 
 The results of the calculations differ per failure mechanism per model. 
 An overview of all "single" result parameters is provided by the DAM documentation on the public wiki for DAM (https://publicwiki.deltares.nl/display/DAM/Tabblad+Ontwerpberekeningen).