X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=introduction.tex;h=4352f6e594851f9c8a0eba26ac87083646f20ccc;hb=7910fda15825b983fd6b1309b07872616cc6367b;hp=70a36b340b365f5cf1a52702f7b5783c65355d43;hpb=9c940edab2b3282dc658a629a24573e92964ae77;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index 70a36b3..4352f6e 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -1,2 +1,34 @@
-\todo{What am I doing}
-\todo{Structure of the thesis}
+\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 \gls{iTasks} implementation} 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}
+Therefore the problem statement is as follows:
+
+\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:methods} describes the foundations on which the implementation
+is built together with the new techniques introduced.
+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.