13hannes11/bachelor_thesis
1
0
Fork 0
mirror of https://github.com/13hannes11/bachelor_thesis.git synced 2024-09-04 01:11:00 +02:00
Code Issues Projects Releases Wiki Activity

add requirements and assumptions to conecpt

Browse Source
This commit is contained in:
hannes.kuchelmeister
2020-04-20 11:46:30 +02:00
parent 028083731c
commit 00b5cc3728
1 changed files with 16 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
30_Thesis/sections/40_concept.tex
View File

@@ -58,30 +58,32 @@ For a group recommender system additional definitions are needed. The attitude o
\section{Requirements} \section{Requirements}
\label{sec:Concept:Requirements} \label{sec:Concept:Requirements}
\todo[inline]{add requirements} This section lists requirements that are considered and implemented in this thesis.
\begin{itemize} \begin{itemize}
\item Simple user interface that only uses three discrete states (like in some social media platforms e.g. reddit) \item Have a simple user interface that only uses three discrete states (like, neutral, dislike).
\item Usable without proprietary software \item The recommendation engine can be used without proprietary software.
\item Give recommendations to a group based on their preferences and the current configuration state \item Give recommendations to a group based on their preferences and the current configuration state.
\item Usage by multiple users at the same time \item The system supports multiple users at the same time.
\item The system should be able to work with other configuration systems too \item The system should be able to work with other configuration systems.
\item A system should give recommendation for the group using a scoring function that takes into account preferences of group members and the current state of the situation. \item The system should take the current configuration state into account.
\item Recommendations should allow different scoring functions. \item Recommendations should allow different scoring functions.
\item Recommendations should always be valid options. \item Recommendations should always be valid solutions.
\item The system should consider all preferences of individuals in a group and find a solution that most people of the group are happy with. \item They system has to respond in a timely manner.
\end{itemize} \end{itemize}
\section{Assumptions} \section{Assumptions}
\label{sec:Concept:Assumptions} \label{sec:Concept:Assumptions}
\todo[inline]{add assumptions} Due to a thesis having a limited scale some assumptions have to be made. The assumptions made are listed in this section.
\begin{itemize} \begin{itemize}
\item Only one product/solution is supposed to be configured at the same time \item Only one product/solution is supposed to be configured at the same time by one group.
\item Features only support single value attributes \item Features only support single value attributes.
\item Users join the system and start configuring once all group members have joined \item Users join the system and start configuring only after all group members have joined.
\item User interface is for demoing purposes only \item The user interface is for demoing purposes.
\item Speed and optimization of the system is not a high priority.
\end{itemize} \end{itemize}
\section{User Interaction with the System} \section{User Interaction with the System}