Merge branch '111-db_annotations' into 'master'

document architectural breach with db annotations in models

See merge request !65

Documentation/src/02_product-documentation/03_architecture.tex

@@ -16,12 +16,20 @@
 		\end{figure}
 
 	\section{Architecture diagram}
+		\label{fig:architecture-diagram}
 		\begin{figure}[H]
 			\centering
 			\caption{Architecture diagram}
 			\includegraphics[scale=0.45]{resources/diagrams/architecture-diagram.png}
 		\end{figure}
 
+		\subsection{Breaches}
+		As shown in \ref{fig:architecture-diagram}, the domain layer should not depend on the used frameworks. 
+		But since we use a database and we use the same models for the database as for the views, we needed to decorate our models with 
+		annotations of the database framework. Therefore the domain layer depends on the framework layer. This affects maintainability, 
+		because the stable, slowly changing domain layer has to change as soon as a new database framework is used. Apart from that, 
+		however, the annotations do not result in any further impairments. 
+
 	\section{Project structure}
 		\subsection{Solution Structure}
 			Our software project uses a horizontal cut, which means it is technically structured and grouped by views, view models and models.