Move server, client diag. to the Requirements

Fix logical error where references to the diagrams were
referring to the subsequent chapter. References to the diagrams
exchanges in first referred paragraph so they are in a numerical order.

analytical.tex

@@ -1,7 +1,7 @@
 \section{Requirements}
 The requirements for the final device are grouped to the three categories. Mandatory requirements are bound to be met at any cost. Some of the high importance requirements can be skipped or slightly modified, if unpredictable obstacles are found. However, they are all assumed to be completed for well being of the project. Optional requirements will be completed only if possible, given the resources will allow it.
 
-They are also divided to a hardware part and software part. Software is easier to change than hardware and requires hardware to be run on. Software is also limited by the resources provided by the hardware. Therefore, hardware needs to be logically completed first and are also highlighted in figures \ref{f:serv_node} and \ref{f:client_node}.
+They are also divided to a hardware part and software part. Software is easier to change than hardware and requires hardware to be run on. Software is also limited by the resources provided by the hardware. Therefore, hardware needs to be logically completed first and are also highlighted in figures \ref{f:client_node} and \ref{f:serv_node}.
 
 \subsection{Hardware requirements}
 
@@ -29,6 +29,11 @@ They are also divided to a hardware part and software part. Software is easier t
 \item Internet and Ethernet connection on server node
 \end{enumerate}
 
+\begin{figure}[ht]
+\centering
+\includegraphics[width=.7\textwidth,angle=0]{client_node_diag}
+\caption{The proposed block diagram of a \textit{client node}, including HW requirements}\label{f:client_node}
+\end{figure}
 
 \subsection{Software requirements}
 \textbf{Mandatory:}
@@ -54,26 +59,20 @@ They are also divided to a hardware part and software part. Software is easier t
 \item Ability to set thresholds for measured data and notify user about crossing them via text based message
 \end{itemize}
 
+\begin{figure}[ht]
+\centering
+\includegraphics[width=.7\textwidth,angle=0]{server_node_diag}
+\caption{The proposed block diagram of a \textit{server node}, including HW requirements}\label{f:serv_node}
+\end{figure}
+
 \newpage
 \section{System design}
 
 The first mandatory software requirement asks for a web server. It is entirely possible for every measurement device to contain its own web server. However, multiple points are requiring devices to work as a \textbf{system}. Two common system structures are \textit{centralised} and \textit{decentralised}. 
 Decentralised (peer-to-peer) systems are harder to build but are more fail-proof. Since fail-proofness is not mentioned in the requirements, centralised system might suffice. 
 
-\begin{figure}[ht]
-\centering
-\includegraphics[width=.75\textwidth,angle=0]{server_node_diag}
-\caption{The block diagram of a \textit{server} node of a proposed system, including hardware requirements}\label{f:serv_node}
-\end{figure}
-
 Using centralised system means, that the measurement devices  will use one separate device, from now called the \textbf{server node}, to do most of the work on the software side. The work includes, but is not limited to, receiving the measured data, storing them, hosting the web server with the \gls{gui} containing all necessary options and information, handling the \gls{usb} or communication with a \gls{cloud} and so on. The block diagram for a server node, depicting required blocks can be seen in the figure \ref{f:serv_node})
 
-\begin{figure}[ht]
-\centering
-\includegraphics[width=.75\textwidth,angle=0]{client_node_diag}
-\caption{The block diagram of a \textit{client} node of a proposed system, including hardware requirements}\label{f:client_node}
-\end{figure}
-
 Where there are at least two nodes in a system, they have to communicate together in a particular way, known to both of them. The web server naturally operates over \gls{tcpip}. Therefore, same networking stack (the way of comunication), that is used for communication between the server node and user can be used to communicate to client nodes as well. \Gls{tcpip} hardware is ready to be used and is supporting a full-blown networking \gls{stack}, powering communication over today's networks.