back/summary.tex

   1 \documentclass[../thesis.tex]{subfiles}
   2
   3 \input{subfilepreamble}
   4
   5 \begin{document}
   6 \input{subfileprefixsmall}
   7 \ifSubfilesClassLoaded{\chapter*{Summary}}{\chapter{Summary}}%
   8 \label{chp:summary}%
   9 \glsresetall%
  10 Programming \gls{IOT} systems is complex since they are dynamic, interactive, distributed, collaborative, multi-tiered, and multitasking in nature.
  11 The complexity is increased further by semantic friction that arises through different hardware and software characteristics between tiers.
  12 Many computers that operate in \gls{IOT} systems are \emph{edge devices} that interact with the environment using sensors and actuators.
  13 Edge devices often use low-cost microcontrollers designed for embedded applications.
  14 They have little memory, unhurried processors, and are slow in communication but are also small and energy efficient.
  15 %Hence they require additional care.
  16
  17 \Gls{TOP} can cope with the challenges of \gls{IOT} programming.
  18 In \gls{TOP}, the main building blocks are tasks, an abstract representation of work.
  19 During execution, the current value of the task is observable, and other tasks can act upon it.
  20 Collaboration patterns can be modelled by combining and transforming tasks into compound tasks.
  21 Programming edge devices benefits from \gls{TOP} as well, but running such a system within the limitations of resource-constrained microcontrollers is not straightforward.
  22
  23 This dissertation demonstrates how to include edge devices in \gls{TOP} systems using \glspl{DSL}.
  24 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.
  25 First, I present advanced \gls{DSL} embedding techniques.
  26 Then \gls{MTASK} is shown, a \gls{TOP} \gls{DSL} for \gls{IOT} edge devices, embedded in \gls{ITASK}.
  27 Tasks are constructed and compiled at run time in order to allow tasks to be tailored to the current work requirements.
  28 The task is then sent to the device for interpretation.
  29 A device is programmed once with a lightweight domain-specific \gls{OS} to be used in an \gls{MTASK} system.
  30 This \gls{OS} executes tasks in an energy-efficient way and automates all communications and data sharing.
  31 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.
  32
  33 Finally, tierless \gls{IOT} programming is compared to traditional tiered programming.
  34 In tierless programming frameworks, the size of the code and the number of required programming languages is reduced significantly.
  35 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.
  36 %This is a summary of 350--400 words.
  37 \end{document}