From a44ad524f45e50ddd0cbdd4a20baa91d377c2ebb Mon Sep 17 00:00:00 2001 From: "hannes.kuchelmeister" Date: Tue, 17 Mar 2020 10:47:44 +0100 Subject: [PATCH] take future work from outline --- 30_Thesis/sections/70_future_work.tex | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/30_Thesis/sections/70_future_work.tex b/30_Thesis/sections/70_future_work.tex index 488869a..1fd5618 100644 --- a/30_Thesis/sections/70_future_work.tex +++ b/30_Thesis/sections/70_future_work.tex @@ -1,2 +1,11 @@ -\chapter{Future Work} -\label{ch:FutureWork} +\chapter{Further Work} +\label{ch:FurtherWork} + +\section{Possible Extensions or Further Research} +\label{sec:FurtherWork:PossibleExtensions} + +\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 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} \ No newline at end of file