|
|
@@ -37,7 +37,7 @@ |
|
|
\subsubsection{Separating Functions and Components} |
|
|
\subsubsection{Separating Functions and Components} |
|
|
It was decided not to add the SCARA and the cable bot as features, for the reason that they do not define behavior. |
|
|
It was decided not to add the SCARA and the cable bot as features, for the reason that they do not define behavior. |
|
|
Instead, the features define how the hardware behaves. |
|
|
Instead, the features define how the hardware behaves. |
|
|
A solution to organize the relations between features and components was found in RobMoSys\footnote{\url{https://robmosys.eu/approach/}}. |
|
|
|
|
|
|
|
|
A solution to organize the relations between features and components was found in RobMoSys \autocite{noauthor_robmosys_2017}. |
|
|
RobMoSys defines a separation of levels in a design. |
|
|
RobMoSys defines a separation of levels in a design. |
|
|
Where the levels start functional and moves via software to hardware implementation. |
|
|
Where the levels start functional and moves via software to hardware implementation. |
|
|
Although not all levels of RobMoSys are used, it was very useful to define the features of the system. |
|
|
Although not all levels of RobMoSys are used, it was very useful to define the features of the system. |
|
|
|
