summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex.backup
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-22 14:53:37 +0200
committerRefik Hadzialic2011-10-22 14:53:37 +0200
commit535de7267c6eee26aa00e39d10b5abe6b8a04ee3 (patch)
treebcbcb961021ebac95e3f3a389f63b49c340429d7 /notFinishedCode/Report/test.tex.backup
parentdefine timeout (diff)
downloadgsm-selftest-535de7267c6eee26aa00e39d10b5abe6b8a04ee3.tar.gz
gsm-selftest-535de7267c6eee26aa00e39d10b5abe6b8a04ee3.tar.xz
gsm-selftest-535de7267c6eee26aa00e39d10b5abe6b8a04ee3.zip
Report writing
Diffstat (limited to 'notFinishedCode/Report/test.tex.backup')
-rw-r--r--notFinishedCode/Report/test.tex.backup17
1 files changed, 14 insertions, 3 deletions
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 4e3b28d..77dea01 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -145,7 +145,7 @@ We decided to use MySQL since it is open source and well supported. However, one
\subsection{Hardware requirements}
Likewise the software requirements, we had hardware requirements as well. We were required to identify the hardware we will need to perform the tests.
It was important to find old and cheap cell phones that could support \emph{AT Modem} commands because our budget was limited.
-\par A problem we had to face at the start was that the base stations are located at different geographical points which were not near to each other.
+\par A problem we had to deal with at the start was that the base stations are located at different geographical points which were not near to each other.
No one should go everyday to the rooms where our cell phones are located only to change or charge the batteries.
In the cable subsection we describe our approach to the charging battery problem. As we defined our requirements we continued with the process of developing the test software.
During the development time we refined our requirements. In the next chapters we will explain our database, software and hardware design ideas.
@@ -159,21 +159,32 @@ The key point in the design of our database was the simplicity and speed of acce
\includegraphics[width=140mm]{DBRelationship.png}
\caption[]{Database relationship diagram}
\end{figure}
+
\par The \emph{PingResultTable} table has six attributes (\emph{taskNo, sipServer, sipGate, unisip, gsmBox1, gsmBox2}), all of integer type.
The \emph{taskNo} attribute identifies the test number but not a single test (e.g. an operator user has selected three different tests to be executed, all of the three tests will have the same \emph{taskNo} to identify them together as belonging to one test group and \emph{taskId} identifies each single test and will be explained later).
\emph{sipServer} represents the Asterisk server ping result. \emph{sipGate} is used to represent the SIP Gate server for the landline calls (\url{http://www.sipgate.de}). \emph{uniSip} represents the ping results for our local University telephone network SIP server.
\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, 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).
+
+\par The \emph{ErrorCodeTable} table defines all the possible test results in the system, in other words it represents a list with error codes with their appropriate descriptions and 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, \emph{deviceName, portName, number, lastChange, username, password, server}.
\emph{deviceName} is the attribute with the name of the device or server (e.g. GSMRZ1 or landline), it is of varchar type. \emph{portName} is the attribute field with the location address for a cell phone (e.g. \emph{/dev/ttyUSB1}) or 'localhost' instead of NULL value for a server, it is of the varchar type.
\emph{number} represents the number of the used service (i.e. number of the cell phone, SIP, etc.) and is of varchar type.
\emph{lastChange} is a time value and represents the date and time the given entry was modified (we had plans in future versions of our test software that if an device gets a new IP address assigned it automatically changes it in the database).
\emph{username} is the field with the username stored in for a server/service, like SIP and landline. \emph{password} attribute stores the password information for the given service. The \emph{server} attribute stores information about the location of the server, IP or DNS address of the server. All three fields, \emph{username}, \emph{password} and \emph{server} are of varchar type.
The information stored in the given table is used by the test software to obtain usernames, passwords and addresses of the used services for the tests.
-\par The \emph{ResultTable} table is used by the test system to store final results for the test cases.
+
+\par The \emph{ResultTable} table is used by the test system to store final results for the performed tests. Our given table consists of two fields, \emph{taskID} and \emph{result} and both are of integer type. For each test entry with unique \emph{taskID} an error code is assigned in the \emph{result} field,
+depending on the test results. Error codes found in the \emph{ErrorCodeTable} table can be only assigned to this field.
+
+\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, the test tasks are kept in the \emph{TaskTable}. We divided this
+
+\par The \emph{TaskTable} table contains all the tests ever performed from the web site.
+
\newpage
\section{Software design} % section 2.1
\begin{figure}[ht!]