From af1053a7f54153fcdb59f78c2ea74e7a543e571b Mon Sep 17 00:00:00 2001
From: Refik Hadzialic
Date: Wed, 5 Oct 2011 11:56:09 +0200
Subject: Working on the report!

---
 notFinishedCode/Report/test.tex | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

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

diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 774061a..47bc0fd 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -100,13 +100,13 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mei
 \section{Introduction and Motivation}             % chapter 1
 \Large In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for landline calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems and infer the results out of our findings.
 Before we had started working on our project, we had to analyze the overall network to come up with test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software. 
-Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. One of our goals was to make it user-friendly and as simple as possible to use. In the following chapters we will describe in more detail our approach and how each subsystem works.
+Gradually we implemented a bit-by-bit of the final software. Every single step was accompanied by testing and validation procedures. At the end we connected all the ``black-boxes'' into one big piece of software. We have fulfilled our requests and goals and made a fully working and operable test software. Despite developing a working software, all the way along we thought about the simplicity of the usage of the software. In the following chapters we will describe in more detail our approach and how each subsystem works.
 \newpage
 \section{Software concept}           % chapter 2
 \newpage
 \section{Introduction}     % section 2.1
-\newpage
 \subsection{Usage}         % subsection 2.1.1
+\newpage
 \section{Design}
 \newpage
 \section{Protocol}
@@ -136,6 +136,13 @@ b
 \end{lstlisting}
 \newpage
 \section{Web page}
+
+\begin{figure}
+  \centering
+  \includegraphics[width=100mm]{resultsImage.png}
+  \caption[]{Result image showing working, defected and not tested subsystems}
+\end{figure}
+
 \newpage
 \section{Conclusion}
 \newpage
-- 
cgit v1.2.3-55-g7522

