summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex16
1 files changed, 11 insertions, 5 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 94b5c9f..6bd90c1 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -100,9 +100,8 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
\section{Introduction and Motivation} % chapter 1
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 land-line 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 from an external perspective 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 the 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 requirements, goals and made a fully 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 to the problem and how each subsystem works.
-This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software. Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
+Gradually we implemented a bit-by-bit of the final software. In the following chapters we will describe in more detail our approach to the problem and how each subsystem works.
+This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software.
\clearpage
\section{Requirements} % chapter 2
At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
@@ -302,10 +301,15 @@ How the class works and what kind of outputs it produces can be found on our pro
\includegraphics[width=60mm]{logging.png}
\caption[]{Logging class}
\end{figure}
-\subsection{SSH Class}
+\subsection{SSH Tunnel Class}
Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
All data sent through the created port is encrypted until it gets to its destination location.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=60mm]{sshTunnelClass.png}
+ \caption[]{SSH Tunnel class}
+\end{figure}
\subsection{USB Cell phone detection class}
Since we had used cables to connect the cell phones with the computer, usually the devices
got their own port addresses. They were automatically assigned by the operating system,
@@ -820,7 +824,9 @@ sudo easy_install setproctitle
\newpage
\section{Conclusion}
-
+We had successfully finished our team project. 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 requirements, goals and made a fully operable test software.
+Despite the fact that we created a fully working and operable software, all the way along we thought about the simplicity of the usage of the software.
+Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
\newpage