From bb78f154803e5810ac16292251c86657cc2d0083 Mon Sep 17 00:00:00 2001 From: Wouter Horlings Date: Wed, 13 Jan 2021 16:05:40 +0100 Subject: [PATCH] Improve evaluation --- content/case_experiment_test_protocol.tex | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/case_experiment_test_protocol.tex b/content/case_experiment_test_protocol.tex index 6652b17..44615ff 100644 --- a/content/case_experiment_test_protocol.tex +++ b/content/case_experiment_test_protocol.tex @@ -101,8 +101,13 @@ \subsubsection{Evaluation} This step was completed without many difficulties. - Even though it required a revision of the earlier specifications and defining order of operation. - However, this is an issue with the preparation phase in general, not with this step in particular. + Which includes the revision of the earlier specifications and definition of orders of operation. + Indicating that I overlooked details while defining the specifications in \autoref{sec:specifications}. + According to the design plan as described in \autoref{chap:analysis}, I should go back and review those specifications. + Followed by reviewing all steps after the specifications. + However, this complete review is not practical and extremely time consuming. + The point here is, looking at the evaluations of this and previous steps, that chosen design strategy is not feasible, especially as a novice designer. + In \autoref{chap:case_evaluation} I will evaluate this with more detail. During the analysis, I expected more specific tests. Each test could then be used as a milestone during the development of the system.