X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=back%2Fsummary.tex;h=41272cbbd2c79bef1708f8e2c11eb8603e8ba72f;hb=a5b8d7509c5846d51e2f9e75d4787c7d9b90b408;hp=1f4a1a30f0ab6cf37d50988710600bf126231679;hpb=066dd25d4da01798ce7a5dd2c96e47040fa908d8;p=phd-thesis.git

diff --git a/back/summary.tex b/back/summary.tex
index 1f4a1a3..41272cb 100644
--- a/back/summary.tex
+++ b/back/summary.tex
@@ -3,24 +3,34 @@
 \input{subfilepreamble}
 
 \begin{document}
-\input{subfileprefix}
-\chapter{Summary}%
-\label{chp:summary}
-%\begin{center}
-\noindent%
-The amount of computers around us is growing exponentially.
-With it, the systems in which they operate are becoming more and more complex.
-Many of these computers are so called \emph{edge devices}.
-For a special class of systems, \glsxtrlong{IOT} systems, they perform the interaction with the world.
-Powered by microcontrollers, these specialised computers have little memory, slow processors, and support slow communication methods.
-On the other hand, they are also cheap, tiny, consume little energy, and can easily equipped with various sensors and actuators.
+\input{subfileprefixsmall}
+\ifSubfilesClassLoaded{\chapter*{Summary}}{\chapter{Summary}}%
+\label{chp:summary}%
+\glsresetall%
+The development of reliable software for the \gls{IOT} is difficult because \gls{IOT} systems are dynamic, interactive, distributed, collaborative, multi-tiered, and multitasking in nature.
+The complexity is increased further by semantic friction that arises through different hardware and software characteristics between tiers.
+Many computers that operate in \gls{IOT} systems are \emph{edge devices} that interact with the environment using sensors and actuators.
+Edge devices are often powered by low-cost microcontrollers designed for embedded applications.
+They have little memory, unhurried processors, and are slow in communication but are also small and energy efficient.
 
-There is a great variety within edge devices but also between edge devices and more conventional computers.
-However, they do have to communicate with the conventional computers.
-This results in semantic friction, an impedance mismatch.
-Developing and maintaining such systems is expensive and error prone.
+\Gls{TOP} can cope with the challenges of \gls{IOT} programming.
+In \gls{TOP}, the main building blocks are tasks, an abstract representation of work.
+During execution, the current value of the task is observable, and other tasks can act upon it.
+Collaboration patterns can be modelled by combining and transforming tasks into compound tasks.
+Programming edge devices benefits from \gls{TOP} as well, but running such a system within the limitations of resource-constrained microcontrollers is not straightforward.
 
-This is a summary of 350--400 words.
-%\end{center}
-\input{subfilepostamble}
+This dissertation demonstrates how to include edge devices in \gls{TOP} systems using \glspl{DSL}.
+With these techniques, all tiers and their interoperation of an \gls{IOT} system is specified in a single high-level source, language, paradigm, high abstraction level, and type system.
+First, I present advanced \gls{DSL} embedding techniques.
+Then \gls{MTASK} is shown, a \gls{TOP} \gls{DSL} for \gls{IOT} edge devices, embedded in \gls{ITASK}.
+Tasks are constructed and compiled at run time in order to allow tasks to be tailored to the current work requirements.
+The task is then sent to the device for interpretation.
+A device is programmed once with a lightweight domain-specific \gls{OS} to be used in an \gls{MTASK} system.
+This \gls{OS} executes tasks in an energy-efficient way and automates all communications and data sharing.
+All aspects of the \gls{MTASK} system are shown: example applications, language design, implementation details, integration with \gls{ITASK}, and green computing facilities such as automatic sleeping.
+
+Finally, tierless \gls{IOT} programming is compared to traditional tiered programming.
+In tierless programming frameworks, the size of the code and the number of required programming languages is reduced significantly.
+By using a single paradigm and a system-wide type system, tierless programming reduces problems such semantic friction; maintainability and robustness issues; and interoperation safety.
+%This is a summary of 350--400 words.
 \end{document}