summaryrefslogtreecommitdiffstats
path: root/notFinishedCode
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode')
-rw-r--r--notFinishedCode/Report/.test.tex.kate-swpbin0 -> 851 bytes
-rw-r--r--notFinishedCode/Report/.~lock.Tri-report.doc#1
-rw-r--r--notFinishedCode/Report/sshTunnelClass.pngbin0 -> 8853 bytes
-rw-r--r--notFinishedCode/Report/test.aux17
-rw-r--r--notFinishedCode/Report/test.log44
-rw-r--r--notFinishedCode/Report/test.pdfbin1458861 -> 1468020 bytes
-rw-r--r--notFinishedCode/Report/test.tex16
-rw-r--r--notFinishedCode/Report/test.tex.backup30
-rw-r--r--notFinishedCode/Report/test.tex~19
-rw-r--r--notFinishedCode/Report/test.toc4
10 files changed, 80 insertions, 51 deletions
diff --git a/notFinishedCode/Report/.test.tex.kate-swp b/notFinishedCode/Report/.test.tex.kate-swp
new file mode 100644
index 0000000..724fd01
--- /dev/null
+++ b/notFinishedCode/Report/.test.tex.kate-swp
Binary files differ
diff --git a/notFinishedCode/Report/.~lock.Tri-report.doc# b/notFinishedCode/Report/.~lock.Tri-report.doc#
new file mode 100644
index 0000000..5f9393a
--- /dev/null
+++ b/notFinishedCode/Report/.~lock.Tri-report.doc#
@@ -0,0 +1 @@
+Refik ,refik,ubuntu.ubuntu-domain,25.10.2011 14:17,file:///home/refik/.libreoffice/3; \ No newline at end of file
diff --git a/notFinishedCode/Report/sshTunnelClass.png b/notFinishedCode/Report/sshTunnelClass.png
new file mode 100644
index 0000000..de522f0
--- /dev/null
+++ b/notFinishedCode/Report/sshTunnelClass.png
Binary files differ
diff --git a/notFinishedCode/Report/test.aux b/notFinishedCode/Report/test.aux
index 8e95aa5..3b64ae0 100644
--- a/notFinishedCode/Report/test.aux
+++ b/notFinishedCode/Report/test.aux
@@ -36,19 +36,20 @@
\@writefile{lof}{\contentsline {figure}{\numberline {10}{\ignorespaces }}{15}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}Ping class}{15}}
\citation{wiki}
-\citation{wiki}
\@writefile{lof}{\contentsline {figure}{\numberline {11}{\ignorespaces }}{16}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.5}Data logging}{16}}
\@writefile{lof}{\contentsline {figure}{\numberline {12}{\ignorespaces }}{16}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.6}SSH Class}{16}}
-\@writefile{toc}{\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{16}}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.6}SSH Tunnel Class}{16}}
+\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces }}{16}}
+\citation{wiki}
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{17}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.8}Truth table class}{17}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.9}Init Test class}{17}}
\@writefile{toc}{\contentsline {subsection}{\numberline {4.10}Controller class}{17}}
\citation{beagleDataSheet}
\@writefile{toc}{\contentsline {section}{\numberline {5}Hardware design}{18}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.1}BeagleBoard}{18}}
-\@writefile{lof}{\contentsline {figure}{\numberline {13}{\ignorespaces }}{18}}
+\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces }}{18}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.2}Cell phones}{19}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.3}Cables for the cell phones}{19}}
\@writefile{toc}{\contentsline {subsection}{\numberline {5.4}Server}{19}}
@@ -57,14 +58,14 @@
\citation{spin}
\citation{spin}
\citation{wiki}
-\@writefile{lof}{\contentsline {figure}{\numberline {14}{\ignorespaces }}{21}}
\@writefile{lof}{\contentsline {figure}{\numberline {15}{\ignorespaces }}{21}}
+\@writefile{lof}{\contentsline {figure}{\numberline {16}{\ignorespaces }}{21}}
\@writefile{toc}{\contentsline {subsection}{\numberline {6.2}Verification of the protocol}{21}}
-\@writefile{lof}{\contentsline {figure}{\numberline {16}{\ignorespaces }}{22}}
+\@writefile{lof}{\contentsline {figure}{\numberline {17}{\ignorespaces }}{22}}
\citation{sshTunnel}
\@writefile{toc}{\contentsline {section}{\numberline {7}Security and safety of the system}{24}}
\@writefile{toc}{\contentsline {subsection}{\numberline {7.1}Encryption of the communication channels}{24}}
-\@writefile{lof}{\contentsline {figure}{\numberline {17}{\ignorespaces }}{24}}
+\@writefile{lof}{\contentsline {figure}{\numberline {18}{\ignorespaces }}{24}}
\citation{https}
\@writefile{toc}{\contentsline {subsection}{\numberline {7.2}Security on the web site}{25}}
\citation{https}
@@ -73,7 +74,7 @@
\@writefile{toc}{\contentsline {subsection}{\numberline {8.1}Communication between the web page and the test software}{29}}
\@writefile{toc}{\contentsline {subsection}{\numberline {8.2}Results on the web page}{29}}
\citation{pChart}
-\@writefile{lof}{\contentsline {figure}{\numberline {18}{\ignorespaces }}{30}}
+\@writefile{lof}{\contentsline {figure}{\numberline {19}{\ignorespaces }}{30}}
\@writefile{toc}{\contentsline {section}{\numberline {9}Employing the test software system}{31}}
\@writefile{toc}{\contentsline {subsection}{\numberline {9.1}Required software and libraries}{31}}
\@writefile{toc}{\contentsline {subsubsection}{\numberline {9.1.1}Python installation}{31}}
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index b80cbfd..9b53343 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 25 OCT 2011 20:07
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 25 OCT 2011 21:03
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -322,29 +322,29 @@ File: test_Use_case.png Graphic file (type png)
<DBRelationship.png, id=43, 1638.12pt x 700.6175pt>
File: DBRelationship.png Graphic file (type png)
<use DBRelationship.png>
-LaTeX Font Info: Try loading font information for T1+cmtt on input line 165.
+LaTeX Font Info: Try loading font information for T1+cmtt on input line 164.
(/usr/share/texmf-texlive/tex/latex/base/t1cmtt.fd
File: t1cmtt.fd 1999/05/25 v2.5h Standard LaTeX font definitions
) [9 <./DBRelationship.png>]
[10]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 198.
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 197.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 198.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 197.
<activityControllerEdited.png, id=52, 720.44156pt x 453.19313pt>
File: activityControllerEdited.png Graphic file (type png)
<use activityControllerEdited.png>
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 222.
+(Font) <9> on input line 221.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 222.
+(Font) <5> on input line 221.
[11 <./activityControllerEdited.png>]
<classDiagram.png, id=58, 1027.84pt x 558.085pt>
File: classDiagram.png Graphic file (type png)
@@ -370,46 +370,50 @@ File: ping.png Graphic file (type png)
File: logging.png Graphic file (type png)
<use logging.png> [15 <./serverClass.png (PNG copy)> <./ClientClass.png (PNG co
-py)>] [16 <./ping.png (PNG copy)> <./logging.png (PNG copy)>] [17]
-<bb.jpg, id=87, 521.95pt x 516.93124pt>
+py)>] <sshTunnelClass.png, id=81, 486.05118pt x 235.23177pt>
+File: sshTunnelClass.png Graphic file (type png)
+
+<use sshTunnelClass.png> [16 <./ping.png (PNG copy)> <./logging.png (PNG copy)>
+ <./sshTunnelClass.png (PNG copy)>] [17]
+<bb.jpg, id=88, 521.95pt x 516.93124pt>
File: bb.jpg Graphic file (type jpg)
<use bb.jpg> [18
<./bb.jpg>] [19]
[20
-] <protocolCommunicationHandler.png, id=99, 2486.93823pt x 792.13588pt>
+] <protocolCommunicationHandler.png, id=100, 2486.93823pt x 792.13588pt>
File: protocolCommunicationHandler.png Graphic file (type png)
<use protocolCommunicationHandler.png>
-<protocolCommunicationcControllerReceiver.png, id=100, 1808.16705pt x 766.62883
+<protocolCommunicationcControllerReceiver.png, id=101, 1808.16705pt x 766.62883
pt>
File: protocolCommunicationcControllerReceiver.png Graphic file (type png)
<use protocolCommunicationcControllerReceiver.png>
-<protocolCommunicationcControllerCaller.png, id=101, 1808.16705pt x 766.62883pt
+<protocolCommunicationcControllerCaller.png, id=102, 1808.16705pt x 766.62883pt
>
File: protocolCommunicationcControllerCaller.png Graphic file (type png)
<use protocolCommunicationcControllerCaller.png> [21 <./protocolCommunicationH
andler.png (PNG copy)> <./protocolCommunicationcControllerReceiver.png (PNG cop
y)>] [22 <./protocolCommunicationcControllerCaller.png (PNG copy)>] [23]
-<sshTunnel.png, id=112, 696.6025pt x 152.57pt>
+<sshTunnel.png, id=113, 696.6025pt x 152.57pt>
File: sshTunnel.png Graphic file (type png)
<use sshTunnel.png> [24
<./sshTunnel.png (PNG copy)>] [25] [26]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 625.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 629.
[27] [28] [29]
-<resultsImage.png, id=132, 702.625pt x 431.6125pt>
+<resultsImage.png, id=133, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
<use resultsImage.png>
[30 <./resultsImage.png (PNG copy)>] [31] [32] [33] [34]
AED: lastpage setting LastPage [35] (./test.aux) )
Here is how much of TeX's memory you used:
- 4949 strings out of 495061
- 68803 string characters out of 1182621
+ 4954 strings out of 495061
+ 68912 string characters out of 1182621
255285 words of memory out of 3000000
- 8055 multiletter control sequences out of 15000+50000
+ 8059 multiletter control sequences out of 15000+50000
17720 words of font info for 42 fonts, out of 3000000 for 9000
28 hyphenation exceptions out of 8191
36i,11n,45p,760b,1679s stack positions out of 5000i,500n,10000p,200000b,50000s
@@ -427,9 +431,9 @@ ur/jknappen/ec/ecsx1440.600pk> </home/refik/.texmf-var/fonts/pk/ljfour/jknappen
sr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi10.pfb></usr/share/te
xmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive
/fonts/type1/public/amsfonts/cm/cmsy9.pfb>
-Output written on test.pdf (35 pages, 1458861 bytes).
+Output written on test.pdf (35 pages, 1468020 bytes).
PDF statistics:
- 741 PDF objects out of 1000 (max. 8388607)
+ 742 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
- 96 words of extra memory for PDF output out of 10000 (max. 10000000)
+ 101 words of extra memory for PDF output out of 10000 (max. 10000000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index aaf541f..f69b9da 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 94b5c9f..6bd90c1 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -100,9 +100,8 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
\section{Introduction and Motivation} % chapter 1
In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems from an external perspective and infer the results out of our findings.
Before we had started working on our project, we had to analyze the overall network to come up with the test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
-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 requirements, goals and made a fully 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 to the problem and how each subsystem works.
-This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software. Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
+Gradually we implemented a bit-by-bit of the final software. In the following chapters we will describe in more detail our approach to the problem and how each subsystem works.
+This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software.
\clearpage
\section{Requirements} % chapter 2
At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
@@ -302,10 +301,15 @@ How the class works and what kind of outputs it produces can be found on our pro
\includegraphics[width=60mm]{logging.png}
\caption[]{Logging class}
\end{figure}
-\subsection{SSH Class}
+\subsection{SSH Tunnel Class}
Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
All data sent through the created port is encrypted until it gets to its destination location.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=60mm]{sshTunnelClass.png}
+ \caption[]{SSH Tunnel class}
+\end{figure}
\subsection{USB Cell phone detection class}
Since we had used cables to connect the cell phones with the computer, usually the devices
got their own port addresses. They were automatically assigned by the operating system,
@@ -820,7 +824,9 @@ sudo easy_install setproctitle
\newpage
\section{Conclusion}
-
+We had successfully finished our team project. 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 requirements, goals and made a fully operable test software.
+Despite the fact that we created a fully working and operable software, all the way along we thought about the simplicity of the usage of the software.
+Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
\newpage
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 2e48780..5eab6fb 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -100,9 +100,8 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
\section{Introduction and Motivation} % chapter 1
In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems from an external perspective and infer the results out of our findings.
Before we had started working on our project, we had to analyze the overall network to come up with the test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
-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 requirements, goals and made a fully 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 to the problem and how each subsystem works.
-This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software. Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
+Gradually we implemented a bit-by-bit of the final software. In the following chapters we will describe in more detail our approach to the problem and how each subsystem works.
+This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software.
\clearpage
\section{Requirements} % chapter 2
At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
@@ -192,12 +191,11 @@ attributes, both of varchar type, \emph{providerName} and \emph{prefix}.
Software design was the next step after we analyzed the problem and developed a plan how to proceed further. Good analysis and planning with poor algorithmic implementation is valueless.
During the work on the project, we had spent most of our time for software design.
We kept in mind that our software should satisfy major paradigms of software engineering,
-like compatibility, extensibility, maintability, modularity, relliability, security, fault-tolerance and usability.
+like compatibility, extensibility, modularity, relliability, security, fault-tolerance and usability.
The software engineering design concepts were achieved following way:
\begin{itemize}
\item Compatibility - we used Python and MySQL which are multiplatform and work on major OS
\item Extensibility - new parts of code can be easily added by just modifying the classes
-\item Maintability - the test software can recognize new added cell phones to the system and dynamically perform tests if new BTS stations are added
\item Mudalarity - the components are independent black boxes, they are tested and validated independently
\item Reliability - we use mutex locks to perform tests and database transaction operations to insert data into the database
\item Security - all communication channels, as well as the access to the web site, are encrypted with asymmetric key cryptography
@@ -303,10 +301,15 @@ How the class works and what kind of outputs it produces can be found on our pro
\includegraphics[width=60mm]{logging.png}
\caption[]{Logging class}
\end{figure}
-\subsection{SSH Class}
+\subsection{SSH Tunnel Class}
Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
All data sent through the created port is encrypted until it gets to its destination location.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=60mm]{sshTunnelClass.png}
+ \caption[]{SSH Tunnel class}
+\end{figure}
\subsection{USB Cell phone detection class}
Since we had used cables to connect the cell phones with the computer, usually the devices
got their own port addresses. They were automatically assigned by the operating system,
@@ -719,6 +722,7 @@ Our goal was to make a multiplatform test software, however we tested it only un
test software performed well, both on PC and MAC computers.
One should keep in mind that some of the libraries we had used do not work
under the 64 bit version of Linux OS.
+
\subsection{Required software and libraries}
In the next subsections, we will guide you how to install all the required software and
libraries to flawlessly run our test software on your employed server.
@@ -750,9 +754,15 @@ After the installation has completed successfully, one can test if it works by g
to the following web address: \emph{http://localhost}. For configuring the \emph{https}
please go to the section 7.2.
+\subsubsection{SSH}
+Secure Shell (SSH) is a network protocol for secure data communication between two
+computers inside of a network. All computers are required to have SSH installed on it.
+You can easily install it by typing the following command:
+\begin{lstlisting}
+sudo apt-get install ssh
+\end{lstlisting}
-
-\subsubsection{MySQL database and MySQL library}
+\subsubsection{MySQL database and MySQLdb library}
The MySQLdb library is required to perform various operations on the MySQL database within
Python. We used the MySQLdb library instead of the native MySQL C API \emph{\_mysql} library
to make the code cleaner and more portable.
@@ -814,7 +824,9 @@ sudo easy_install setproctitle
\newpage
\section{Conclusion}
-
+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 requirements, goals and made a fully operable test software.
+Despite the fact that we created a fully working and operable software, all the way along we thought about the simplicity of the usage of the software.
+Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
\newpage
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index fb17a36..5eab6fb 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -100,9 +100,8 @@ Prof. Dr. Gerhard Schneider\\ \vspace{1\baselineskip} Supervisors: \\ Konrad Mai
\section{Introduction and Motivation} % chapter 1
In the following report, the authors will try to give you a brief insight into our team project. The goal of our project was to develop a mechanism for automatic testing of our University Telecommunication network. The Telecommunication network of University of Freiburg consists of: our own internal GSM and telephone network systems; GSM redirecting device (if one initiates a call to one of the four external GSM networks, it redirects the calls to: T-mobile, 02, Vodaphone or E-Plus); a SIP gateway for land-line calls inside of Germany (sipgate.de) and international calls. Since we did not have access to internal servers, our strategy was to exploit the existing systems from an external perspective and infer the results out of our findings.
Before we had started working on our project, we had to analyze the overall network to come up with the test cases that contain the highest information content. The next step in our procedure was to implement our ideas into a working piece of software.
-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 requirements, goals and made a fully 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 to the problem and how each subsystem works.
-This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software. Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
+Gradually we implemented a bit-by-bit of the final software. In the following chapters we will describe in more detail our approach to the problem and how each subsystem works.
+This particular report and our wiki page should be a sufficient guide and manual for understanding, running and continuing the development of our test software.
\clearpage
\section{Requirements} % chapter 2
At the start of the project the requirements were not completely known but as the time had passed we redefined our requirements and goals.
@@ -192,12 +191,11 @@ attributes, both of varchar type, \emph{providerName} and \emph{prefix}.
Software design was the next step after we analyzed the problem and developed a plan how to proceed further. Good analysis and planning with poor algorithmic implementation is valueless.
During the work on the project, we had spent most of our time for software design.
We kept in mind that our software should satisfy major paradigms of software engineering,
-like compatibility, extensibility, maintability, modularity, relliability, security, fault-tolerance and usability.
+like compatibility, extensibility, modularity, relliability, security, fault-tolerance and usability.
The software engineering design concepts were achieved following way:
\begin{itemize}
\item Compatibility - we used Python and MySQL which are multiplatform and work on major OS
\item Extensibility - new parts of code can be easily added by just modifying the classes
-\item Maintability - the test software can recognize new added cell phones to the system and dynamically perform tests if new BTS stations are added
\item Mudalarity - the components are independent black boxes, they are tested and validated independently
\item Reliability - we use mutex locks to perform tests and database transaction operations to insert data into the database
\item Security - all communication channels, as well as the access to the web site, are encrypted with asymmetric key cryptography
@@ -303,10 +301,15 @@ How the class works and what kind of outputs it produces can be found on our pro
\includegraphics[width=60mm]{logging.png}
\caption[]{Logging class}
\end{figure}
-\subsection{SSH Class}
+\subsection{SSH Tunnel Class}
Since security played an important role in our team project. We decided to encrypt all of our data that was not processed on our server computer.
The simplest solution to this problem was to build an SSH Class that could open and close a local forwarding port.
All data sent through the created port is encrypted until it gets to its destination location.
+\begin{figure}[ht!]
+ \centering
+ \includegraphics[width=60mm]{sshTunnelClass.png}
+ \caption[]{SSH Tunnel class}
+\end{figure}
\subsection{USB Cell phone detection class}
Since we had used cables to connect the cell phones with the computer, usually the devices
got their own port addresses. They were automatically assigned by the operating system,
@@ -821,7 +824,9 @@ sudo easy_install setproctitle
\newpage
\section{Conclusion}
-
+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 requirements, goals and made a fully operable test software.
+Despite the fact that we created a fully working and operable software, all the way along we thought about the simplicity of the usage of the software.
+Our team members were enthusiastic about the idea that our team project will contribute to a better perferomance and quality of the telecommunication network for the University staff and all their students.
\newpage
diff --git a/notFinishedCode/Report/test.toc b/notFinishedCode/Report/test.toc
index 2eab00d..32cb4fc 100644
--- a/notFinishedCode/Report/test.toc
+++ b/notFinishedCode/Report/test.toc
@@ -11,8 +11,8 @@
\contentsline {subsection}{\numberline {4.3}Client and Server class}{14}
\contentsline {subsection}{\numberline {4.4}Ping class}{15}
\contentsline {subsection}{\numberline {4.5}Data logging}{16}
-\contentsline {subsection}{\numberline {4.6}SSH Class}{16}
-\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{16}
+\contentsline {subsection}{\numberline {4.6}SSH Tunnel Class}{16}
+\contentsline {subsection}{\numberline {4.7}USB Cell phone detection class}{17}
\contentsline {subsection}{\numberline {4.8}Truth table class}{17}
\contentsline {subsection}{\numberline {4.9}Init Test class}{17}
\contentsline {subsection}{\numberline {4.10}Controller class}{17}