summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-20 16:41:22 +0200
committerRefik Hadzialic2011-10-20 16:41:22 +0200
commit5c080b0ec7274e26027f80f8a8ca01d0b219bd79 (patch)
treead6f9b521677127b839f9255642a6068c409d4f4 /notFinishedCode/Report/test.tex
parentReport writing (diff)
downloadgsm-selftest-5c080b0ec7274e26027f80f8a8ca01d0b219bd79.tar.gz
gsm-selftest-5c080b0ec7274e26027f80f8a8ca01d0b219bd79.tar.xz
gsm-selftest-5c080b0ec7274e26027f80f8a8ca01d0b219bd79.zip
Requirements writing!
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex20
1 files changed, 17 insertions, 3 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index f20b34c..3037ee4 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -104,14 +104,22 @@ Gradually we implemented a bit-by-bit of the final software. Every single step w
\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 goal of our team project. It was to build a
+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 the figure 1 and depending on it to build our test software.
+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 system}
+ \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. One of the requirements by Dennis and Konrad was to make the software caable of being run from the terminal.
\newpage
\section{Database design}
At the start our database of choice was MySQL.
@@ -532,6 +540,12 @@ If one of the fields is red it means the subsystem is not online or cannot be se
%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}.