X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;ds=sidebyside;f=introduction.tex;h=775a7b5b4b37bf3070bf12e38f99498f4d3a8fb4;hb=c7fa2f10a5c049e2ae70405630857c7873778899;hp=7ea1d08763e1deb184b60870ab31dd3ebc1c9736;hpb=435b0d98d22a47530f50ff82f2451e70ce2bed96;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index 7ea1d08..775a7b5 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -9,7 +9,7 @@ are often equipped with sensors, \gls{GNSS}\footnote{e.g.\ the American
 \gls{GPS} or the Russian \gls{GLONASS}} and actuators%
 \cite{da_xu_internet_2014}. With these new technologies information
 can be tracked very accurately using very little power and bandwidth. Moreover,
-\gls{IoT} technology is coming into people's homes, clothes and in
+\gls{IoT} technology is coming into people's homes, clothes and
 healthcare\cite{riazul_islam_internet_2015}. For example, for a few euros a
 consumer ready fitness tracker watch can be bought that tracks heartbeat and
 respiration levels.
@@ -28,8 +28,8 @@ incident management~\cite{lijnse_top_2013}. Interfaces are automatically
 generated for the types of data which makes rapid development possible.
 \Glspl{Task} in the \gls{iTasks} system are modelled after real life workflow
 tasks but the modelling is applied on a very high level. Therefore it is
-difficult to connect \gls{iTasks}-\glspl{Task} to real world tasks and let
-them interact. A lot of the actual tasks could be performed by small
+difficult to connect \gls{iTasks}-\glspl{Task} to real world \glspl{Task} and
+allow them to interact. A lot of the actual tasks could be performed by small
 \gls{IoT} devices. Nevertheless, adding such devices to the current system is
 difficult to say the least as it was not designed to cope with these devices. 
 
@@ -38,16 +38,16 @@ principle --- can be written as \glspl{SDS}\footnote{Similar as to resources
 such as time are available in the current \gls{iTasks} implementation}.
 However, this
 requires a very specific adapter to be written for every device and function.
-This forces a fixed logic in the device that is set at compile time. A
-lot of the small \gls{IoT} devices have limited processing power but can still
-contain decision making. Oortgiese et al.\ lifted \gls{iTasks} from a single
-server model to a distributed server architecture that is also runnable on
-smaller devices like \acrshort{ARM} devices\cite{oortgiese_distributed_2017}.
-However, this is limited to fairly high performance devices that are equipped
-with high speed communication channels. Devices in \gls{IoT} often have only
-\gls{LTN} communication with low bandwidth and a very limited amount of
-processing power and are therefore not suitable to run an entire \gls{iTasks}
-core.
+This forces a fixed logic in the device that is set at compile time. Many
+small \gls{IoT} devices have limited processing power but can still contain
+decision making. Oortgiese et al.\ lifted \gls{iTasks} from a single server
+model to a distributed server architecture that is also runnable on small
+devices such as those powered by \acrshort{ARM}~\cite{%
+oortgiese_distributed_2017}. However, this is limited to fairly high
+performance devices that are equipped with high speed communication channels.
+Devices in \gls{IoT} often have only \gls{LTN} communication with low bandwidth
+and a very limited amount of processing power and are therefore not suitable to
+run an entire \gls{iTasks} core.
 
 \section{Problem statement}
 The updates to the \gls{mTask}-system\cite{koopman_type-safe_nodate} will
@@ -70,14 +70,13 @@ Chapter~\ref{chp:top} introduces the reader to the basics of \gls{TOP} and
 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 on in this dissertation.
+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.
-
-\todo{Vul aan}
-
+Chapter~\ref{chp:itasksint} shows the integration with \gls{iTasks} that was
+built to realise the system.
 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