From 15d016a5bf581c4e6ba3e50c1e400f509d4ef7b3 Mon Sep 17 00:00:00 2001 From: "hannes.kuchelmeister" Date: Wed, 29 Apr 2020 14:13:43 +0200 Subject: [PATCH] fix description of the use case --- 30_Thesis/sections/40_concept.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/30_Thesis/sections/40_concept.tex b/30_Thesis/sections/40_concept.tex index 35304de..c2d19dd 100644 --- a/30_Thesis/sections/40_concept.tex +++ b/30_Thesis/sections/40_concept.tex @@ -102,8 +102,8 @@ The evaluation is done solely with the recommender system and its APIs therefore \section{User Interaction with the System} \label{sec:Concept:UserSystemInteraction} -The system has one main way to be used as defined in \autoref{tab:Concept:MainUseCase}. This process is also visualized in \autoref{fig:Concept:ConfigurationProcess}. -hier braucht es noch eine genauere textliche Beschreibung, was in der Grafik zu sehen ist. Auch: woher kommt diese Prozessdefinition? Wurde sie aus den Requirements und Einschränkungen abgeleitet? +The system has one main way to be used as defined in \autoref{tab:Concept:MainUseCase}. This process is also visualized in \autoref{fig:Concept:ConfigurationProcess}. All users start the configuration process together. +They select the current state at the beginning of the process. Then repeatedly users enter their preferences until each user's preference have been entered into a system. Based on the entered preferences the system generates a recommendation that is a compromise of all users preferences. \begin{figure} \centering