overviews updated

[msc-thesis1617.git] / arch.tex

diff --git a/arch.tex b/arch.tex
index 3d8a7a8..c5e46ee 100644 (file)
--- a/arch.tex
+++ b/arch.tex
@@ -1,16 +1,16 @@
-The system provides a framework of functions with
-which an \gls{iTasks}-system can add, change and remove devices at runtime.
-Moreover, the \gls{iTasks}-system can send \gls{mTask}-\glspl{Task} ---
-compiled at runtime to bytecode by the \gls{mTask}-view --- to the device. The
-device runs an interpreter which executes the \gls{Task}'s bytecode following
-the scheduling strategy given. Devices added to the system are stored and get a
-profile for identification. These profiles are persistent during reboots of
-the \gls{iTasks}-system to allow for easy reconnecting with old devices. The
-methods of interacting with \gls{mTask}-\gls{Task} is analogous to interacting
+The system provides a framework of functions with which an \gls{iTasks}-system
+can add, change and remove devices at runtime.  Moreover, the
+\gls{iTasks}-system can send \gls{mTask}-\glspl{Task} --- compiled at runtime
+to bytecode by the \gls{mTask}-view --- to the device. The device runs an
+interpreter which executes the \gls{Task}'s bytecode following the provided
+scheduling strategy. Devices added to the system are stored and get a profile
+for identification. These profiles are persistent during reboots of the
+\gls{iTasks}-system to allow for easy reconnecting with old devices. The
+way of interacting with \gls{mTask}-\gls{Task} is analogous to interacting
 with \gls{iTasks}-\glspl{Task}. This means that programmers can access the
 \glspl{SDS} made for a device in the same way as regular \glspl{SDS} and they
-can execute \gls{mTask}-\glspl{Task} as if they where normal
-\gls{iTasks}-\glspl{Task}.
+can execute, combine and transform \gls{mTask}-\glspl{Task} as if they where
+normal \gls{iTasks}-\glspl{Task}.
 
 \section{Devices}
 \input{arch.devices}