add high level architecture concept for recommender

This commit is contained in:
hannes.kuchelmeister
2019-12-09 14:50:36 +01:00
parent 5d5f2951f4
commit e3f51ea48b
3 changed files with 15 additions and 2 deletions

View File

@@ -21,7 +21,6 @@
\section{CAS Group-Configurator}
\label{sec:Concept:GroupConfigurator}
\citeauthor{raabKollaborativeProduktkonfigurationEchtzeit2019} extends CAS Merlin Configurator in his thesis to allow simultaneous configuration. The extended architecture is shown in Figure \ref{fig:Concept:CollaborativeConfiguratorMerlin}.
He only makes changes to M.Customer which is renamed to M.Collab-Customer and introduces a new component M.Collab.
@@ -37,6 +36,19 @@ He only makes changes to M.Customer which is renamed to M.Collab-Customer and in
\label{fig:Concept:CollaborativeConfiguratorMerlin}
\end{figure}
\section{Extended Configurator}
\label{sec:Concept:ExtendedConfigurator}
\missingfigure{Extenden Architecture}
Extending \citeauthor{raabKollaborativeProduktkonfigurationEchtzeit2019} work a module called M.Recommender is added. Its aim is to provide a recommendation server that holds all the data needed for recommendations. M.Collab and M.Collab-Customer have to be modified to allow taking in preferences and to show recommendations. The recommender engine is set up to be in a separate system which allows the easier replacement and the usage of different technologies. The extended architecture is shown in Figure \ref{fig:Concept:RecommenderForCollaborativeConfiguratorMerlin}.
\begin{description}
\item[M.Recommender] is a new system that will get queried from M.Collab for recommendations, when the configuration changes. M.Recommender will return recommendations which then can be presented to users by M.Collab-Customer.
\end{description}
\begin{figure}
\centering
\includegraphics{./figures/MerlinCollabRecommender.pdf}
\caption{Architecture of Collaborative Configurator Merlin with an added recommender system.}
\label{fig:Concept:RecommenderForCollaborativeConfiguratorMerlin}
\end{figure}