-%Applying the concepts of \gls{LSOC} to \gls{IOT} systems can be done in two ways.
-%Firstly, edge devices can be seen as simple resources, thus accessed through the resource access layer.
-%The second view is that edge devices contain miniature \gls{LSOC} systems in itself as well.
-%In \gls{TOSD} the same can be applied.
-%The individual components in the miniature systems, the tasks, the \glspl{SDS}, are connected to the main system.
-%\t odo{Is deze \P\ dui\-de\-lijk genoeg of \"uberhaupt nodig?}
+\Cref{fig:tosd} differs from the presented \gls{IOT} architecture because they represent separate concepts.
+The \gls{IOT} architecture from \cref{fig:iot-layers} describes an execution architecture wheras the \gls{TOSD} figure describes a softwared development model.
+E.g.\ from a software development perspective, a task is a task, whether it is executed on a microcontroller, a server or a client.
+Only once a task is executed, the location of the execution becomes important, but this is taken care of by the system.
+Some concepts from the \gls{TOSD} model can be mapped upon the \gls{IOT} architecture though.
+Applying the concepts of \gls{TOSD} to \gls{IOT} systems can be done in two ways.
+Firstly, edge devices can be seen as simple resources, thus accessed through \glspl{SDS}.
+The second view is that edge devices contain miniature \gls{TOP} systems in itself.
+The individual components in the miniature systems, the tasks, the \glspl{SDS}, are, in the eventual execution, connected to the main system.
+\todo{ik ben niet echt te\-vre\-den met deze \P}