From d804790eafb505ff1c69f5d16fac7d28299fefa9 Mon Sep 17 00:00:00 2001
From: Refik Hadzialic
Date: Sun, 30 Oct 2011 17:24:28 +0100
Subject: Making some of the images appear in landscape, just for better
 reading

---
 notFinishedCode/Report/test.tex | 39 +++++++++++++++++++++++++++++----------
 1 file changed, 29 insertions(+), 10 deletions(-)

(limited to 'notFinishedCode/Report/test.tex')

diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index b645681..d9be0cc 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -1,6 +1,7 @@
 \documentclass[a4paper, titlepage, oneside, headsepline, footsepline]{scrartcl} 
 %PACKAGES
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\usepackage{lscape} %for the landscape pages it is used
 \usepackage[english]{babel} %what language are we using
 \usepackage[latin2]{inputenc} %what alphabet
 
@@ -180,11 +181,7 @@ During the development time we refined our requirements. In the next chapters we
 As we mentioned in the software requirements section, we decided to use MySQL as our database system for storing the test information and results.
 It was not difficult to decide what database to use, since MySQL is one of the most supported database and one can find a library to use it with major programming languages. 
 The key point in the design of our database was the simplicity and speed of accessing the data. We had decided to use seven tables. In the following paragraphs we will explain each table separately and its usage.
-\begin{figure}[ht!]
-  \centering
-  \includegraphics[width=147mm]{DBRelationship.png}
-  \caption[]{Database relationship diagram}
-\end{figure}
+The database design can be seen in figure 4.
 
 \par The \emph{PingResultTable} table has six attributes (\emph{taskNo, sipServer, sipGate, unisip, gsmBox1, gsmBox2}), all of integer type. 
 The \emph{taskNo} attribute identifies the test number but not a single test (e.g. an operator user has selected three different tests to be executed, all of the three tests will have the same \emph{taskNo} to identify them together as belonging to one test group and \emph{taskId} identifies each single test and will be explained later). 
@@ -213,7 +210,20 @@ However, all the test tasks even after deleting them from \emph{TempTaskTable} a
 \par The \emph{TaskTable} table, as mentioned before contains all the tests ever performed from the web site. It is made out of five attributes, \emph{taskID, taskNo, from, to, timestamp}. The first four fields are the same as in \emph{TempTaskTable}, however the last one, \emph{timestamp}, is used to record the exact time when the test was performed. 
 \par The \emph{GSMListPrefix} table contains the data about the GSM networks and their prefixes. It consists of two
 attributes, both of varchar type, \emph{providerName} and \emph{prefix}.
-\newpage
+\begin{landscape}
+\begin{center}
+\begin{figure}[ht!]
+  \centering
+  \includegraphics[width=218mm]{DBRelationship.png}
+  \caption[]{Database relationship diagram}
+\end{figure}
+\end{center}
+\end{landscape}
+
+
+
+
+
 \section{Software design}     % section 2.1
 Software design was the next step after we analyzed the problem and developed a plan how to proceed further. Good analysis and planning with poor algorithmic implementation is valueless. 
 During the work on the project, we had spent most of our time for software design. 
@@ -255,12 +265,16 @@ it manually can see the test results. We will proceed with introducing the class
 The software class diagram can be seen in the following figure. More details for the 
 classes, like the input/output can be found on our project's wiki page \cite{wiki}.
 
-
+\begin{landscape}
+\begin{center}
 \begin{figure}[ht!]
   \centering
-  \includegraphics[width=147mm]{classDiagram.png}
+  \includegraphics[width=218mm]{classDiagram.png}
   \caption[]{Class diagram (some classes were excluded)}
 \end{figure}
+\end{center}
+\end{landscape}
+
 
 \newpage
 \subsection{Database access}         % subsection 2.1.1
@@ -474,12 +488,17 @@ from begining again. If the states are not entered in the specified order the co
 the state machine is in the waiting for a new connection state\footnote{It cannot be seen in the protocol flowchart but one should
 keep in mind it works like a well defined state machine.}.
  
-
+\begin{landscape}
+\begin{center}
 \begin{figure}[ht!]
   \centering
-  \includegraphics[width=147mm]{protocolCommunicationHandler.png}
+  \includegraphics[width=218mm]{protocolCommunicationHandler.png}
   \caption[]{Flowchart of the protocol on the handler side without the state representation}
 \end{figure}
+\end{center}
+\end{landscape}
+
+
 
 \begin{figure}[ht!]
   \centering
-- 
cgit v1.2.3-55-g7522

