\chapter{Deployment view}
\label{chapter_deployment_view}

\section{Primary presentation}
\begin{figure}[h]
    \begin{center}
        \includegraphics*[angle=270, width=15cm, keepaspectratio]{Images/Deploymentdiagram.eps}
        \caption{Deployment Diagram}
    \end{center}
\end{figure}

\section{Element catalog}
This section will describe physical components of the deployment diagram. 
\subsection*{Client} 
The client is the hardware (or PC) which is used by an employee for using the system, by a client to access the website, or by the government instance to access the website. 

It only contains the highest layer of the development diagram, which is the systems interface to the users. This is the interface of the website which the client or government instance uses to get information from the system. The employees uses this interface to work with the system. 

\subsection*{Server}
The server is the hardware (or server) which communicates with the system, does all the calculations and stored all the data.

It contains the three lower layers of the development diagram. For a description of the three levels see the \textit{Development view}.  

\section{Context diagram}
N/A

\section{Variability guide}
N/A

\section{Architectural background}
\subsection{Rationale}
The system uses a Client-Server architecture style. The components are servers and clients,
which are both used in our model. The exact style is a so called \textit{thin client} style. The largest 
part of processing is at the server-side. 

The reasons why we've chosen this style are:
\begin{itemize}
\item The style ensures data security, because all calculations are done server side and data is server side.
\item It also makes the configuration management simple, because it only has to be done on the server.
\item The style makes the system more robust, because the clients have no state.
\end{itemize}

\subsection{Assumptions}
- There will be only one main server for the system.


\section{Other information}
