-\section{Motivation}
+\section{Introduction}
\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
+through a \gls{EDSL} 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
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:
+often only have \gls{LTN} 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{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
+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
repositories / msc-thesis1617.git / blobdiff