\documentclass[../thesis.tex]{subfiles}
+\input{subfilepreamble}
+
\begin{document}
-\ifSubfilesClassLoaded{
- \pagenumbering{arabic}
-}{}
\chapter{Introduction}%
\label{chp:introduction}
-%\setlength{\epigraphwidth}{.5\textwidth}%
-%\epigraphhead[30]{
-% A \textbf{rhapsody} in music is a one-movement work that is episodic yet integrated, free-flowing in structure, featuring a range of highly contrasted moods, colour, and tonality. An air of spontaneous inspiration and a sense of improvisation make it freer in form than a set of variations.
-%}{%
-% Wikipedia~\citep{wikipedia_contributors_rhapsody_2022}
-%}%
-The sheer number of connected devices around us is increasing exponentially.
-All these devices are equipped with processors, sensors, actuators, communication interfaces and much more.
-They
-The one thing they all have in common
-All these connected devices are driven by software and communicate with eachother, sense and interact with the world.
-This thesis is about \ldots
-\todo[inline]{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 the world\footnote{\url{https://transformainsights.com/research/tam/market}, accessed on: \formatdate{2022}{10}{13}}.
+ These devices, together with the networks that provide the communication, the servers realising the back end and the devices in our pockets are called the \gls{IOT}.
+ \Gls{IOT} systems can be seen as layered systems, where each layer is powered by different types of computers; and programming languages and paradigms.
+ Thes 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.
+
+ This chapter provides the required background material, detail regarding the contributions and a reading guide.
+\end{chapterabstract}
+\todo{Introduction in the abstract doen zoals nu?}
\section{Internet of Things}
-\todo[inline]{add more citations and rewrite to make modern}
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}:
Today, the \gls{IOT} is the term for a system of devices that sense the environment, act upon it and communicate with each other and the world.
These connected devices are already in everyone's household in the form of smart electricity meters, smart fridges, smartphones, smart watches, home automation, \etc.
-When describing \gls{IOT} systems, a layered, or tiered architecture is often used to compartmentalize the technology.
-The number of tiers heavily depends on the complexity of the model but for the intents and purposes of the thesis, the four layer architecture shown in \cref{fig:iot-layers} is used.
+When describing \gls{IOT} systems layered---or tiered---architecture is often used to compartmentalize the technology.
+The number of tiers heavily depends on the required complexity of the model but for the intents and purposes of the thesis, the four layer architecture shown in \cref{fig:iot-layers} is used.
\begin{figure}[ht]
\centering
\includestandalone{iot-layers}
- \caption{The four layered \gls{IOT} architecture.}%
+ \caption{A four-layer \gls{IOT} architecture.}%
\label{fig:iot-layers}
\end{figure}
-\begin{description}
- \item[Presentation layer] This presentation layer provides the interface between the user and the \gls{IOT} application.
- For example, in home automation, this is often implemented as a web interface or a mobile app.
- \item[Application layer]
- Servers often power the application layer, by providing the data storage,
- One of its goals is to provide the \gls{API}, interfaces and data storage
- \item[Network layer] connects all layers together.
- In many applications this may be implemented using conventional networking techniques such as WiFi or wire networks.
- However, recently, networks tailored to the needs of \gls{IOT} applications have been increasingly popular such as \gls{BLE}, LoRa, ZigBee or LTE-M.
- \item[Perception layer], also called edge layer, collects the data, interacts with the environment and consists of (edge) devices equipped with various sensors and actuators.
- As a special type of device, it may also contain a \gls{SN}.
- A \gls{SN} is a collection of sensors connected by a mesh network or central hub.
-\end{description}
+The presentation layer provides the interface between the user and the \gls{IOT} application.
+For example, in home automation, this is a web interface or a mobile app used on the phone or a mounted tablet to interact with the edge devices.
+
+The application layer provides the \glspl{API}, interfaces and data storage.
+In home automation, this would be the cloud service or local server.
-The devices are a large heterogeneous collection of different platforms, protocols and languages resulting in impedance problems or semantic friction between layers~\citep{ireland_classification_2009}.
-Furthermore, the perception layer often is a heterogeneous collections of microcontrollers as well, each having their own peculiarities, language of choice and hardware interfaces.
-The hardware needs to be cheap, small-scale and energy efficient.
-As a result, the \glspl{MCU} used to power these devices do not have a lot of computational power, a soup\c{c}on of memory, and little communication bandwidth.
+All layers are connected using the network layer.
+In many applications this is implemented using conventional networking techniques such as WiFi or wired networks.
+However, networks and layers on top of itt tailored to the needs of \gls{IOT} applications have been increasingly popular such as \gls{BLE}, LoRa, ZigBee, LTE-M, or \gls{MQTT}.
+
+The perception layer---also called edge layer---collects the data, interacts with the environment, and consists of (edge) devices equipped with various sensors and actuators.
+%As a special type of device, it may also contain a \gls{SN}.
+%A \gls{SN} is a collection of sensors connected by a mesh network or central hub.
+In home automation this layer consists of all the microprocessors in the sensors, for example in the smart lightbulbs, actuators to open doors and sensors.
+
+Spanning all layers, the devices are a large heterogeneous collection of different platforms, protocols, paradigms and programming languages resulting in impedance problems or semantic friction between layers~\citep{ireland_classification_2009}.
+Furthermore, specifically the perception layer often is a heterogeneous collections of microprocessors in itself as well, each having their own peculiarities, language of choice and hardware interfaces.
+As the hardware needs to be cheap, small-scale, and energy efficient, the \glspl{MCU} used to power these devices do not have a lot of computational power, only a soup\c{c}on of memory, and little communication bandwidth.
Typically the devices do not run a full fledged \gls{OS} but a compiled firmware.
This firmware is often written in an imperative language that needs to be flashed to the program memory.
Program memory typically is flash based and only lasts a couple of thousand writes before it wears out.
-While devices are getting a bit faster, smaller, and cheaper, they keep these properties to an extent.
-The properties of the device greatly reduce the flexibility for dynamic systems where tasks are created on the fly, executed on demand and require parallel execution.
-\todo{\gls{OTA} benoemen?}
+While devices are getting a bit faster, smaller, and cheaper, they keep these properties to an extent, greatly reducing the flexibility for dynamic systems where tasks are created on the fly, executed on demand, or require parallel execution.
These problems can be mitigated by dynamically sending code to be interpreted to the \gls{MCU}.
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{Domain-specific languages}
+\section{\texorpdfstring{\Acrlongpl{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.
Unfortunately it also means that they need to develop a compiler or interpreter for the language to be usable making standalone \glspl{DSL} costly to create.
Examples of standalone \glspl{DSL} are regular expressions, make, yacc, XML, SQL, \etc.
-A dichotomous approach is embeddding the \gls{DSL} in a host language, i.e.\ \glspl{EDSL}~\citep{hudak_modular_1998}.
+A dichotomous approach is embedding the \gls{DSL} in a host language, i.e.\ \glspl{EDSL}~\citep{hudak_modular_1998}.
By defining the language as constructs in the host language, much of the machinery is inherited and the cost of creating embedded languages is very low.
There is more linguistic reuse~\cite{krishnamurthi_linguistic_2001}.
There are however two sides to the this coin.
Furthermore, errors shown to the programmer may be larded with host language errors, making it difficult for a non-expert of the host language to work with the \gls{DSL}.
\subsection{Heterogeneity and homogeneity}
-Tratt applied a notion from metaprogramming~\citep{sheard_accomplishments_2001} to \glspl{EDSL} to define homogeneity and heterogeneity of \glspl{EDSL} as follows~\citep{tratt_domain_2008}:
+\Citet{tratt_domain_2008} applied a notion from metaprogramming~\citep{sheard_accomplishments_2001} to \glspl{EDSL} to define homogeneity and heterogeneity of \glspl{EDSL} as follows:
+
\begin{quote}
- \emph{a homogeneous system is one where all the components are specifically designed to work with each other, whereas in heterogeneous systems at least one of the components is largely, or completely, ignorant of the existence of the other parts of the system.}
+ A homogeneous system is one where all the components are specifically designed to work with each other, whereas in heterogeneous systems at least one of the components is largely, or completely, ignorant of the existence of the other parts of the system.
\end{quote}
+
Homogeneous \glspl{EDSL} are therefore languages that are solely defined as an extension to their host language.
They often restrict features of the host language to provide a safer interface or capture an idiomatic pattern in the host language for reuse.
The difference between a library and a homogeneous \glspl{EDSL} is not always clear.
Examples of homogeneous \glspl{EDSL} are libraries such as ones for sets, \glspl{GUI} creation, LISP's macro system, \etc.
On the other hand, heterogeneous \glspl{EDSL} are languages that are not executed in the host language.
-For example, Elliott et al.\ describe the language Pan, for which the final representation in the host language is a compiler that will, when executed, generate code for a completely different target platform~\citep{elliott_compiling_2003}.
-In fact, \gls{ITASK} and \gls{MTASK} are both heterogeneous \glspl{EDSL}\todo{reference next section?}.
+For example, \citep{elliott_compiling_2003} describe the language Pan, for which the final representation in the host language is a compiler that will, when executed, generate code for a completely different target platform.
+In fact, \gls{ITASK} and \gls{MTASK} are both heterogeneous \glspl{EDSL} and \gls{MTASK} specifically is a compiling \gls{DSL}.
\section{Task-oriented programming}
\Gls{TOP} is a declarative programming paradigm designed to model interactive systems~\citep{plasmeijer_task-oriented_2012}.
\end{figure}
\begin{description}
- \item[Presentation layer: \gls{UI}]
+ \item[Presentation layer (\gls{UI})]
The \gls{UI} of the system is automatically generated from the representation of the type.
% For instance, \gls{TOP} languages implemented in an \gls{FP} language often use generic programming or template metaprogramming to automatically achieve this.
% \Gls{TOP} languages embedded in imperative programming languages may use introspection\todo{Do I want this sentence here?}.
Even though the \gls{UI} is generated from the structure of the datatypes, in practical \gls{TOP} systems it can be tweaked afterwards to suit the specific needs of the application.
- \item[Business layer: tasks]
+ \item[Business layer (tasks):]
A task is an abstract representation of a piece of work that needs to be done.
It provides an intuitive abstraction over work in the real world.
Just as with real-life tasks and workflow, tasks can be combined in various ways such as in parallel or in sequence.
Furthermore, a task is observable which means it is possible to observe a---partial---result during execution and act upon it by for example starting new tasks.
Examples of tasks are filling in a form, sending an email, reading a sensor or even doing a physical task.
- \item[Resource access: \glspl{SDS}]
+ \item[Resource access (\glspl{SDS}):]
Tasks can communicate using task values but this imposes a problem in many collaboration patterns where tasks that are not necessarily related need to share data.
Tasks can also share data using \glspl{SDS}, an abstraction over any data.
An \gls{SDS} can represent typed data stored in a file, a chunk of memory, a database \etc.
\Glspl{SDS} can also represent external impure data such as the time, random numbers or sensory data.
Similar to tasks, transformation and combination of \glspl{SDS} is possible.
- \item[\Gls{UOD}: programming language]
+ \item[\Gls{UOD} (programming language):]
The \gls{UOD} from the business layer is explicitly and separately modelled by the relations that exist in the functions of the host language.
\end{description}
\todo[inline]{uitbreiden}
On Wikipedia, a rhapsody is defined as follows~\citep{wikipedia_contributors_rhapsody_2022}:
\begin{quote}
- \emph{A \textbf{rhapsody} in music is a one-movement work that is episodic yet integrated, free-flowing in structure, featuring a range of highly contrasted moods, colour, and tonality. An air of spontaneous inspiration and a sense of improvisation make it freer in form than a set of variations.}
+ A \textbf{rhapsody} in music is a one-movement work that is episodic yet integrated, free-flowing in structure, featuring a range of highly contrasted moods, colour, and tonality. An air of spontaneous inspiration and a sense of improvisation make it freer in form than a set of variations.
\end{quote}
-
This thesis follows the tradition and consists of three movements that are episodic yet integrated, a purely functional rhapsody.
\Cref{prt:dsl} is about \gls{EDSL} techniques, \cref{prt:top} elaborates on \gls{TOP} for the \gls{IOT} and \cref{prt:tvt} compares traditional tiered \gls{IOT} architectures to a tierless architectures such as \gls{TOP}.
The movements are readable independently if the reader is familiarised with the background material provided in \cref{chp:introduction}.
The thesis wraps up with \cref{chp:conclusion} that provides a conclusion and an outlook on future work.
\subsection*{\nameref{prt:dsl}}
-This movement is a cumulative---paper-based---movement that focusses on techniques for embedding \glspl{DSL} in \gls{FP} lanugages.
-After reading the first chapter, subsequent chapters in this movement are readable as independently.
+This movement is a cumulative---paper-based---movement that focusses on techniques for embedding \glspl{DSL} in \gls{FP} languages.
+After reading the first chapter, subsequent chapters in this movement are readable independently.
\subsubsection*{\fullref{chp:dsl_embedding_techniques}}
This chapter shows the basic \gls{DSL} embedding techniques and compares the properties of several embedding methods.
This chapter is not based on a paper and written as a extra background material for the subsequent chapters in the movement.
-\subsubsection*{\fullref{chp:classy_deep_embedding}}
-This chapter is based on the paper: \emph{Deep Embedding with Class}~\todo{cite when published}.
+\subsubsection*{\fullref{chp:classy_deep_embedding}}
+This chapter is based on the paper: \bibentry{lubbers_deep_2022}\todo{change in-press when published}.
-During a Master's thesis supervision~\citep{amazonas_cabral_de_andrade_developing_2018}, focussing on an early version of \gls{MTASK}, a seed was planted for a novel deep embedding technique for \glspl{DSL} where the resulting language is extendible both in constructs and in interpretation using type classes and existential data types.
+While supervising \citeauthor{amazonas_cabral_de_andrade_developing_2018}'s \citeyear{amazonas_cabral_de_andrade_developing_2018} Master's thesis, focussing on an early version of \gls{MTASK}, a seed was planted for a novel deep embedding technique for \glspl{DSL} where the resulting language is extendible both in constructs and in interpretation using type classes and existential data types.
Slowly the ideas organically grew to form the technique shown in the paper.
The research from this paper and writing the paper was solely performed by me.
\Cref{sec:classy_reprise} was added after publication and contains a (yet) unpublished extension of the embedding technique.
\subsubsection*{\fullref{chp:first-class_datatypes}}
-This chapter is based on the paper: \emph{First-Class Data Types in Shallow Embedded Domain-Specific Languages using Metaprogramming}~\todo{cite when accepted}.
-It shows how to inherit data types in \glspl{EDSL} using metaprogramming.
+This chapter is based on the paper: \bibentry{lubbers_first-class_2022}\todo{change when accepted}.
+
+It shows how to inherit data types from the host language in \glspl{EDSL} using metaprogramming.
The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer in which we discussed and refined the ideas.
\subsection*{\nameref{prt:top}}
-This part is a monograph focussing on \glspl{TOP} for the \gls{IOT}.
-Therefore, the chapters depend on eachother and are best read in order.
+This part is a monograph focussing on \glspl{TOP} for the \gls{IOT} and hence are the chapters best read in order.
The monograph is compiled from the following papers and revised lecture notes.
+\newcommand{\citeentry}[1]{\begin{NoHyper}\bibentry{#1}\end{NoHyper}. \citep{#1}}
\begin{itemize}
- \item \bibentry{koopman_task-based_2018}.
+ \item \citeentry{koopman_task-based_2018}
This was the initial \gls{TOP}/\gls{MTASK} paper.
- Pieter Koopman wrote it but I helped with the software and research.
- \item \bibentry{lubbers_task_2018}.
+ Pieter Koopman wrote it, I helped with the software and research.
+ \item \citeentry{lubbers_task_2018}
This paper was an extension of my Master's thesis~\citep{lubbers_task_2017}.
It shows how a simple imperative variant of \gls{MTASK} was integrated with \gls{ITASK}.
While the language was a lot different than later versions, the integration mechanism is still used in \gls{MTASK} today.
-
The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer in which we discussed and refined the ideas.
- \item \bibentry{lubbers_multitasking_2019}.
+ \item \citeentry{lubbers_multitasking_2019}
This paper was a short paper on the multitasking capabilities of \gls{MTASK} in contrast to traditional multitasking methods for \gls{ARDUINO}.
- \item \emph{Simulation of a Task-Based Embedded Domain Specific Language for the Internet of Things}~\todo{cite when published}
+ The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer.
+ \item \citeentry{koopman_simulation_2018}\todo{change when published}
These revised lecture notes are from a course on the \gls{MTASK} simulator was provided at the 2018 CEFP/3COWS winter school in Ko\v{s}ice, Slovakia.
- Pieter Koopman wrote and taught it though I helped with the software and research.
- \item \emph{Writing Internet of Things applications with Task Oriented Programming}~\todo{cite when published}
+ Pieter Koopman wrote and taught it, I helped with the software and research.
+ \item \citeentry{lubbers_writing_2019}\todo{change when published}
These revised lecture notes are from a course on programming in \gls{MTASK} provided at the 2019 CEFP/3COWS summer school in Budapest, Hungary.
- Pieter prepared half of the lecture. I wrote the lecture notes, prepared the other half of the lecture, the assignments and practical session.
- \item \bibentry{lubbers_interpreting_2019}.
+ Pieter Koopman prepared and taught half of the lecture and supervised the practical session.
+ I taught the other half of the lecture, wrote the lecture notes, made the assignments and supervised the practical session.
+ \item \citeentry{lubbers_interpreting_2019}
- This paper showed an implementation for \gls{MTASK} for microcontrollers in the form of a compilation scheme and informal semantics description.
+ This paper shows an implementation for \gls{MTASK} for microcontrollers in the form of a compilation scheme and informal semantics description.
- The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer in which we discussed and refined the ideas.
- \item \emph{Reducing the Power Consumption of IoT with Task-Oriented Programming}~\todo{cite when published}
+ The research in this paper and writing the paper was performed by me, though there were weekly meetings with Pieter Koopman and Rinus Plasmeijer.
+ \item \citeentry{crooijmans_reducing_2022}\todo{change when published}
This paper shows how to create a scheduler so that devices running \gls{MTASK} tasks can go to sleep more automatically.
Furthermore, it shows how to integrate hardware interrupts into \gls{MTASK}.
- The research was carried out by Sjoerd Crooijmans during his Master's thesis~\citep{crooijmans_reducing_2021}.
+ The research was carried out by \citet{crooijmans_reducing_2021} during his Master's thesis.
I did the daily supervision and helped with the research, Pieter Koopman was the formal supervisor and wrote most of the paper.
- \item \emph{Asynchronous Shared Data Sources}~\todo{cite when accepted}
-
- \todo[inline]{This paper could in theory be dropped in favour of being done sooner with the thesis}
+ \item \emph{Green Computing for the Internet of Things}\todo{change when published}
- Asynchronous \glspl{SDS} are used in the current \gls{ITASK} system and allow bigger \gls{IOT} devices such as raspberry pi's to be used in a tierless \gls{ITASK} system.
- The example application shown in \cref{prt:tvt} heavily uses asynchronous \glspl{SDS}.
- This paper shows how to lift \glspl{SDS} to operate asynchronously independent of \gls{ITASK} or another \gls{TOP} implementation.
+ These revised lecture notes are from a course on sustainable programming using \gls{MTASK} provided at the 2022 SusTrainable summer school in Rijeka, Croatia.
- The initial research was carried out by Haye B\"ohm during his Master's thesis~\citep{bohm_asynchronous_2019}.
- I did the daily supervision and helped with the research, Pieter Koopman and Rinus Plasmeijer were the formal supervisors.
- I extended and generalised the research and wrote the paper.
- \item \emph{Green Computing for the Internet of Things}~\todo[inline]{cite when done}
-
- These revised lecture notes are from a course on sustainable programming using \gls{MTASK} provided at the 2022 Sustrainable summer school in Rijeka, Croatia.
-
- Pieter prepared half of the lecture and wrote the introduction.
- I wrote the middle part of the lecture notes, prepared the other half of the lecture, the assignments and the practical session.
-\end{itemize}
-
-The movement is made up out of the following chapters
-\todo[inline]{preliminary}
-
-\begin{itemize}
- \item The mTask language (includes informal semantics)
- \begin{itemize}
- \item Expressions
- \item Functions
- \item Tasks
- \item Shares
- \item Peripherals
- \end{itemize}
- \item Interpretations/views/backends\todo{decide on terminology}
- \item Green computing
- \item Integration with iTask
- \item Implementation (based on IFL19 paper)
- \item TOP for IoT beyond microprocessors
+ Pieter prepared and taught a quarter of the lecture and supervised the practical session.
+ I prepared and taught the other three quarters of the lecture, made the assignments and supervised the practical session\todo{writing contribution}.
\end{itemize}
\subsection*{\nameref{prt:tvt}}
-These chapters focus on comparing traditional tiered architectures to tierless architectures and are based on a single journal paper that extended on a conference paper.
-The conference paper was partly funded by the Radboud-Glasgow Collaboration Fund.
-It does both a qualitative and a quantitative four-way comparison of a smart campus application.
-
-The research in these papers and writing them 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 micropython implementation (\acrshort{PWS}), the original python implementation (\acrshort{PRS}) and the server application were created by Jeremy Singer, Dejice Jacob and Kristian Hentschel~\citep{hentschel_supersensors:_2016}.
+This chapter is based on the journal paper: \citeentry{lubbers_could_2022}\footnote{The journal paper is an extension of the conference article: \citeentry{lubbers_tiered_2020}\footnotemark{}}.
+\footnotetext{This paper was partly funded by the Radboud-Glasgow Collaboration Fund.}
-\begin{itemize}
- \item \bibentry{lubbers_tiered_2020}.
- \item \emph{Could Tierless Languages Reduce IoT Development Grief?}~\todo[inline]{cite when accepted}
-\end{itemize}
-
-\newcounter{secondauthorcnt}
-\newcounter{underreviewcnt}
-\newcounter{plannedcnt}
-\newcounter{publicationscnt}
-\newcommand{\secondauthor}{\textsuperscript{$\ast$}\stepcounter{secondauthorcnt}}
-\newcommand{\underreview}{\textsuperscript{$\dagger$}\stepcounter{underreviewcnt}}
-\newcommand{\planned}{\textsuperscript{$\ddagger$}\stepcounter{plannedcnt}}
-
-\subsection{List of publications}
-\begin{enumerate}
- \item \secondauthor{}
- A Task-Based DSL for Microcomputers
-
- P. Koopman\footnote{\orcid{0000-0002-3688-0957}}, M. Lubbers\footnote{\orcid{0000-0002-4015-4878}}, and R. Plasmeijer (RWDSL 2018)~\citep{koopman_task-based_2018}.
- \item Task Oriented Programming and the Internet of Things
-
- M. Lubbers, P. Koopman, and R. Plasmeijer (IFL 2018)~\citep{lubbers_task_2017} (extension of Master's thesis~\citep{lubbers_task_2018}).
- \item Multitasking on Microcontrollers using Task Oriented Programming
-
- M. Lubbers, P. Koopman, and R. Plasmeijer (MIPRO/4COWS 2019)~\citep{lubbers_multitasking_2019}.
- \item \secondauthor{}
- Simulation of a Task-Based Embedded Domain Specific Language for the Internet of Things
-
- P. Koopman, M. Lubbers, and R. Plasmeijer (CEFP/3COWS 2018).
- \item Writing Internet of Things applications with Task Oriented Programming
-
- M. Lubbers, P. Koopman, and R. Plasmeijer (CEFP/3COWS 2019).
- \item Interpreting Task Oriented Programs on Tiny Computers
-
- M. Lubbers, P. Koopman, and R. Plasmeijer (IFL 2019)~\citep{lubbers_interpreting_2019}.
- \item Tiered versus Tierless IoT Stacks: Comparing Smart Campus Software Architectures
-
- M. Lubbers, P. Koopman, A. Ramsingh\footnote{\orcid{0000-0003-3501-902X}}, J. Singer\footnote{\orcid{0000-0001-9462-6802}}, and P. Trinder\footnote{\orcid{0000-0003-0190-7010}} (IoT 2020)~\citep{lubbers_tiered_2020}.
-
- % in press
- \item Deep Embedding with Class
+It compares programming traditional tiered architectures to tierless architectures by showing a qualitative and a quantitative four-way comparison of a smart campus application.
- M. Lubbers (TFP 2022).
- \item \secondauthor{}
- Reducing the Power Consumption of IoT with Task-Oriented Programming
-
- S. Crooijmans, M. Lubbers, and P. Koopman (TFP 2022).
-
- %Under review
- \item \underreview{} Could Tierless Languages Reduce IoT Development Grief?
-
- M. Lubbers, P. Koopman, A. Ramsingh, J. Singer, and P. Trinder (ACM TIOT) (extension of~\citep{lubbers_tiered_2020}).
- \item \secondauthor\underreview{}
- Strongly-Typed Multi-View Stack-Based Computations
-
- M. Lubbers and P. Koopman (IFL 2022 under review).
- \item \underreview{} First-Class Data Types in Shallow Embedded Domain-Specific Languages using Metaprogramming
-
- M. Lubbers, P. Koopman, and R. Plasmeijer (IFL 2022 under review).
- \item \underreview{} Asynchronous Shared Data Sources
-
- M. Lubbers, H. Böhm, P. Koopman, and R. Plasmeijer (IFL 2022 under review).
-
- %Planned
- \item \planned{} Green Computing for the Internet of Things
-
- M. Lubbers, P. Koopman (Sustrainable 2022 planned).
-
- \setcounter{publicationscnt}{\value{enumi}}
-\end{enumerate}
-
-There are \thepublicationscnt{} publications of which \thesecondauthorcnt{} I'm second author, \theunderreviewcnt{} are under review and \theplannedcnt{} are planned.
+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}.
\input{subfilepostamble}
\end{document}
repositories / phd-thesis.git / blobdiff