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.tex~13
1 files changed, 12 insertions, 1 deletions
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index cb5b00f..06aa99e 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -103,7 +103,7 @@ 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.
+At the start of the project the requirements were not completely known but as the had time passed we redefined our requirements and 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 properly 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.
@@ -115,6 +115,14 @@ Konrad and Dennis suggested us to look at figure 1 and depending on it to build
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.
+\subsection{Logical and algorithmic requirements}
+\par Another requirement was to draw a use case diagram and a simple test case diagram so that we could better identify all the problems we had to deal but also to easier follow the development of our test software.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=100mm]{activity_diagram.png}
+ \caption[]{Simple algorithmic overview of a test case}
+\end{figure}
+\subsection{Software requirements}
\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}.
@@ -124,6 +132,9 @@ The next requirement was to make a good looking GUI so that even an operator use
\par In addition it was required to log all the past test. Later on a machine learning algorithm or some other intelligence could be applied to deduce some error behavior of the system
(e.g. an intelligent algorithm could find that part of the system fail in a combined manner). To accomplish the logging of all the tests we had to use a database system.
We decided to use MySQL since it is open source and well supported. However, one should know that the test results are only stored into the database in case the test was started from the web site.
+
+\subsection{Hardware requirements}
+\par Beside the software requirements we had hardware requirements as well.
\newpage
\section{Database design}
At the start our database of choice was MySQL.