ソースを参照

Add result to evaluation

tags/0.5.1-reflection
コミット
6799629bc7
2個のファイルの変更36行の追加2行の削除
  1. +6
    -2
      content/case_evaluation.tex
  2. +30
    -0
      content/case_evaluation_result.tex

+ 6
- 2
content/case_evaluation.tex ファイルの表示

@@ -1,6 +1,10 @@
%&tex
\chapter{Case Study: Evaluation}
\label{chap:case_evaluation}

\section{Result}
\input{content/case_evaluation_result.tex}

\section{Time Investment}
Prior to each step in the development, I made an estimation on the workload of that particular step.
In \autoref{fig:time_spend} the planned and spend time on each step is plotted next to each other.
@@ -13,7 +17,7 @@
\begin{figure}
\centering
\includegraphics{graphics/time_table.pdf}
\caption{Overview of the planned and spend number of days for each step during the case study.}
\caption{Overview of the planned and spend number of days for each step during the case study. For Development Cycle 1 three days were planned for the initial development, based on the outcome I decided to abandon this cycle. Therefore, no additional time was planned nor spend on the development.}
\label{fig:time_spend}
\end{figure}
Furthermore, there is a significant difference between the planned number of days for both development cycles.
@@ -32,7 +36,7 @@
However, the time required to get the software to a viable state was four weeks.
Even though, the focus was not on the software, this timespan of four weeks is too significant to ignore.
Especially when the software is compared to the developed models.
In total I build eight competent models: a CAD drawing, one kinematics model, three 2D models and three 3D models.
As explained in the previous section, I build a total of eight models.
Each of these models includes documentation and an evaluation of the design process.
The software, on the other hand, is in a bare minimum state; I skipped documentation and evaluation; and the code quality relatively low.
Still, the software was more time consuming than the hardware modeling and development.


+ 30
- 0
content/case_evaluation_result.tex ファイルの表示

@@ -0,0 +1,30 @@
%&tex
This previous chapter described the development and implementation process of the Whiteboard Writer.
The following is a brief overview of the produced design, models and prototype.
The design is covered with dynamic models and CAD drawing.
These dynamic models can be categorized into three different modelling approaches, with different levels of detail:
\begin{description}
\item{Kinematics:}
\begin{itemize}
\item Basics model
\end{itemize}
\item{2D:}
\begin{itemize}
\item Ideal physics implementation
\item DC-motor behavior
\item Control loop
\item Stepper motor behavior
\end{itemize}
\item{3D:}
\begin{itemize}
\item 3D physics implementation
\item Marker lifting behavior
\end{itemize}
\end{description}
The CAD drawing was added at the end of the development process.
Therefore, the CAD drawing has not been made for the levels of detail prior to the marker lifting behavior.

The assembled SCARA prototype is shown in \autoref{fig:scara_pic}.
This prototype is able to make complete \autoref{test1}, which is the small rectangle.
Furthermore, it was possible to write three characters, which completes \autoref{test_triple_char}.


読み込み中…
キャンセル
保存