\input{subfilepreamble}
\begin{document}
-\chapter{Introduction}%
+\chapter{Prelude --- Introduction}%
\label{chp:introduction}
-
\begin{chapterabstract}
- The sheer number of connected devices around us is mind boggling and seems increases exponentially for many years.
- In 2022, there is an estimated number of 13.4 billion of devices connected that sense, act or otherwise interact with people and the physical world surrounding us\footnote{\url{https://transformainsights.com/research/tam/market}, accessed on: \formatdate{2022}{10}{13}}.
- These devices, together with all the scaffolding and integration such as the various networks providing the communication, (cloud) computers realising the back end or administration and the devices in our pockets providing us with a view on the system are called the \gls{IOT}.
- \Gls{IOT} systems can be seen as layered systems, where each layer is powered by different types of computers; programming languages and even programming paradigms.
- This thesis shows a novel way of orchestrating these brobdingnagian systems using the \gls{TOP} paradigm.
- It does so by giving a proof-of-concept implementation for a \gls{TOP} system specifically designed for the \gls{IOT}: \gls{MTASK}.
- At the core of the \gls{MTASK} system is a \gls{DSL}, embedded in the general purpose \gls{TOP} system \gls{ITASK}.
- Using the \gls{MTASK} system, all layers of an \gls{IOT} system can be programmed from a single declarative specification.
+ \noindent%
+ \begin{itemize}
+ \item How many devices are there?
+ \begin{itemize}
+ \item Number of devices is big\footnote{\url{https://transformainsights.com/research/tam/market}, accessed on: \formatdate{2022}{10}{13}}
+ \item It only grows
+ \item they are powered by software
+ \item These devices live in layered systems
+ \end{itemize}
+ \item What is the {IoT}?
+ \begin{itemize}
+ \item IoT is such a layered system
+ \item Layers, device layer
+ \end{itemize}
+ \item What is impedance mismatch/semantic friction?
+ \begin{itemize}
+ \item heterogeneous between layers
+ \item heterogeneous on the device/edge/perception layer
+ \item Results in problems in software
+ \item We see this also in web systems
+ \end{itemize}
+ \item What is TOP?\todo{hier al TOP uitleggen in \`e\`en zin? of alleen benoemen}
+ \begin{itemize}
+ \item declarative workflow language (partiture AND conductor)
+ \item iTask for distributed web applications.
+ \end{itemize}
+ \item This thesis: how to orchestrate this concerto of devices?
+ \begin{itemize}
+ \item Embedded devices require special code (different clef/key)
+ \item DSL is a special language in a language to facilitate this (part 1)
+ \item mTask is a TOP language for IoT (part 2)
+ \item This approach is called tierless programming (part 3)
+ \end{itemize}
+ \end{itemize}
This chapter provides the required background material, an overview of the concrete contributions and a reading guide.
+
+% The sheer number of connected devices around us is mind boggling and seems increases exponentially for many years.
+% In 2022, there is an estimated number of 13.4 billion of devices connected that sense, act or otherwise interact with people and the physical world surrounding us\footnote{\url{https://transformainsights.com/research/tam/market}, accessed on: \formatdate{2022}{10}{13}}.
+% These devices, together with all the scaffolding and integration such as the various networks providing the communication, (cloud) computers realising the back end or administration and the devices in our pockets providing us with a view on the system are called the \gls{IOT}.
+% \Gls{IOT} systems can be seen as layered systems, where each layer is powered by different types of computers; programming languages and even programming paradigms.
+% This thesis shows a novel way of orchestrating these brobdingnagian systems using the \gls{TOP} paradigm.
+% It does so by giving a proof-of-concept implementation for a \gls{TOP} system specifically designed for the \gls{IOT}: \gls{MTASK}.
+% At the core of the \gls{MTASK} system is a \gls{DSL}, embedded in the general purpose \gls{TOP} system \gls{ITASK}.
+% Using the \gls{MTASK} system, all layers of an \gls{IOT} system can be programmed from a single declarative specification.
+
\end{chapterabstract}
-\todo{Introduction in the abstract doen zoals nu?}
\section{Internet of Things}
The \gls{IOT} is growing rapidly and it is changing the way people and machines interact with the world.
While the term \gls{IOT} briefly gained interest around 1999 to describe the communication of \gls{RFID} devices~\citep{ashton_internet_1999,ashton_that_2009}, it probably already popped up halfway the eigthies in a speech by \citet{peter_t_lewis_speech_1985}:
\begin{quote}
- \emph{The \acrlong{IOT}, or \acrshort{IOT}, is the integration of people, processes and technology with connectable devices and sensors to enable remote monitoring, status, manipulation and evaluation of trends of such devices.}
+ \emph{The \glsxtrlong{IOT}, or \glsxtrshort{IOT}, is the integration of people, processes and technology with connectable devices and sensors to enable remote monitoring, status, manipulation and evaluation of trends of such devices.}
\end{quote}
CISCO states that the \gls{IOT} only started when there where as many connected devices as there were people on the globe, i.e.\ around 2008~\citep{evans_internet_2011}.
With interpretation, a specialized interpreter is flashed in the program memory once that receives the program code to execute at runtime.
%weiser_computer_1991
-\section{\texorpdfstring{\Acrlongpl{DSL}}{Domain-specific languages}}
+\section{\texorpdfstring{\Glsxtrlongpl{DSL}}{Domain-specific languages}}
% General
Programming languages can be divided up into two categories: \glspl{DSL}\footnote{Historically this has been called DSEL as well.} and \glspl{GPL}~\citep{fowler_domain_2010}.
Where \glspl{GPL} are not made with a demarcated area in mind, \glspl{DSL} are tailor-made for a specific domain.
\end{itemize}
\subsection*{\nameref{prt:tvt}}
-This chapter is based on the journal paper: \citeentry{lubbers_could_2022}\footnote{This work is an extension of the conference article: \citeentry{lubbers_tiered_2020}\footnotemark{}}.
+This chapter is based on the journal paper: \citeentry{lubbers_could_2022}\todo{change when published}\footnote{This work is an extension of the conference article: \citeentry{lubbers_tiered_2020}\footnotemark{}}.
\footnotetext{This paper was partly funded by the Radboud-Glasgow Collaboration Fund.}
It compares programming traditional tiered architectures to tierless architectures by showing a qualitative and a quantitative four-way comparison of a smart campus application.
Writing the paper was performed by all authors.
-I created the server application, the \gls{CLEAN}/\gls{ITASK}/\gls{MTASK} implementation (\acrshort{CWS}) and the \gls{CLEAN}/\gls{ITASK} implementation (\acrshort{CRS})
-Adrian Ramsingh created the \gls{MICROPYTHON} implementation (\acrshort{PWS}), the original \gls{PYTHON} implementation (\acrshort{PRS}) and the server application were created by Jeremy Singer, Dejice Jacob and Kristian Hentschel~\citep{hentschel_supersensors:_2016}.
+I created the server application, the \gls{CLEAN}/\gls{ITASK}/\gls{MTASK} implementation (\glsxtrshort{CWS}) and the \gls{CLEAN}/\gls{ITASK} implementation (\glsxtrshort{CRS})
+Adrian Ramsingh created the \gls{MICROPYTHON} implementation (\glsxtrshort{PWS}), the original \gls{PYTHON} implementation (\glsxtrshort{PRS}) and the server application were created by Jeremy Singer, Dejice Jacob and Kristian Hentschel~\citep{hentschel_supersensors:_2016}.
\input{subfilepostamble}
\end{document}
repositories / phd-thesis.git / blobdiff