Index: DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex
===================================================================
diff -u -r923 -r2553
--- DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex	(.../DAM - Architecture Overall.tex)	(revision 923)
+++ DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.tex	(.../DAM - Architecture Overall.tex)	(revision 2553)
@@ -16,8 +16,8 @@
 \reference{1210702-000-GEO-0005}
 \classification{-}
 
-\date{Jan. 2017}
-\version{0.1}
+\date{Jul. 2019}
+\version{1.0}
 
 \keywords{Dike, safety assessment, design, software, macro stability, piping}
 
@@ -28,14 +28,14 @@
 \textbf{\footnotesize{Samenvatting}} \\
 Dit document bevat een beschrijving van de totale architectuur van \ProgramName, een User Interface applicatie die een gebruiker in staat stelt om voor een dijktraject berekeningen uit te voeren voor verschillende faalmechanismen, waaronder macrostabiliteit en piping.}
 
-\versioni{0.1}
-\datei{Jan 2017}
+\versioni{1.0}
+\datei{Jul 2019}
 \authori{Tom The}
 \revieweri{John Bokma}
 \approvali{Maya Sule}
 
-\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.}
+\status{final}
+\disclaimer{}
 
 \deltarestitle
 
@@ -416,6 +416,67 @@
 
 
 %------------------------------------------------------------------------------
+\chapter{Releasing a product}  \label{ProductRelease}
+
+This is a description of the steps needed to create a \ProgramName release. An external release is normally a release of a \ProgramName client (\ProgramName UI or \ProgramName Live).
+The order of releasing the several modules of the \ProgramName system is important because of the dependencies between the several modules. So keep the order of releasing as is specified in this chapter. \newline
+It is not always necessary to release all modules, but a module needs to be released, when a dependent module has a been released. 
+\section{Dam Failure Mechanisms} \label{ReleaseDamFailureMechanisms}
+This chapter describes the failure mechanisms which are specifically developed for Dam.
+\subsection{DamMacroStability} \label{ReleaseDamMacroStability}
+This failure mechanism is a wrapper around the D-Geo Stability executable (part of the D-Serie).
+The following steps are needed to release this failure mechanism.
+\begin{itemize}
+	\item Update version number in .$\backslash$src$\backslash$Deltares.DamMacroStability.Version$\backslash$GlobalAssembly.cs.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+\subsection{DamPiping} \label{ReleaseDamPiping}
+The following steps are needed to release this failure mechanism.
+\begin{itemize}
+	\item Update version number in .$\backslash$src$\backslash$Deltares.DamPiping.Version$\backslash$GlobalAssembly.cs.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+
+\section{DGSMStabDam} \label{ReleaseDGSMStabDam}
+This module is responsible for creating the D-Geo Stability project files.
+It is used by the \ProgramName Engine.
+The module is written in Delphi and the sources can be found in another repository:
+https://repos.deltares.nl/repos/pvcsprojects/ApplicationSupport/DAM/DGSMStabDam
+ 
+The following steps are needed to release this module.
+\begin{itemize}
+	\item Update version number in  .$\backslash$src$\backslash$DGSMStabDAM$\backslash$ResourceVersionInfo.rc.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+\section{Dam Engine} \label{ReleaseDamEngine}
+The following steps are needed to release this module.
+\begin{itemize}
+	\item Update version number in .$\backslash$src$\backslash$Deltares.DamEngine.Version$\backslash$GlobalAssembly.cs.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+This module has the following dependencies:
+\begin{itemize}
+	\item \ProgramName Failure Mechanisms
+	\item DGSMStabDam
+\end{itemize}
+
+\section{Dam UI} \label{ReleaseDamUI}
+The following steps are needed to release this application.
+\begin{itemize}
+	\item Update version number in .$\backslash$src$\backslash$Deltares.Dam.Version$\backslash$GlobalAssembly.cs.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+This application is dependent on the \ProgramName Engine.
+
+\section{DamLive} \label{ReleaseDamLive}
+The following steps are needed to release this application.
+\begin{itemize}
+	\item Update version number in .$\backslash$src$\backslash$Deltares.DamLive.Version$\backslash$GlobalAssembly.cs.svn
+	\item Release binary artifacts (from Teamcity) to the directory .$\backslash$release 
+\end{itemize}
+This application is dependent on the \ProgramName Engine.
+
+%------------------------------------------------------------------------------
 \chapter{Literature}  \label{Literature}
 
 \bibliography{../DAM_references/dam_references}
Index: DamOverall/trunk/doc/DAM - Architecture Overall/DAM - Architecture Overall.pdf
===================================================================
diff -u -r923 -r2553
Binary files differ