summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-22 23:18:43 +0200
committerRefik Hadzialic2011-10-22 23:18:43 +0200
commit2375bb932bd2e68a3aa7c9e4f774ac7bc976e526 (patch)
treed4f2ae79af593401498d408aae8aeaf5efa1a788 /notFinishedCode/Report/test.tex
parentReport writing (diff)
downloadgsm-selftest-2375bb932bd2e68a3aa7c9e4f774ac7bc976e526.tar.gz
gsm-selftest-2375bb932bd2e68a3aa7c9e4f774ac7bc976e526.tar.xz
gsm-selftest-2375bb932bd2e68a3aa7c9e4f774ac7bc976e526.zip
Report writing
Diffstat (limited to 'notFinishedCode/Report/test.tex')
-rw-r--r--notFinishedCode/Report/test.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 7f8188a..0b8b1d0 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -313,7 +313,7 @@ response from the other side. Our approch to this problem was to build a simple
confirmed or otherwise the connection between two sides is immediatelly terminated. Since designing protocols is a demanding and challenging
topic which requires years of experience and verification, we do not expect that we had developed the best possible and an optimum
protocol\footnote{Design concepts and paradigms for the protocol design have been used from the
-``Network Protocol Design and Evaluation'' course, lectured by Stefan R\"{u}hrup}.
+``Network Protocol Design and Evaluation'' course, lectured by Dr. Stefan R\"{u}hrup}.
In the following paragraphs we will try to clarify how our protocol works. Before we start to go into detail how the protocol works,
it is important to remember that we differentiate two sides, handler and the controller side. The handler side represent the device
that physically handles the call (e.g. the BeagleBoard) whereas the controller (i.e. the main test software), is the test software