summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex~
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-21 15:52:15 +0200
committerRefik Hadzialic2011-10-21 15:52:15 +0200
commitccab309ae147186f518bb530b94eb637addda9ba (patch)
tree4bc52b50f0a0a533661db53f4d55300173740401 /notFinishedCode/Report/test.tex~
parentReport writing! (diff)
downloadgsm-selftest-ccab309ae147186f518bb530b94eb637addda9ba.tar.gz
gsm-selftest-ccab309ae147186f518bb530b94eb637addda9ba.tar.xz
gsm-selftest-ccab309ae147186f518bb530b94eb637addda9ba.zip
Report writing!
Diffstat (limited to 'notFinishedCode/Report/test.tex~')
-rw-r--r--notFinishedCode/Report/test.tex~6
1 files changed, 4 insertions, 2 deletions
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 63e0c39..a38ea54 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -153,7 +153,7 @@ During the development time we refined our requirements. In the next chapters we
\section{Database design}
As we mentined in the software requirements section, we decided to use MySQL as our database system for storing the test information and results.
It was not difficult to decide what database to use, since MySQL is one of the most supported database and one can find a library to use it with major programming languages.
-The key point in the design of our database was the simplicity and speed of accessing the data. We had decided to use seven tables. In the following paragraph we will explain each table separately and its usage.
+The key point in the design of our database was the simplicity and speed of accessing the data. We had decided to use seven tables. In the following paragraphs we will explain each table separately and its usage.
\begin{figure}[ht!]
\centering
\includegraphics[width=140mm]{DBRelationship.png}
@@ -165,7 +165,9 @@ The \emph{taskNo} attribute identifies the test number but not a single test (e.
\emph{gsmBox1} and \emph{gsmBox2} are the two single-chip Linux computers (BeagleBoard), that controll two cell phones each one (i.e. they are also known under the name of \emph{nanoBTSx}).
\emph{taskNo} is the primary and unique key in the table \emph{PingResultTable}. Rest of the attributes (i.e. \emph{sipServer, sipGate, uniSip, gsmBox1, gsmBox2}) are used to insert the ping results, if the assigned servers are reachable or not.
Before any test attempt is made, our test software first tries to ping the servers. These results are then stored in the \emph{PingResultTable}.
-\par The \emph{ErrorCodeTable} table defines all the error codes in the project
+\par The \emph{ErrorCodeTable} table defines all the error codes in the project, in other words it represents a list with error codes with their meanings. It consists of two attributes (\emph{errorcode} and \emph{description}), the first is of integer type and the second of varchar type (the description message is allowed to be only 100 characters long).
+The \emph{ErrorCodeTable} table is used by the main test software (i.e. controller) to report the operator user what kind of error had appeared in the system.
+\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes.
\newpage
\section{Software design} % section 2.1
\begin{figure}[ht!]