From e49ac7eab40ed4e999ef26b092efd1055de67815 Mon Sep 17 00:00:00 2001 From: "hannes.kuchelmeister" Date: Sat, 9 May 2020 10:55:28 +0200 Subject: [PATCH] remove mention of M.Customer --- 30_Thesis/sections/10_foundations.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/30_Thesis/sections/10_foundations.tex b/30_Thesis/sections/10_foundations.tex index 275d6e2..8752e7e 100644 --- a/30_Thesis/sections/10_foundations.tex +++ b/30_Thesis/sections/10_foundations.tex @@ -217,7 +217,7 @@ The following list provides a short overview of each component. \item[M.Core] provides the base of the configurator. It checks the configuration against all rules in the database, provides possible alternatives if a change invalidates other parts of a configuration. The system relies on a CSP solver for validation and suggestion of alternatives. \item[M.Model] is the editor to create products and rules. These rules can then be uploaded to M.Core. \item[M.Collab] is a node.js server application that communicates with M.Core via REST-API and with M.Collab-Customer via WebSockets. It sits in between M.Collab-Customer and M.Core and handles all processing regarding collaborative configuration. - \item[M.Collab-Customer] is a modified version of M.Customer that does all communication via WebSockets and does communicate with M.Collab instead of M.Core. M.Customer is the customer facing component. It allows a customer to configure a product or solution. \todo[inline]{M.Collab striechen} + \item[M.Collab-Customer] is the customer facing component. It allows a customer to configure a product or solution and contains the user interface. Actions undertaken in M.Collab-Customer are send to M.Collab. \end{description} \section{Software Design}