introduction.tex

   1 \section{Motivation}
   2 \Gls{TOP} and \gls{iTasks} have been designed to offer a high abstraction level
   3 through a \gls{DSL} that describes workflows as \glspl{Task}. \gls{iTasks} has
   4 been shown to be useful in fields such as incident
   5 management~\cite{lijnse_top_2013}. However, there still lacks support for small
   6 devices to be added in the workflow. In principle such adapters can be written
   7 as \glspl{SDS}\footnote{Similar as to resources such as time are available in
   8 the current system} but this requires a very specific adapter to be written for
   9 every device and functionality. Oortgiese et al.\ lifted \gls{iTasks} from a
  10 single server model to a distributed server architecture~\todo{Add cite} that
  11 is also runnable on smaller devices like \acrshort{ARM}. However, this is
  12 limited to fairly high performance devices that are equipped with high speed
  13 communication lines.  Devices in \gls{IoT} often only have LPLB communication
  14 with low bandwidth and a very limited amount of processing power. \glspl{mTask}
  15 will bridge this gap.  It can run on devices as small as Arduino
  16 microcontrollers and operates via the same paradigms as regular \glspl{Task}.
  17 The \glspl{mTask} have access to \glspl{SDS} and can run small imperative
  18 programs.
  19
  20 \section{Problem statement}
  21
  22 \section{Document structure}
  23 The structure of the thesis is as follows.
  24 Chapter~\ref{chp:introduction} contains the problem statement, motivation and
  25 the structure of the document
  26 Chapter~\ref{chp:theoretical-framework} introduces the reader with all the
  27 terminology and techniques lying at the foundation of the study.
  28 Chapter~\ref{chp:methods} will describe the actual techniques used for the
  29 integration.
  30 Chapter~\ref{chp:results} shows the results in the form of an example
  31 application accompanied with implementation.
  32 Chapter~\ref{chp:conclusion} concludes by answering the research question (s)
  33 and discusses future research.
  34 Appendix~\ref{app:communication-protocol} shows the concrete protocol used for
  35 communicating between the server and client.