X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=introduction.tex;h=79f6c1d93d9de1a7c2d2d00002aa13c1ddb11f10;hb=a3a00cd9df798eda92291a2f3f6c922bdfdfdac2;hp=c2ee7bc230bae48cc492bedfa88f501a2d892966;hpb=3bc980446b86f187a2af8b4a679f15c58bdca8f2;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index c2ee7bc..79f6c1d 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -3,19 +3,19 @@ The \gls{TOP} paradigm and the according \gls{iTasks} implementation offer a
 high abstraction level for real life workflow tasks. These workflow tasks can be
 described through an \gls{EDSL} and modeled as \glspl{Task}
 From the specification the system will then generate a multi-user web service.
-This web service can be accessed through a browser and used to complete these
+This web service is accessed through a browser and used to complete these
 \glspl{Task}. Familiar workflow patterns like sequence, parallel and
 conditional tasks can be modelled using combinators.
 
 \gls{iTasks} has been shown to be useful in many fields of operation such as
 incident management~\cite{lijnse_top_2013}. Interfaces are automatically
 generated for the types of data which makes rapid development possible.
-However, while the tasks in the \gls{iTasks} system model after real life
-workflow tasks the modelling is very high level. It is difficult to connect
-actual tasks to the real tasks and let them interact. A lot of the actual tasks
-can be \emph{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. 
+\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} tasks to the real world tasks and let them
+interact. A lot of the actual tasks can be \emph{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. 
 
 In the current system such adapters, in principle, can be written as 
 \glspl{SDS}\footnote{Similar as to resources such as time are available in
@@ -24,8 +24,8 @@ adapter to be written for every device and functionality. However, 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~\cite{oortgiese_distributed_2017} that is also
-runnable on smaller devices like \acrshort{ARM} devices. However, this is
+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 only have \gls{LTN}
 communication with low bandwidth and a very limited amount of processing power
@@ -41,11 +41,11 @@ at runtime and information can be exchanged.
 
 \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:introduction} contains the problem statement, motivation,
+literature embedding 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
+is built.
+Chapter~\ref{chp:results} shows the new techniques deviced and an example
 application accompanied with implementation.
 Chapter~\ref{chp:conclusion} concludes by answering the research questions
 and discusses future research.
@@ -53,3 +53,7 @@ Appendix~\ref{app:communication-protocol} shows the concrete protocol used for
 communicating between the server and client.
 Appendix~\ref{app:device-interface} shows the concrete interface for the
 devices.
+
+\section{Relevant research}
+\todo{Hier alle citaten en achtergrond doen}
+Ivory, firmata, dsl spul, etc.