X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=introduction.tex;h=1c728585ce97dd7fcf005bb76b1e5ce30b8413b0;hb=fcef9f5c5b6021ac424b19c44b4bda608eceaf40;hp=8d5de43aa9d43a9a7abbca85f226c5577b0aa32e;hpb=66de2590bcb4046b92ea54bcd3e55b38208be17b;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index 8d5de43..1c72858 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -71,12 +71,11 @@ Chapter~\ref{chp:dsl} discusses the pros and cons of different embedding
 methods to create \gls{EDSL}.
 Chapter~\ref{chp:mtask} shows the existing \gls{mTask}-\gls{EDSL} on which is
 extended upon in this dissertation.
-Chapter~\ref{chp:arch} shows the architecture used for \gls{IoT}-devices that
-are a part of the new \gls{mTask}-system.
 Chapter~\ref{chp:mtaskcont} shows the extension added to the
 \gls{mTask}-\gls{EDSL} that were needed to make the system function.
-Chapter~\ref{chp:itasksint} shows the integration with \gls{iTasks} that was
-built to realise the system.
+Chapter~\ref{chp:arch} shows the architecture used for \gls{IoT}-devices that
+are a part of the new \gls{mTask}-system. It covers the client software running
+on the device and the server written in \gls{iTasks}.
 Chapter~\ref{chp:conclusion} concludes by answering the research questions
 and discusses future research.
 Appendix~\ref{app:communication-protocol} shows the concrete protocol used for
@@ -88,17 +87,25 @@ Text written using the \CI{Teletype} font indicates code and is often
 referring to a listing. \emph{Emphasized} text is used for proper nouns and
 words that have a unexpected meaning.
 
+The complete source code of this thesis can be found in the following git
+repository:\\
+\url{https://git.martlubbers.net/msc-thesis1617.git}
+
+The complete source code of the \gls{mTask}-system can be found in the
+following git repository:
+\url{https://git.martlubbers.net/mTask.git}
+
 \section{Related work}
-Several types of similar research have been conducted concerning these matters.
-Microcontrollers such as the \gls{Arduino} can be remotely controlled by the
-\gls{Firmata}-protocol\footnote{``firmata/protocol: Documentation of the
-Firmata protocol.'' (\url{https://github.com/firmata/protocol}). [Accessed:
-23-May-2017].}. This protocol
-is designed to expose the peripherals such as sensors to the server. This
-allows very fine grained control but with the cost of excessive communication
-overhead since no code is executed on the device, only the peripherals are
-queried. A \gls{Haskell} implementation of the protocol has been created%
-\footnote{``hArduino by LeventErkok.'' (\url{%
+Similar research has been conducted concerning these matters.
+For example, microcontrollers such as the \gls{Arduino} can be remotely
+controlled by the \gls{Firmata}-protocol\footnote{``firmata/protocol:
+Documentation of the Firmata protocol.''
+(\url{https://github.com/firmata/protocol}). [Accessed: 23-May-2017].}. This
+protocol is designed to expose the peripherals such as sensors to the server.
+This allows very fine grained control but with the cost of excessive
+communication overhead since no code is executed on the device, only the
+peripherals are queried. A \gls{Haskell} implementation of the protocol is
+also available\footnote{``hArduino by LeventErkok.'' (\url{%
 https://leventerkok.github.io/hArduino}). [Accessed: 23-May-2017].}.
 
 \Gls{Clean} has a history of interpretation and there is a lot of research
@@ -107,8 +114,8 @@ functional intermediate language that has interpreters written in
 \gls{C++}~\cite{jansen_efficient_2007} and \gls{Javascript}%
 ~\cite{domoszlai_implementing_2011} and \gls{Clean} and \gls{Haskell} compiler
 backends~\cite{domoszlai_compiling_2012}. However, interpreting the resulting
-code is still heap-heavy and therefore not directly suitable for devices with as
-little as $2K$ of RAM such as the \gls{Arduino} \emph{UNO}. It might be
+code is still heap-heavy and therefore not directly suitable for devices with
+as little as $2K$ of RAM such as the \gls{Arduino} \emph{UNO}. It might be
 possible to compile the \gls{SAPL} code into efficient machine language or
 \gls{C} but then the system would lose its dynamic properties since the
 microcontroller then would have to be reprogrammed every time a new \gls{Task}