summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex.backup
diff options
context:
space:
mode:
authorgsmselftest2011-10-20 17:01:29 +0200
committergsmselftest2011-10-20 17:01:29 +0200
commit6d2d33198b5eb76c9224e2ea4bc67824f5765a8d (patch)
treec1bb729cf779a6d6e93f6389ff28214ac153127f /notFinishedCode/Report/test.tex.backup
parentlast edtign (diff)
parentRequirements writing! (diff)
downloadgsm-selftest-6d2d33198b5eb76c9224e2ea4bc67824f5765a8d.tar.gz
gsm-selftest-6d2d33198b5eb76c9224e2ea4bc67824f5765a8d.tar.xz
gsm-selftest-6d2d33198b5eb76c9224e2ea4bc67824f5765a8d.zip
Merge branch 'master' of lab.ks.uni-freiburg.de:lsfks/projekte/gsm-selftest
Diffstat (limited to 'notFinishedCode/Report/test.tex.backup')
-rw-r--r--notFinishedCode/Report/test.tex.backup37
1 files changed, 35 insertions, 2 deletions
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 7c427aa..cd4ce7b 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -79,10 +79,10 @@ escapeinside={\%}{)} % if you want to add a comment within your code
\titlepic{\includegraphics[width=70mm]{uniLogo1.jpg}}
\title{Team project \\ ``\titleOfProject''} % type title between braces
\date{\today} % type date between braces
-\author{Arda Akcay\\ Tri Atmoko\\ Refik Had\v{z}iali\'{c} } % type author(s) between braces
+\author{Tri Atmoko\\ Refik Had\v{z}iali\'{c} } % type author(s) between braces
\department{\vspace{1\baselineskip} \large Albert-Ludwigs-Universit\"{a}t Freiburg \\
Lehrstuhl f\"{u}r Komunikationsysteme\\
-Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Meier \\ Denis Wehrle \\ \vspace{1\baselineskip} Sommersemester 2011}
+Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Maier \\ Dennis Wehrle \\ \vspace{1\baselineskip} Sommersemester 2011}
\maketitle
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -103,6 +103,23 @@ Before we had started working on our project, we had to analyze the overall netw
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.
\clearpage
\section{Requirements} % chapter 2
+At the start of the project the requirements were not completely known but as the time passed we redefined our goals.
+The first and the most important part at the start was to define the key goals of our team project. It was to build a
+test software system which could tell the operator user what is not preoperly working in our local University telecommunication network.
+Konrad and Dennis suggested us to look at figure 1 and depending on it to build our test software.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=140mm]{BigPicture_new1.png}
+ \caption[]{Overview of the Freiburg University telecommunication network \cite{network}}
+\end{figure}
+Our first objective was to see what could we test without having access to the system. We installed various communication programs to see what others have done.
+After gaining access to the communication software we had decided to build most of the test software ourselves. Libraries, which were used,
+were only the ones we could not develop ourself because of the time-span of our team project.
+\par Afterward we had to choose the programming language. Since we had the freedom of choice, between the three suggested programming languages
+Java, C++ and Python, we made a joint decision to use Python as the main programming language in our team project. One of the requirements was to finish the team project in time,
+therefore our decision to use Python is justified. Using Python we could work faster and integrate our subsystems more effectively \cite{python}.
+Our programming language of choice is multiplatform, therefore our test software would be easy portable to other operating systems.
+\par Likewise we had to decide how our test software will work.
\newpage
\section{Database design}
At the start our database of choice was MySQL.
@@ -171,11 +188,15 @@ A ping timeout response was set up to 2 seconds. For more details and insights,
\caption[]{Ping class, used by test software}
\end{figure}
\subsection{Data logging}
+If bugs appear it is important to reconstruct the case. One of the best ways to reconstruct the case was to log every single step part of code gets executed.
+We had used the logging class to follow our handler code run on the BeagleBoard. In case there is an error we could look inside of the log files and track the error.
+How the class works and what kind of outputs it produces can be found on our project wiki page \cite{wiki}.
\begin{figure}[ht!]
\centering
\includegraphics[width=60mm]{logging.png}
\caption[]{Logging class}
\end{figure}
+\subsection{SSH Class}
\clearpage
\section{Hardware design}
In our team project we had the option to choose all the required hardware ourself beside the two BeagleBoards, which we were supplied by Konrad and Dennis.
@@ -507,12 +528,24 @@ 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}
+\subsection{Required libraries}
+\subsection{Configuring hardware}
+\newpage
\section{Conclusion}
\newpage
+
+
%bibliography start
\begin{thebibliography}{9}
+\bibitem{network} \emph{Projects based on RZ-GSM}, accessed on 20.06.2011, available at
+\url{http://lab.ks.uni-freiburg.de/projects/gsm/wiki}.
+
+\bibitem{python} \emph{Projects based on RZ-GSM}, accessed on 20.06.2011, available at
+\url{http://lab.ks.uni-freiburg.de/projects/gsm/wiki}.
+
\bibitem{mysqlManual} \emph{MySQLdb User's Guide}, accessed on 05.06.2011, available at \\
\url{http://mysql-python.sourceforge.net/MySQLdb.html}.