summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-22 15:04:44 +0200
committerRefik Hadzialic2011-10-22 15:04:44 +0200
commit54063a2139ec1f8a85ec0c6445eda505e184c194 (patch)
tree4bc95361c63066b2be85d8977c67fedb6eb9c7b6 /notFinishedCode/Report/test.tex
parentReport writing (diff)
downloadgsm-selftest-54063a2139ec1f8a85ec0c6445eda505e184c194.tar.gz
gsm-selftest-54063a2139ec1f8a85ec0c6445eda505e184c194.tar.xz
gsm-selftest-54063a2139ec1f8a85ec0c6445eda505e184c194.zip
Rerport writing
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index eb4f177..8f684a3 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -151,7 +151,7 @@ In the cable subsection we describe our approach to the charging battery problem
During the development time we refined our requirements. In the next chapters we will explain our database, software and hardware design ideas.
\newpage
\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.
+As we mentioned 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 paragraphs we will explain each table separately and its usage.
\begin{figure}[ht!]
@@ -182,9 +182,9 @@ depending on the test results. Error codes found in the \emph{ErrorCodeTable} ta
\par The \emph{TempTaskTable} table represents the table with the tasks the system has to execute next time the test software is started. The given table gets new data every time an operator user submits one or more test cases from the website to be executed. \emph{TempTaskTable} includes four attributes, \emph{taskID, taskNo, from, to}. Former two are of integer type and later two of varchar type.
\emph{taskID} and \emph{taskNo} identify the test task to be executed, \emph{taskID} is the unique primary key. \emph{from} and \emph{to} fields have to match the names given in \emph{DeviceAddressTable.deviceName}, these two attributes specify the caller and callee devices/services. Consequently, after the tasks get executed, the test tasks are removed and the given table is empty again until next tests are added to it.
-However, all the test tasks even after deleting them from \emph{TempTaskTable} are kept in the \emph{TaskTable}. The reason why the authors of this project divided it into two tables was because of the database row selection speed.
+However, all the test tasks even after deleting them from \emph{TempTaskTable} are kept in the \emph{TaskTable}. The reason why the authors of this project divided it into two tables was because of the database row selection speed. We had made the assumption that with time the database size will grow and therefore the database speed will not be the same as during the development period.
-\par The \emph{TaskTable} table contains all the tests ever performed from the web site.
+\par The \emph{TaskTable} table, as mentioned before contains all the tests ever performed from the web site. It is made out of five attributes, \emph{taskID, taskNo, from, to, timestamp}. The first four fields are the same as in \emph{TempTaskTable}, however the last one, \emph{timestamp}, is used to record the exact time when the test was performed.
\newpage
\section{Software design} % section 2.1