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.tex21
1 files changed, 13 insertions, 8 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 5dc0feb..4d0ae3b 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -333,12 +333,13 @@ It selects automatically the important tests to perform. In the next step it
tries to identify the problem in the network.
More details can be found in the \emph{smart test} description.
\subsection{Controller class}
-The controller class is used to assign jobs to handlers (e.g. which one is going to be the caller
-and callee). Simultaneously, it defines the port address for the communication between
-the handlers and controller. If the callee or the caller are nanoBTS control
-boxes (i.e. BeagleBoards outside the Rechenzentrum), it will first create an
-SSH connection to make a tunnel before the local connection is created.
-The controller class sends all the required data regarding the test task to the handler.
+The controller class is used to assign jobs to handlers (in other words, which one is
+going to be the caller and callee). Simultaneously, it defines the port addresses for
+the communication between the handlers and the main test software (controller).
+If the callee or the caller are nanoBTS control boxes (i.e. BeagleBoards outside
+the Rechenzentrum), it will first create an SSH connection to make a tunnel before
+the local socket connection is created. Then the controller class sends all the
+required data regarding the test tasks to the handlers.
\clearpage
\section{Hardware design}
@@ -696,7 +697,7 @@ where it automatically shuts down.
All the performed test results are displayed on the web site. The results are displayed in real time after each selected test case is performed.
After all the test cases have been performed a topological picture is generated which represents the current state of the system, this can bee seen in the following figure.
Afterwards, when the result picture is generated, the test user can easily see what is wrong in the system. Various icons represent different subsystems.
-Reading the test results is simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
+Reading the test results is as simple as looking at the icons and identifying if they have: a green plus signs (i.e. working properly), a red minus sign (i.e. not working properly) and a yellow exclamation mark (i.e. it was not tested).
\begin{itemize}
\item Triangles represent BTS stations
@@ -716,7 +717,11 @@ We use the pChart library\footnote{It is under the GNU GPLv3 license and our pro
\par On the right side of the result picture the test user can immediatelly identify the network operability in percentage\footnote{The test user has to take into account that this percantage is only valid if a full test is performed.}. Bellow the network operability statistics are the ping results statistics located.
If one of the fields is red it means the subsystem is not online or cannot be seen by our server computer where the test software is located.
\newpage
-\section{How to use and start the system}
+\section{Employing the test system software}
+In this section the reader can find out how to install and how to use the test system.
+Our goal was to make a multiplatform test software, however we tested it only under Ubuntu
+11.04 32 bit Linux OS and the given instruction manual is only tested under that operating
+system.
\subsection{Required libraries}
\subsection{Configuring hardware}
\newpage