From 8690b4402eec953aed1157b61a5929152439a56d Mon Sep 17 00:00:00 2001 From: "hannes.kuchelmeister" Date: Thu, 30 Jan 2020 10:47:55 +0100 Subject: [PATCH] added suggestions for possible extensions or future research --- 25_Outline/outline.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/25_Outline/outline.tex b/25_Outline/outline.tex index f2824f7..c57944d 100644 --- a/25_Outline/outline.tex +++ b/25_Outline/outline.tex @@ -164,8 +164,8 @@ Now the recommendation procedure looks as follows: \begin{itemize} \item How to optimise such that no need to search through all stored finished configurations is necessary? (e.g. improve runtime from $\mathcal{O}(n)$ to $\mathcal{O}(log\ n)$) - \item How to model hierarchy and knowledge about part of the products in preferences? - \item Letting users just chose functions and how much they value them instead of rating individual attributes (more lay friendly). And how does this compare to explicitly choosing preferences. + \item How to model hierarchy and knowledge about product components in preferences? + \item Letting users set preferences for product functions (e.g. for a forest a recreation function, a productive function, a protective function, etc.). How does it compare to explicitly choosing preferences? \end{itemize}