moved intro to abstract, added refs, test listing

[msc-thesis1617.git] / introduction.tex

diff --git a/introduction.tex b/introduction.tex
index cc6b22d..1b184ee 100644 (file)
--- a/introduction.tex
+++ b/introduction.tex
@@ -1,22 +1,35 @@
-The main goal of this thesis is to present a way to connect small \gls{IoT}
-devices with high level \gls{TOP} languages.
-
-\section{\acrlong{IoT}}
-
-
-\section{\acrlong{TOP}}
-
-\todo{Structure of the thesis}
-
-
-\gls{TOP} is a recent new programming paradigm implemented as
-\gls{iTasks}~\cite{achten_introduction_2015} in
-the pure lazy functional language \gls{Clean}
-
-\todo{Main terms}
-The lazy functional programming language based on graph rewriting
-\gls{Clean}~\cite{brus_cleanlanguage_1987}
-
-\todo{What am I doing}
-
-
+\section{Motivation}
+\Gls{TOP} and \gls{iTasks} have been designed to offer a high abstraction level
+through a \gls{DSL} that describes workflows as \glspl{Task}. \gls{iTasks} has
+been shown to be useful in fields such as incident
+management~\cite{lijnse_top_2013}. However, there still lacks support for small
+devices to be added in the workflow. In principle such adapters can be written
+as \glspl{SDS}\footnote{Similar as to resources such as time are available in
+the current system} but this requires a very specific adapter to be written for
+every device and functionality. Oortgiese et al.\ lifted \gls{iTasks} from a
+single server model to a distributed server architecture~\todo{Add cite} that
+is also runnable on smaller devices like \acrshort{ARM}. However, this is
+limited to fairly high performance devices that are equipped with high speed
+communication lines.  Devices in \gls{IoT} often only have LPLB communication
+with low bandwidth and a very limited amount of processing power. \glspl{mTask}
+will bridge this gap.  It can run on devices as small as Arduino
+microcontrollers and operates via the same paradigms as regular \glspl{Task}.
+The \glspl{mTask} have access to \glspl{SDS} and can run small imperative
+programs.
+
+\section{Problem statement}
+
+\section{Document structure}
+The structure of the thesis is as follows.
+Chapter~\ref{chp:introduction} contains the problem statement, motivation and
+the structure of the document
+Chapter~\ref{chp:theoretical-framework} introduces the reader with all the
+terminology and techniques lying at the foundation of the study.
+Chapter~\ref{chp:methods} will describe the actual techniques used for the
+integration.
+Chapter~\ref{chp:results} shows the results in the form of an example
+application accompanied with implementation.
+Chapter~\ref{chp:conclusion} concludes by answering the research question (s)
+and discusses future research.
+Appendix~\ref{app:communication-protocol} shows the concrete protocol used for
+communicating between the server and client.