proposal/p.tex

   1 \documentclass[a4paper]{article}
   2 \usepackage[british]{babel} \usepackage{booktabs} \usepackage{geometry}
   3 \usepackage{tabu}
   4
   5 \title{Research Internship Proposal}
   6 \date{\today}
   7 \author{Mart Lubbers (s4109503)}
   8
   9 \begin{document}
  10 \pagenumbering{gobble}
  11 \thispagestyle{empty}
  12 \clearpage
  13 \maketitle
  14 \subsection*{Practical information}
  15 \begin{table}[h]
  16         \centering
  17         \begin{tabu}{p{8em}X}
  18                 \toprule
  19                 \textbf{Start date} & September 2016\\
  20                 \midrule
  21                 \textbf{End date} & February 2017\\
  22                 \midrule
  23                 \textbf{Research group} & Software Science\\
  24                 \midrule
  25                 \textbf{Supervisors} & Rinus Plasmeijer, Pieter Koopman\\
  26                 \midrule
  27                 \textbf{Topics} & Functional programming, compilers, iTasks, embedded systems\\
  28                 \midrule
  29                 \textbf{Master courses already taken} &
  30                         Advanced Programming, Automated Reasoning,
  31                         Compiler Construction, Design of Embedded Systems,
  32                         ICT in a different culture, Model Checking,
  33                         Natural Computing, Research Seminar Software Science,
  34                         Testing Techniques\\
  35                 \bottomrule
  36         \end{tabu}
  37 \end{table}
  38
  39 \subsection*{Description of the research activities}
  40 In \emph{Task Oriented Programming} (TOP) a program is built out of pieces of
  41 work called \emph{tasks}~\cite{achten_introduction_2015}. Tasks differ from
  42 function in the way that they return a result. A task's return value can change
  43 over time. Task exist in many forms and they can be composed sequentially and
  44 in parallel. Some possible tasks are asking for user input via a web browser,
  45 setting up a TCP connection to another server or combining several tasks. At
  46 the moment there are several types of leaf tasks. A leaf task is a task that
  47 does not consist of tasks itself. Examples of leaf tasks are  the so called
  48 editors.
  49
  50 This proposal describes the effort to add another type of leaf task that
  51 focusses on microcontrollers. Microcontrollers are often not powerful
  52 enough to run a full-fledged task server and therefore there is the need to
  53 introduce special microcontroller tasks. Effort for this is already made by by
  54 the department~\cite{koopman_tasks_2016}. However, communication between the
  55 \emph{mTask} and the iTasks system is still lacking and exactly that will be the
  56 goal of the project. This requires adding a new type of leaf task that allows
  57 the user to run \emph{mTasks} on microcontrollers. The leaf task should
  58 abstract away from communication techniques and it should be relatively easy to
  59 add techniques. Techniques that are interesting to experiment with is Serial
  60 communication, Bluetooth, \textsc{WiFi}, \textsc{GSM} and \textsc{LoRa}.
  61
  62 Similar work has been done in the department on distributing tasks to so-called
  63 \emph{node-servers}~\cite{oortgiese_task_2016}. It might be possible that the
  64 same communication strategy can be used with a slimmed down taskserver on a
  65 microcontroller.
  66
  67 \bibliographystyle{ieeetr}
  68 \bibliography{p}
  69 \end{document}