\ifSubfilesClassLoaded{\chapter*{Summary}}{\chapter{Summary}}%
\label{chp:summary}%
\glsresetall%
-\todo[inline]{
-eigenlijk zouden de eerste zinnen van de alinea's in je samenvatting zouden de samenvatting van je samenvatting moeten zijn.
-}
-
-The number of computers around us is growing exponentially, compounding the complexity of the systems in which they operate.
-Many of these computers are \emph{edge devices} operating in \gls{IOT} systems.
-Within these orchestrations of computers, they interact with the environment using sensors and actuators.
-Edge devices often use 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.
-Programming \gls{IOT} systems is complex since they are dynamic, interactive, distributed, collaborative, multi-tiered, and multitasking in nature.\todo[inline]{Dit eerste zin maken?}
+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.
-A solution is found in \gls{TOP}.
-\todo[inline]{Dit is nog niet erg specifiek voor dit werk. De eerste zin is prima. Verder zijn er volgens mij twee dingen van belang: high level focus op de taken die gedaan moeten woredn en alle code uit een source genereren (tierless).}
-%A solution is found in the declarative programming paradigm \gls{TOP}.%, a declarative programming paradigm.
+\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.
-From this declarative description of the work, a ready-for-work computer system is generated that guides all operators in doing the work.
-An example of a \gls{TOP} system is \gls{ITASK}, a language which describes interactive web applications.
-Programming edge devices benefits from \gls{TOP} as well.
-However, it is not straightforward to run \gls{TOP} systems on resource-constrained edge devices.
+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 dissertation demonstrates how to orchestrate complete \gls{IOT} systems using \gls{TOP}.
-\todo[inline]{Eerste zin moet al het woord DSL bevatten}
+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 are 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.
-This allows tasks to be tailor-made for the current work requirements.
-The compiled task is sent to the device for interpretation.
-For a device to be used in an \gls{MTASK} system, it is programmed once with a lightweight domain-specific \gls{OS}.
-\todo[inline]{Waar, maar erg op de tecniek. Wat je er aan hebt lijkt me belangrijker.}
+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.
-When using \gls{MTASK} in conjunction with \gls{ITASK}, entire \gls{IOT} systems are programmed tierlessly from a single source, language, paradigm, high abstraction level, and type system.
-Many problems such as semantic friction; maintainability and robustness issues; and interoperation safety are mitigated when using tierless programming.
-\todo[inline]{episode III mist eigenlijk nog.\ vergelijking met de traditionele IoT implementatie heeft laten zien dat dit inderdaad veel korter en veiliger is.}
+
+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 as semantic friction; maintainability and robustness issues; and interoperation safety.
%This is a summary of 350--400 words.
\end{document}
repositories / phd-thesis.git / blobdiff